James Dickens wrote:
perhaps project approval is just too easy for Sun's pet projects.
Why should it be hard for any project? Perhaps "Project Approval"
is the wrong term - this process is not supposed to indicate any
stamp of approval of a proposed solution or exclusivisity - just
that there's enough people interested in it to set aside a section
of the opensolaris.org website and a mailing list/forum for further
discussion. "Project Hosting Request" would be a better description,
as it's akin to asking for a spot on sourceforge for project hosting,
not asking for endorsement of the project goals.
+1 to this does not say "The Companion CD must be the one and only
way of distributing packages" or even "The current Companion CD
is the right model". All it says is "This is something related to
opensolaris which can have it's own section on the website and mailing
list." It doesn't preclude any other projects, presuppose any
conclusions, just says "Let's talk" - and clearly there's a lot of
people who want to talk about this, including you.
As for Sun's pet projects, I don't see how that has any relevance
- the ksh93-integration was certainly not one of Sun's pet projects,
and it sailed through. I doubt you'ld have any problem getting a
second for a Blastwave project if you decided you wanted to run the
blastwave mailing lists through opensolaris.org instead of blastwave.org.
And even if it was easier for Sun, so what? Given that all that
creating a project does is provide web space & mailing lists on
servers that Sun is providing and maintaining, would it be so terrible
that Sun is making use of these services to provide the community
with more information and opportunities for participation than they'd
otherwise get?
--
-Alan Coopersmith- [EMAIL PROTECTED]
Sun Microsystems, Inc. - X Window System Engineering
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
