[ogb-discuss] The OpenSolaris Constitution: (Really Rough) v2.0

Mark Martin storycrafter at gmail.com
Tue Oct 7 08:51:04 PDT 2008


For what it is worth coming from me:

On Tue, Oct 7, 2008 at 4:10 AM, Jim Grisanzio <Jim.Grisanzio at sun.com> wrote:

>
> Creating Communities, Projects, and User Groups
>  Overview: Groups can be created, archived, reactivated and changed. All
> groups are considered equal, and there is one process to create all groups.
>
> Group Creation Process
>
>    1. Go to http://defect.opensolaris.org
>    2. Create a new "bug" under Community > Infrastructure > Create with
>    the following information
>       1. Your opensolaris.org user ID (required)
>       2. Type (Community, Project, User Group)
>       3. Community Name
>       4. Title
>       5. Description
>       6. Leaders (opensolaris.org user IDs required)
>       7. Mailing List Requirements
>    3. Someone other than yourself with an Opensolaris.org user ID needs to
>    vote for the "bug" you just created. Group requests will only be accepted
>    once they have one or more votes from people other than the originator.
>    4. Wait. As someone becomes available, your request will be processed
>    by one of the admin team and you will be notified.
>
>
> Group Type Change
>
>
>    1. Go to http://defect.opensolaris.org
>    2. Create a new "bug" under Community > Infrastructure > Change with
>    the following information
>       1. Your opensolaris.org user ID (required)
>       2. Community Name
>       3. New Type (Community, Project, User Group)
>       4. Rationale/context
>    3. Wait. As someone becomes available, your request will be processed
>    by one of the admin team and you will be notified.
>
>
> Archiving
>
> >From time to time, a group may become dormant. But since it's never a
> desirable situation to have unmaintained infrastructure on the web, there is
> a process for archiving groups. If there has been no activity from a group
> for six months, or at the discretion of the OGB or its nominated committee
> acting in the interests of the community, the following may happen:
>
>    - Mailing list changed to 'no subscriptions' [note: may need to note
>    Jive forum status here too]
>     - Web page visibly tagged with 'Dormant'
>    - List of leaders/participants reset to zero
>    - SCM write disabled
>
>
> Reactivating
>
>    1. Go to http://defect.opensolaris.org
>    2. Create a new bug under Community > Infrastructure > activate with
>    the following information
>       1. Name
>       2. Reasons to activate
>       3. Leaders (preferably opensolaris.org user IDs)
>    3. Wait. As someone becomes available, your request will be processed
>    by one of the admin team and you will be notified.
>
>
> Mailing Lists
>
> Mailing list names should indicate purpose, and have one of the following
> suffices:
>
>    - -dev: developer discussion
>    - -discuss: general discussion
>    - -notify: notification alias for SCM putbacks
>
> Private mailing lists may be granted in exceptional circumstances, but full
> rationale is required and the OGB must approve. Although this process is
> intended to be essentially automatic, the OGB will form a committee with
> oversight and with the power to veto group requests if it is in the
> interests of the community. Finally, all notifications to bugs in Community
> > Infrastructure > Creation will be sent to group-creation at opensolaris.org
> .
>

I'm wondering if codifying the procedures and policy for group et al
creation is appropriate here.  As I think James C. alluded to, there's a lot
of detail here, and I worry that presenting this much detail into this type
of document will make changes or evolution of those procedures much more
difficult.  As this is a "constitution", ostensibly changing anything here
would seem a heavyweight ordeal.

How about something along the lines of "Creation of <<stuff>> is governed by
the current <<stuff>> creation policy, found at hxxp://
policies.opensolaris.org/stuff", and delegate ownership and management of
that either to a committee or just call out it's governance model here.

I'm not disputing this section's accuracy or importance, just respectfully
questioning its presence in *this* document with the default constitution
changing procedures required to change it.

Dissolution If the OGB is reduced in membership below the minimum of three
> members, Sun Microsystems shall appoint a new board.
>

Was there discussion about modifying this?  I can't seem to find it.

Respectfully submitted,
Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/ogb-discuss/attachments/20081007/e4bdea72/attachment.html>


More information about the ogb-discuss mailing list