The open source community is diverse and highly motivated. We're sure you'll be able to find someone who can help you (or that you can help) no matter what your interests are.
Whether it's development or advocacy, open source software and other collaborative projects benefit through, and because of, community. Unlike traditional projects that require physical resources, sharing economies are generally only hindered by the number of people contributing to an effort and their ability to acquire and share knowledge.
Our development efforts generate resources for collaborative organizations, to help create and maintain communication within and among open source projects; motivate and efficiently organize groups of remote individuals, and; cultivate an open ethos where the principles and practices of open source can foster collaboration co-creation and community.
If you want to contribute to a project and make it better, your help is very welcome. Contributing is also a great way to learn more about social coding on Github, new technologies and and their ecosystems and how to make constructive, helpful bug reports, feature requests and the noblest of all contributions: a good, clean pull request.
Look for a project's contribution instructions. If there are any, follow them.
- Create a personal fork of the project on Github.
- Clone the fork on your local machine. Your remote repo on Github is called origin.
- Add the original repository as a remote called upstream.
- If you created your fork a while ago be sure to pull upstream changes into your local repository.
- Create a new branch to work on! Branch from develop if it exists, else from master. Implement/fix your feature, comment your code.
- Follow the code style of the project, including indentation.
- If the project has tests run them!
- Write or adapt tests as needed.
- Add or change the documentation as needed. Squash your commits into a single commit with git's interactive rebase. Create a new branch if necessary. Push your branch to your fork on Github, the remote origin. From your fork open a pull request in the correct branch. Target the project's develop branch if there is one, else go for master! ... Once the pull request is approved and merged you can pull the changes from upstream to your local repo and delete your extra branch(es). And last but not least: Always write your commit messages in the present tense. Your commit message should describe what the commit, when applied, does to the code – not what you did to the code.