On 18-Jul-08, at 10:36 AM, Glynn Foster wrote: > Hey, > > On 15/07/2008, at 10:09 PM, Jim Grisanzio wrote: >> I updated this again to reflect the removal of the Facilitator role, >> and I'm also recommending the removal of the Emeritus role. This is >> just an outline of an idea to give the infrastructure dev team the >> minimum information (roles, structure, relationships) they've been >> requesting for four weeks so they can continue working to build the >> applications to upgrade the site and support the gate migration. > > [snip] > > As I said on Jim's blog, I like this a lot more than some of the > others. > > As I see it, we have a couple of formal roles within our community > (which I've grouped accordingly) - > > - Contributor > - Leader > > - Member > - OGB > > A Contributor is *everyone* in the context of opensolaris.org. No one > would be involved or reading lists if they weren't interested, and > contributing to the success of the community.
I somewhat take issue with this, in as far as a casual browser may simply be interested in what all this "opensolaris" hype is all about, completely apathetic as to the success or failure of the project. ( They may also be antagonistic, but let's leave the trolls aside ). I'm not sure 'contributor' is something that we might be able to pin down with mathematical precision considering we seem to be moving towards wanting to grant the status to non-code contributions ( the practicality and cognitive framework leading to that decision being taken as axiomatic ... ). Is someone asking "my network doesn't work. why?" contributing to the success of the community? maybe maybe not. What about the guy that answers that question? The difference between the two may simply be the next similar email that comes out ( guy asking becomes guy answering) > Leader are those people with a stronger position in the community. > Leaders in the project sense may be ones making decisions and deciding > the direction of a project. They have respect from their peers that > has elevated them into a position of responsibility. Only leaders can > elevate other people to that position, to share in the > responsibilities. What of communities / projects / groups with a vacuum of leadership? Who elevates leader #0 ? > Both of these roles have a set of attributes - > > - can edit web pages > - can administer mailing lists > - can commit code > > Members are those who want to be associated with the OpenSolaris > community, and care about its long term success from a social point of > view. Membership is voluntary, and based on an individual's > contribution to the community. Members are approved by a small > membership committee (the tick boxers), but recommended (reference) by > existing Members. They can vote in community wide elections, but don't > necessarily have a say in many of the operational parts of the > community (ie. Projects). Members elect OGB board representatives, who > are given the responsibility for the long term success of the project, > ensuring that it has all the resources it needs to be that success. > > The rest of Jim's proposal starts to identify the high level groups. I > also believe this comes close to my thoughts - > > - Projects > - Communities/SIGs > - User Groups > > Very, very close. I've added Release Team and ARC as stand outs, > because I believe those are fundamentally important in getting our > software out into the hands of our users. +1 to this. release and ARC have a unique over-arching position of making sure that we have something to coalesce around and that it's high quality, respectively. Perhaps to reflect this, another supergroup, something like "summit" , designed such that leaders of other, diverse groups come together to accomplish a specific goal ( like fitting all that stuff on a CD, or evaluating architectural impact ) ? -John -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part URL: <http://mail.opensolaris.org/pipermail/ogb-discuss/attachments/20080718/9c90be7d/attachment.bin>
