Justin Erenkrantz wrote: > Taking a look at the constitution for a sec: > --- > ARTICLE VII. Community Groups > > 7.1. Purpose. In order to promote a diversity of activities within the > OpenSolaris Community and to provide a means for self-governance > within those activities, the OpenSolaris Community is held to be > composed of Community Groups that are initiated by the OGB for the > purpose of focused management and accomplishment of a given set of > activities. Community Groups are, in turn, responsible for initiating > and managing projects to accomplish those activities. > --- > > If the CGs aren't reporting in some form back to the OGB, then it's > impractical for the OGB to know what's going on - other than > subscribing to every list and doing micro-management. That simply > doesn't scale. (In the early days of Apache, we didn't do the > reporting scheme; but we've now learned that it's essential - and is > often as good for the community writing the report as it is to the > Board to know what's going on.) > > More broadly, the CGs don't have a license to do whatever they choose > to do - they are still responsible to the OGB in demonstrating that > they are following 'the purpose of focused management and > accomplishment of a given set of activities'. A reporting scheme > would demonstrate that. -- justin
+1 Sounds like a good amendment. You should add it to the bug list. Projects should have to file at least an annual report to their sponsoring community groups, and community groups should have to file a report to the OGB. This will have the effect of pushing leadership, structure and accountability down the chain and make the community stronger. In addition, it will make unproductive projects and CGs more visible, so they can be removed, and give the OGB more information to base their decisions on. Cheers, Jim
