Bonnie Corwin wrote:
> So everything you've said confirms that consolidations are not special 
> in this discussion.  They are simply large Projects.  They manage code 
> and they have processes for taking in code.  Projects that deliver to a 
> larger project don't need to be nested hierarchically or 'owned' by the 
> larger project.  Projects should simply exist.  Where each chooses to 
> deliver should not be part of a governance discussion.

I believe the only difference between a Project and a Consolidation is
that a Consolidation is that Consolidations have a specific place in the
hierarchy of delivering to a product.

I tried last year to define what Consolidations, C-Teams and a W-Team
were in the OpenSolaris world [1], and we didn't go far with that for
various reasons - I think now that we've accepted that at least part of
our collective effort is building a distro or family of distros, we may
be closer to being able to define this.

So my thoughts on this and the hierarchy are not fully worked out, but
their current half baked state is something along the lines of this:

- The OGB charters a top-level collective called "The OpenSolaris WOS".
  This effectively replaces the current Indiana Project collective and
  will run the W-Team for the OpenSolaris OS.   The W-Team will either
  charter or adopt other Projects as OpenSolaris Consolidations - these
  are most likely going to look like the current Consolidations - ON, SFW,
  Desktop, X, etc.   The W-Team will set the requirements for these
  Consolidations (ARC review, schedules for delivery to WOS builds, etc.).

- Every project that wants to deliver into "The OpenSolaris WOS" either
  finds a consolidation to accept it, or applies to the W-Team to become
  a consolidation itself.

Projects don't necessarily have to be associated with a consolidation,
especially ones in the experiment and refine stages, that aren't ready
to deliver.  They don't have to have a governance/hierarchical relationship
with an existing consolidation - but to get set up, they have to convince
someone they should be created - that could be a SIG, another Project, or
the OGB, though we'd prefer most projects not come to the OGB, and would
try to refer most to a more appropriate group to get started under.

[1] http://mail.opensolaris.org/pipermail/ogb-discuss/2007-July/002109.html

-- 
        -Alan Coopersmith-           alan.coopersmith at sun.com
         Sun Microsystems, Inc. - X Window System Engineering


Reply via email to