The Shakespearean question of every leader of a free software project is: how can I get other developers interested and willing to commit to my project? Sometimes you have the crazy idea that just by having a good idea or by developing a very good quality software, that alone, as if by magic, will attract developers en masse to produce plugins, polish some visual aspects, introduce new improvements, fix bugs, etc.
The harsh reality is very different. |
How to get other developers to help us?
Gregory Wilson, a professor of computer science at the University of Toronto, argued that the Google Summer of Code and UCOSP They have shown that it is much easier for students to collaborate on these (free software) projects if they can do so by fixing small errors or making small improvements. At least that's a good way to start.
Following this advice, the people of OpenHatch, has created lists with small errors (bugs) that need to be fixed, belonging to a large number of soft projects. free. More than 100 projects have already joined this system.
To make them easier to find, the OpenHatch volunteer opportunity finder allows you to search, in one place, more than 1000 small errors belonging to hundreds of projects.
If you know of a project that should be included in the listings, you can add it to the OpenHatch system very easily. First, check the list of bug trackers that OpenHatch is already monitoring. If the project you contribute to is not on that list, go to the project's bug tracker right now and tag the small bugs you want to add to OpenHatch as "bite size". Finally, add your bug tracker to the OpenHatch index.