Alan Coopersmith wrote: > Once the community re-organization is complete, the OGB will > send out a notice to each community explaining the new process. > Each community will have 30 days from this notice to notify the > OGB secretary of their nominations for community facilitator, > ... reams of manual processes with no tools to help out...
Can we *please* build this functionality into the web app? Making this a manual process when we already have most of the membership tracking tools built in seems shortsighted. (i.e., we already have ways of endorsing communities, becoming observers, etc - just expand on these ideas to make the role management another online feature.) See http://www.opensolaris.org/jive/thread.jspa?messageID=70236𑉜 for more thoughts on this topic. > seconded by an existing Contributor or Core Contributor of the > community. This will cause large volumes of email traffic on many aliases - is this what is desired? It also can't bootstrap - who is the initial Core Contributer in a community who can do this seconding, and why is it needed on every individual and not simply on the final list? This all seems very process-heavy. > simply submitting the entire set of PSARC licensees... > is not acceptable. This seems arbitrary and uncalled for. Most of the PSARC licensees ARE involved with open projects and with closed projects that are transitioning to open. Having them as community contributers (but not core) should pose no problem. What specific problems are you seeing today because of this? (Note that my call for clarification and/or contributer additions before the election garnered no responses....) -John
