Sharing my slides at open source Festival talk, "How to improve the way you write codes by contributing to Open_Source". Really appreciate everyone that attended the workshop! @oscafrica
@Samson_Goddy
@Didicodes
@iambolajiayo
@oscaimo
the best ways to get started with the real-world experience of the programming world and learning quickly • open-source organizations are very eage and welcoming new contributors to their platforms.
solutions Well, the first and foremost advantage of doing open-source is that you learn different things. When you are doing open-source you have to complete the PRs which involve writing code, tests and documentation for the feature that you are building.
the team Open-source involves communicating with all the people in the organizations in a public channel. This will help you a lot on how to communicate your concerns better. How to ask questions and what questions to ask is very important to learn.
You also get a sense of pride while you build something that people use. You also get good feedback from the users who directly use the feature that you build.
to stay there for a long time to come and people will judge you with the code that you have written for these organizations. Since most of the organizations have a high standard for type of code they merge to the repository, you will be rated highly among your peers for participating in some open-source organization.
very important. Always try to choose the organizations whose product you might have used in the past. This helps you to build a sense on how the product should work.
is to figure out all the communication channels which the organization uses and join all of them.Introduce yourself as quickly as possible. Communicate your intentions of joining early. If you are there to participate in GSoC, best to tell them right from the start that you are doing it for the reason.
project on local following the instruction from the organizers or READMEs and let them know if READMEs are wrong anywhere. Sometimes, people figure out something wrong in the READMEs and its a great point to start and write a patch for them.
with Most organizations mark easy issues as good-first issues. You can pick any one of those issues and start solving them. Just remember to tell the organizers that you working on that issue so that no one else picks it up at the same time.