Hi, Speaking as the leader of the Systems Administration community, I'd have to say that the endorsement function is a manual process and doesn't change any community processes. It's a totally manual process where you select from a list of projects to endorse. I haven't updated it in a long time and when I last did I just selected a bunch of things that were of interest to what we were doing at the time. All it ends up doing is creating a list with links. It doesn't reflect a formal relationship or anything. As a matter of fact, I don't like where the list ends up on the page:( And have thought about removing the items in the list just because of that. It probably should do something more functional, but it's just a way to link to projects.
Octave --- Keith M Wesolowski <[EMAIL PROTECTED]> wrote: > On Mon, Mar 05, 2007 at 10:02:32AM -0800, Alan Coopersmith wrote: > > > The system for choosing core contributors is notably flawed in that > > it only recognizes people working with Communities, not Projects or > > distros. (For instance, Roland wasn't initially listed because > > This is not a flaw in the process but a flaw in the leadership of the > various Communities which should be following more closely the > various > Projects which are or should be relevant to their areas of interest. > > > ksh93 is a Project, not a Community, and hasn't been affiliated > with > > any Community groups, yet he's one of the biggest contributors in > > That's the defect - I'd like to know why the System Administration > Community, to name but one obvious example, has endorsed other > projects but not that one (it's their prerogative to make that > choice, > but it seems as likely as not that it represents ignorance or > incompleteness rather than a conscious choice). One would expect > that > with that recognition of the project itself would come contributor > and > core contributor status for some or all of the major participants in > the project, provided that it is seen to have made significant > progress toward integration. > > > reality. Similarly, is your qemu project affiliated with any > > community? If so, ask the leaders of that community why you > weren't > > included.) > > Exactly - that's the right place to start, not with the OGB and not > with the process itself. If the Community leaders are unresponsive > or > don't appear to have any sound rationale for denying endorsement, > escalation to the OGB may be appropriate. The OGB should never force > a Community to endorse a Project; presumably the Communities are the > repository of technical knowledge and leadership and are expected to > make value judgments about the viability and desirability of ongoing > work. But denying endorsement by failing to maintain awareness of > relevant projects, because of personality conflicts, or for other > reasons not related to a project's technical merit is a problem well > within the OGB's mandate to address. > > Suffice it to say that dealing with Community failure is one of the > deeper challenges facing the new OGB. Community leaders are advised > to put their houses in order sooner rather than later, and to seek > dissolution if adequate leadership cannot be found or a sensible > definition of scope cannot be agreed upon. > > -- > Keith M Wesolowski "Sir, we're surrounded!" > FishWorks "Excellent; we can attack in any direction!" > _______________________________________________ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Octave J. Orgeron Solaris Systems Engineer http://www.opensolaris.org/os/community/sysadmin/ http://unixconsole.blogspot.com [EMAIL PROTECTED] *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* ____________________________________________________________________________________ Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
