Jenn wrote:
>>
>> Write your best specifications for the bits you aren't doing right now,
>> and find out the accepted way to advertise for helpers for open source
>> projects.
Could anyone clue me in on the "accepted way" to advertise an open source project?
Also, is anyone participating in an open source project right now that they feel is
really well-managed and organized? (So we can look at it as an example?)
----------------------------------------
Just for fun, I thought I'd pass on recommendations from Brian Behlendorf (of Apache)
in the book "Open Sources" on what he considers a minimum resource set for a project
of moderate complexity:
Role 1: Infrastructure support -- maintain mailing lists, web server, CVS, bug
database, etc.
Role 2: Code "captain" -- integrates patches, watches all commits, and has overall
responsibility for the quality of the code.
Role 3: Bug database maintenance -- go through outside bug reports and add real ones
to list for developers to tackle.
Role 4: Documentation/web site maintenance -- often left unattended according to
Brian. Good place to help for non-programmers.
Role 5: Cheerleader/zealot/evangelist/strategist -- rah, rah, find people/customers to
try/use the software; keep the big picture in mind.
For a small project of your own, if you want to open development to the outside world,
you can see that there's plenty to do in addition to the raw coding work. But I agree
with Deidre and Jenn, take it step by step and go for it. The whole process should be
a fun and educational challenge.
kathy g
************
[EMAIL PROTECTED] http://www.linuxchix.org
