Since I already attend the OpenSolaris P-Team meetings as the
X consolidation rep, Bonnie asked if I'd give an update at this
weeks meeting on what the OGB has been up to and what policy
changes the P-Team should be aware of.
(For those not familiar with it, the OpenSolaris Program Team
(P-Team for short) is the representatives from each Solaris
consolidation releasing source to OpenSolaris - it's an internal
planning and communication meeting for coordinating source
releases and similar activities, not the OpenSolaris equivalent
to the Solaris P-Team (Product Team) which decides build &
release schedules and contents.)
A brief outline of what I figured I'd mention are:
- The Constitution has been approved, and OGB elected
- OGB Community holds the docs, ogb-discuss the public discussion
- Under the Constitution, most of the decisions are made
in the individual Community Groups, with the OGB handling
things such as community-wide policy and the creation/disposal
of the Community Groups, as well as conflicts between groups
or appeals of group decisions.
- Only Core Contributors get to vote in community votes.
- Contributors are listed on polls.opensolaris.org,
Communities can name Core Contributors or Contributors by
mailing the OGB Secretary (Glynn)
- The first example of this is the Project Creation Policy,
which the OGB has approved and is in the process of publishing.
- Communities get to decide on creating projects, notifying
the OGB of their decision to get project website/SCM/mailing
lists/etc. set up.
- The OGB is working on publishing a guide for Community Groups
to explain what they can do and how, and what the Constitution
expects of them.
- Current ongoing discussion in the OGB includes:
- Open ARC reviews
- Community reorganization
- Handling Communities with no Core Contributors
- Upcoming discussions in the OGB are expected to include:
- OpenSolaris C-Teams - open existing teams or create new open ones?
- OpenSolaris W-Team - committee formed of open C-Teams? (similar
to the Solaris P-Team, but since OpenSolaris isn't a Product, the
older WOS-Team name seems more appropriate)
- Things we suggest the consolidations start thinking about:
- OpenSolaris C-Teams (see above)
- OpenSolaris Defect Tracking (see tools-discuss)
- What to do when OpenSolaris wants to include changes that the
Solaris C-Teams may not want? (such as new code without a
Sun manager willing to take ownership of a bug category for
long term maintenance)
Anything else I should bring up? (I was thinking of something on
the order of 5 minutes, but after typing all that in, I may go a
bit long...)
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
