Skip to content

septa-ma/working-in-open-source

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

20 Commits
 
 

Repository files navigation

A- How open source helps you in your career life?

  • 1- learn new things: you will find plenty of architectures, frameworks, patterns, implementations which you never seen before.
  • 2- strengthen your skills: you can keep refresh and up to date with your knowledge.
  • 3- receive feedback: feedback from other developers will help you extend your views and solve problems from various ways.
  • 4- help the community.
  • 5- make better work samples and improve your resume: having a good online presence is a huge bonus, and contributing to open source is extremely revalued when recruiters view your resume.
  • 6- expand your networking and finding a new job: lots of professionals are spending some of their time in open source.
  • 7- personal satisfaction and confidence boost.

B- How to find a project?

C- How to contribute to the open-source contributions?

  • 1- Code Contributions: You can contribute to the code of the project. You can add a new feature to it or you can solve bugs by writing the code.
  • 2- Documentation contributions: This involves writing or updating documentation for the project, such as adding examples, improving the read-me file, or fixing errors. you can translate documentation in your own language.
  • 3- Designing: You can contribute to the project with the UI design of the project or you can help them in designing posters or social media visuals designs.
  • 4- Testing: You can contribute to open-source projects as a tester as well. you can test the application, documents of a project, or anything where you want to contribute. You help them find bugs in their product/application by providing an explanation of the bug and helping fix problems.
  • 5- Reviewing Pull requests: As lots of PR is made, you can help them by reviewing PRs and correcting them with the contributor. for example linking duplicate issues, asking for more details in case a bug or a feature request is not clear enough, reproducing bugs and adding more context.
  • 6- Community contributions: It involves helping people to contribute and answering their questions and organizing events for the communities. You can find many of them from Explore -> Topics -> Awesome lists.

D- How to become familiar with a project's culture?

  • 1- it has to have LICENSE to understand if it's open source or not.
  • 2- check the number of commits and last day of commit.
  • 3- reading README.md to learn more about the project.
  • 4- look at CONTRIBUTING.md or CODE OF CONDUCT file to understand not only how the contribution workflow is handled in the project, but also knowing about the vision of it.
  • 5- navigate to the issues tab, not only to see how users write their issues and how maintainers answer and guide the community, but also you can filter the issue for finding a good one to work on.
  • 6- click on Pull Requests tab and check and read some.
  • 7- search todo on the repository to find out what things need to be done.

E- How to make a pull request?

  • 1- make a fork from the project.
  • 2- clone on your local machine.
  • 3- create a new branch and go to that branch.
  • 4- work on the project.
  • 5- for being sure nothing change in original branch go to original branch and pull the project.
  • 6- go to your branch and pull again then add changes to the repository.
  • 7- when your done create your pull request.

sources:

About

how contributing in open source community.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published