My 2 cents after reading the 50 or so messages on the topic ;^) Most of you are making this wayyyyy too complicated. I like Simon's idea, seconded by JimG. Make the top level of projects, and let the projects decide how to assign all the attributes and votingness and the top level group needs to come to the ogb with its process as Simon describes.
All the "collectives" and "roles" are things that each project can decide. We'll obviously have a few of the top level projects which are in the "collective" bucket, but how they assign "votingness" and other attributes should be up to them. This allows, as Jim pointed out, evolution. A number of you are attempting to solve the roles issue globally and it just won't work, as is evidenced by the number of counter-example emails bantering about. Finally, on the SCA, Sun will continue to require one when a participant donates "their code" which they could copyright (unless they want it only as part of the contrib/experimental repository of software). I don't understand why there's any debate on that. Other non-Sun, community-owned code with licenses that allow it to be used by products created from the OpenSolaris code repository will do so. Tim
