[EMAIL PROTECTED] wrote:
Inside Sun, there is a committee known as the
"Product Approval Committee" that has oversight
of what goes into Solaris. As this also impacts
what is putback into nevada, it has oversight of
OpenSolaris too, at present.
Is there any thought that the same will (or will not :) be
needed for OpenSolaris?
We've discussed this a few months ago, but since you're
apparently just coming to the table now with all these
questions...
I'm not sure we need a PAC per se - it's about product
definition and requirements (though perhaps Indiana will
have a PAC-like body for it).
What I think we will need is an OpenSolaris W-Team,
analogous to the Solaris P-Team (though using the
older name indicating it's the WOS team, instead of
the "product" team) - a place where all the C-Teams
send representatives to coordinate cross-consolidation
issues & projects, like determining which compilers
are to be supported by all the consolidations, what
the build schedules are (build number N occurs on
which date?) or implementing things like Secure-by-Default
across all the consolidations uniformly. I'd like to do
even a better job here than the Solaris P-Team has,
where things like SMF conversion are still hit and
miss as to which C-Teams have done it yet, and some
consolidations build with no-exec stacks and others
don't.
What should OpenSolaris do if the Solaris PAC says
"no" to something we want in OpenSolaris (given that
going into nevada is the only way to get there at
present)? Or vice versa, if the Solaris PAC said
"yes" to something that OpenSolaris doesn't want?
The Solaris PAC is free to fork the OpenSolaris source
tree to create a Solaris product with whatever changes
they do or do not want, and will almost certainly have
to do so at some point. That they haven't planned for
this is a sign how little they've thought about what
OpenSolaris really means to the way Solaris is built.
--
-Alan Coopersmith- [EMAIL PROTECTED]
Sun Microsystems, Inc. - X Window System Engineering
_______________________________________________
opensolaris-discuss mailing list
[email protected]