John, (Thanks for listing all the projects!) My 2 cents...
Starting with what you mapped out, I took another stab at this. And put it at the bottom of: http://www.genunix.org/wiki/index.php/OGB_2008/010 I had problems with SIGS and Special CGs. I don't see the need for additional classifications, and would rather have a general theory of community organization, than a special one :) In addition, I took a stab at organizing things more logically from an external first time users perspective, than the way things may be organized within Sun. I think it's also important to get rid of acronyms were possible, since they don't translate well. I got things down to 26 top level communities with projects and sub-projects below that. As a starting point, if we agreed on a set of communities, we probably could just have the current projects decide for themselves where they wanted to be placed, and move on from there. BTW. I think we should plan to remap things every two years. We are moving fast. Cheers, Jim +++ ==================================== Community Project Sub-Project ==================================== == Communities === Advocacy and User Groups Appliances Applications Architecture and Process Desktop Device Drivers Distribution Documentation Emerging Platforms File Systems Governance High Availability Cluster High Performance Computing Internationalization and Localization Networking Observability Performance Power Management Security Software Porting Storage Systems Administration Testing Tools Virtualization Website John Plocher wrote: > John Plocher wrote: >> (I'll post PART 2 [specifics about a transition] in the morning - >> there are not enuf hours in the day...) > > So it isn't morning anymore... > > My "Part 1" provided a high level overview of a community structure > where there were several types of "Community Groups" (User Groups, SIGs > and Components), as well as PROJECTS, which were the mechanisms whereby > CGs actually performed "work". Two key parts of this proposal are that > PROJECTS can themselves spawn sub-PROJECTS and that PROJECTS are the > incubators for new CGs. > > The following is a first-pass whack at taking all of the 300 or so > existing Community Groups, User Groups and Projects and reorganizing > them into a more manageable structure. > > Key to my reorg was an attempt to put PROJECTs under the COMPONENT > where they integrate rather than under the SIG where they get talked > about. Some existing Projects got turned into umbrella PROJECTS, > as did some Community Groups. I didn't look too hard for dead > CGs and Projects, though I noted them when their deadness jumped > out at me. If I misfiled tings, or if I missed any obvious-to- > everyone-but-me things, feel free to correct the wiki page > http://www.genunix.org/wiki/index.php/OGB_2008/009 > > > I count > > 2 "Special CGs" > 67 USER GROUPs > 8 SIGs > 9 COMPONENTS > --- > 86 top level Community Groups > > -John > > > > ==================================== > CG TYPE > CG NAME > PROJECT NAME > PROJECT NAME > ====================================
