Alan Burlison wrote:
> "Endorse" suggests to me at least a degree of approval,
What is the underlying intent? We have two types of CGs
at the moment - ones that act like consolidations and ones that
act like enthusiasts (working definition: one has a primary focus
on a code repository, the others focus on attributes that may
cross many such repositories)
An example:
The ON Consolidation has a bunch of interested/related CGs:
DTrace, BrandZ, Documentation, Device Drivers, MDB, Security, ...
Looking at the projects under ON, there is a bunch of overlap:
DTrace Provider for NFSv4
IPSec Tunnel Reform
...
What do we think should happen? What are the "verbs" that connect
each of these entities? Both ON and DTrace have a stake in the
DTrace Provider for NFSv4 Project...
IMO, ConsolidationCGs should own Projects that are focused on
integrating changes back into its repository, while EnthusiastCGs
spawn Projects to create policies, documents or other artifacts that
can be [applied to/reused by/...?...] the various ConsolidatrionCGs.
In the above example, this would mean that the DTrace CG drives the
evolution of DTrace by producing ARC umbrella cases, roadmaps and the
like; its people then go off and create Projects under ON to actually
implement that vision in the ON consolidation.
Or are you thinking of something else?
-John
