This guide is for new Chapter leads and Technical Writers
Open Source Community Africa (O.S.C.A) is for open source lovers, enthusiasts, advocates and experts within and across Africa with the sole aim of increasing the rate of credible contributions by African software developers, designers, writers and everyone involved in the sphere of technology to open source projects both locally and globally, changing the perception of Africans from just the billion users to the NEXT BILLION CREATORS.
General Writing Rules
Towards changing the perception of Africans from just the billion users to the NEXT BILLION CREATORS, we publish internal contents, chapter recap articles, and guest posts on our Blog. Before we publish your content, please ensure that you are willing to agree to the following terms.
- You must abide by our Code of Conduct
- Your submission must be Open Source related
- Plagiarism is a crime, your content must be original, and all extracts must be attributed accurately
- Your content should not include promotional materials or links
- We reserve the right to edit your content to remove typographical errors, grammatical errors, and to improve the title.
- Your content will be shared on all our social media
- Not all submitted content will be published, we will provide feedback(s) where necessary
Guide for Chapter Leads
As chapter leads, it is expected that you write a recap article after every event like this, which would be published on our blog. Here's how to get started:
Upon completion of your event, prepare a draft recap article with the following information:
- Introduction to the event
- How did the event go
- Recap of each talk with pictures
- Link to speaker slides
- Link to event photos
- Attendees feedback(s)
- Special thanks to sponsor(s), speaker(s) and attendees
Your draft should be submitted on or before 72 hours after the event. If there would be any delays, feel free to contact the Technical Writing Team.
Our blog is powered by Devblog Team Publication, and it is expected that you create a Devblog account to have your articles published with us.
PS: You need to be a chapter lead to request for access
- Write your article on Hashnode like so:
- Scroll to the bottom of the editor and locate the Post this to a publication? section
blog.oscafrica.orgfrom the dropdown list like so
- Now click the Publish button to submit the post for review
- You will get an edit link after submission on the next page where you can make changes to your submission before final reviews
- Contact any member of the Technical Writing team again on [Discord](https://bit.ly/osca-discord or Bolaji on Twitter to request for a review
- Your submitted article will be reviewed, and some changes will be made with feedbacks related back to you
- Upon successful reviews, it would be published on the blog.
Guide for Technical Writers
If you would like to share your expertise and experience on the OSCA blog, please reach out to Bolaji on Twitter to start a conversation.
We accept guest posts from just any amazing human with excellent technical writing skills around contents related to and not limited to Open Source:
- and lot's more.
We keep an Open OSCA Writing Ideas Doc, you can pick an idea and request to work on it or add your own idea.
Why Guest Post?
Submitting a guest post helps put your content in front of amazing Open Source creators and contributors across the globe, It is also a great way to build your technical writing portfolio and an opportunity to work with the amazing humans at Open Source Community Africa.
- Your article is published by you on our Blog, we don't take any credits for them.
- We help you market your article by sharing it across all our social media.
- Our Technical writing team is top-notch, you will get an opportunity to get your article reviewed by an experienced writer.
- Top organizations sponsoring us will see your article, including Facebook Open Source and Google Open Source, amongst others.
- When you attend any OSCA organized event, you will be celebrated with some fantastic event swags.
Convinced now? Please reach out, and let's get started on that brilliant idea 🙂.
Got any suggestion(s) on how to improve this Document? You can suggest them by creating an Issue or Pull Request here
This work is licensed under a Creative Commons Attribution 3.0 Unported License.