Open Source Recruiting Is Fundamental
Update Corrected my pop-culture iconography mix up.
Thomas Eyde brings up a great point in the comments section of Scott Hanselman’s post about SandCastle and the death of NDoc.
It’s sad to see good projects die, especially when programmer support is a main reason.
But on the other side, it’s not that easy to join these projects. How many of them advertise? How often do we see “Developers wanted on [your favorite project]”?
I think these projects must advertise what they need. Do they need C++ expertise? Java? C#? UI design? How do we know what to do? Where are the tasks listed? How do we assign to them?
Open Source project that are lacking in developer support probably need to tear off a page from the corporate playbook and be a bit more savvy about recruiting developers. I often hear developers wistfully day dreaming that if they just open source their pet project, legions of developers will take up the banner and join in.
Ha! Hardly! Recruitment is necessary and fundamental to an OS project. So much so that SourceForge has a tab dedicated to the topic in the admin section of a project.
Seeking skilled developers (and people who are interested in the goals of your project) is one of the most important activities performed by project administrators.
But by no means limit yourself to SourceForge. Consider putting a free ad in CraigsList or in the forums of other developer communities.
The second comment on Scott’s post by Martin Bennedik questions the donation model.
But I don’t understand the donation model. Who is supposed to donate the \$5? Say I am an employee working for my company, and I am using NDoc. Should I donate the \$5 personally? Or should I ask my company to pay the 5\$?
When I wrote my original challenge to donate to Open Source projects, I wanted to avoid a
Suzanne Summers Sally Struthers For just five dollars you can feed
the kids of those poor Open Source Developers plea. As Scott points
out, monetary contributions are far down on the totem pole of
contributions. For the subtext project, I added a Contribution
that discusses several ways in which developers contribute should they
feel the desire.
I think it is the project leader’s job to make the barrier to contribution as low as possible.