Teresa Giacomini wrote:
> Glynn Foster wrote:
>   
>> Hey,
>>
>> Stephen Lau wrote:
>>     
>>> +1 from me
>>>
>>> I've always felt a direct ownership of a Project by a CG would create 
>>> more responsibility on the part of the CG to stay current with what's 
>>> going on in the project, and vice versa.
>>>       
>> I'm actually not sure I agree, and maybe my opinion touches on what Peter has
>> already expressed that the Community Group structure has failed. I'd actually
>> like to see *less* of a bond between Projects and Community Groups. There 
>> should
>> be an extremely low barrier to entry for project creation - rather than 
>> having
>> to even propose a project, any contributor should be able to JFDI. The 
>> project
>> will succeed depending on the number of people that gather around it and 
>> their
>> determination to complete it.
>>
>> We need to encourage the 'go knock yourselves out' mentality. The fact that
>> someone is interested in starting a project is a great thing and we need to
>> encourage that. The knowledge and experience they gain during the lifecycle 
>> of
>> that project will be invaluable to the OpenSolaris commons in general, even 
>> if
>> it proves to be a failure.
>>
>>
>> Glynn
>>     
>
> Aren't there some projects that might logically be owned by more than 
> one CG?  For example, the Starter Kit project would make sense under the 
> Academic and Research Community, the Documentation community, the 
> Advocacy CG and possible more.  Why force it to align with on CG?

Great example.

The Starter Kit is certainly a Documentation Project managed by the Docs 
CG.  It serves the Academic and Research Community and Advocacy, but 
neither of those CG's have the resources to coordinate that work, the 
Docs CG does.

OpenSolaris is highly integrated in many respects.  CG's will always 
depend on other CG's or their Projects, and thats a very healthy thing, 
but there is a difference between needing something else and controlling 
something else.

Take for example GNOME/JDS and X.  GNOME/JDS will always depend on X, 
but they are still separate efforts which have different development 
teams.  GNOME/JDS may ask things of X, X may ask things of GNOME/JDS, 
but they are never-the-less very independent development efforts.

benr.

Reply via email to