Keith M Wesolowski wrote:
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.
In this case, I think it's still a follow-on of the poor initial setup
of Communities - instead of a Xen community, we should have a Virtualization
community with Xen & qemu projects.
--
-Alan Coopersmith- [EMAIL PROTECTED]
Sun Microsystems, Inc. - X Window System Engineering
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
