I think most of your questions were already answered by others,
and on the technical side, they and you are more qualified than
I to comment.
James C. McPherson wrote:
> I've been strongly advised by some people within Sun that
> I should not request a PSARC review, let alone NV CTeam
> consideration - all because LSI is supposed to be delivering
> some code real soon now.
We can't help that you were given bad advice, but if that advice
came from your management we can't tell you to jeopardize your
career by defying your employer's instructions.
If there is a technical reason (as it sounds like there may be
with the trouble in migrating from one driver name to another),
I expect the ARC & C-Team to help you either find the best way
to resolve it (such as using the same name for both) or to come
up with a plan to handle this. The OGB can not and should not
overrule them on technical issues.
If it's a non-technical reason, then the OGB, as the community's
voice to Sun, can ask Sun management to resolve it, pointing out
that Sun is the steward of the shared tree, and needs to figure
out how to allow community contributions in, even if it chooses
not to ship them in the distros it controls. (We know about the
issue of the ON C-Team not allowing code in until there's a bugster
subcategory for it, with a Sun-employed responsible manager who
has agreed to assign resources to fixing bugs in it - the imminent
selection of an OpenSolaris Defect Tracking System to replace bugster
should resolve that issue shortly.) I believe this should be trivial
for a driver - just don't include that package in the ON deliveries
to the Nevada WOS docks.
--
-Alan Coopersmith- [EMAIL PROTECTED]
Sun Microsystems, Inc. - X Window System Engineering
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
