A while ago I started an open-source project, which for me meant (until now) I simply pushed my source code to a public repository (Mercurial on Google Code). Recently though, I’ve received requests from other people to collaborate on my project. Having never collaborated on an open-source project before, I’m not sure how to proceed:
- Do I just give them access to the repository so they can push changes? If they push something I don’t like I can always roll back and if they get on my nerves I can always revoke their access to the repository.
- Do I tell them to send in patches (via the issue tracker) and then apply the ones I like and revoke the ones I don’t?
Now:
- I don’t want to lose ownership of my project. It’s a pretty nice project and it’s good resume material. I think this is what I am most afraid of. However, I want to give proper credit to my collaborators.
- I know this is the whole point of open-source: collaboration, so I don’t want to be an idiot and say no to these people who want to help.
- Lately I haven’t had much time to code on my project, so it could use some help.
Also, I’m a bit reluctant to let just anyone work on my project. What if they’re, pardon the expression, noobs? I suppose I can just rollback they’re changes and tell them to, pardon the expression, gtfo, but that wouldn’t be particularly nice.
How is this usually done?
Have different levels of contribution.
Start by taking patches from everyone. You don’t have to accept them all – if rejecting a patch, explain why it was rejected and what can be done to improve it.
For accepted patches, clean them up (and document the cleanups in a coding style guide).
The people providing the most and best patches could then get access to the repository directly and start accepting patches themselves.
At this point, accept the fact that the project is no longer just yours, though you may want to continue and lead it.