[Community] New working group, procedures

Eugene Eric Kim eekim at blueoxen.com
Sun Apr 1 23:55:20 PDT 2007


Drummond Reed wrote:
> +1. Every WG should have its own mailing list if it wants it. Chartering
> the WG, revising the charter, or any other major news involving the WG
> should be sent to the Community list.

Drummond, what Joaquin is proposing is that anyone who _proposes_ a
working group gets a mailing list.

I think we can borrow from the Apache model.  Apache has the notion of an
incubator, and "elders" from the community act as mentors to incubated
projects.  I like that model for IC, except we are in a different
situation from Apache.  Apache had a history of successful, sustainable
projects before adopting that model.  We're just getting started, and we
don't have that same history, not at the same level at least.  So it
seems a bit duplicitous to call anyone an "elder," in the sense of
someone who has fostered a successful project under (or over) the IC
upside-down umbrella.

All that said, I like the overall model, and I think we should be able to
adapt this model to fit our needs.  Thoughts?

=Eugene

-- 
=========================================================================
Eugene Eric Kim ................................... http://xri.net/=eekim
Blue Oxen Associates ........................... http://www.blueoxen.com/
=========================================================================


More information about the Community mailing list