Excerpts from linuxchix: 8-Oct-99 Re: [issues] Good and bad r.. by
[EMAIL PROTECTED]
> 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?)
Yep. www.worldforge.org
> 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.
Got that. We even have an infrastructure group.
> Role 2: Code "captain" -- integrates patches, watches all
> commits, and has overall responsibility for the quality of
> the code.
We've got a "leader", but he doesn't really watch everything. Each
section pretty much has someone in charge.. worldforge has got a
lot of relatively separate bits
> Role 3: Bug database maintenance -- go through outside bug reports
> and add real ones to list for developers to tackle.
Since the only thing that we've released is a demo, we don't have
"bugs" per se, yet...
> Role 4: Documentation/web site maintenance -- often left
> unattended according to Brian. Good place to help for
> non-programmers.
We've got wiki, which is a real nice system for organizing and
allowing web-based editing of the site. Anyone who can edit
a page or section can give any other developer edit access to it,
so everyone can document their own stuff.
> Role 5: Cheerleader/zealot/evangelist/strategist -- rah,
> rah, find people/customers to try/use the software; keep
> the big picture in mind.
None yet. We need to release something first :)
************
[EMAIL PROTECTED] http://www.linuxchix.org
