On Thu, Nov 01, 2007 at 10:33:47AM -0400, Bill Sommerfeld wrote: > If a "GNU compliant" environment were to become a first-class or default > environment on solaris (in other words, if we expect a significant > fraction of users to put /usr/gnu/bin in $PATH), I'd think that a > logical extension of the precedent set in PSARC 2005/683 (which added > crontab variants to /usr/xpgN/bin) might be in order, resulting in a > general mandate to add non-conflicting GNU-compliant extensions to > the /usr/bin variants of tools found in /usr/gnu/bin.
All of this is true and makes sense, but the high-order bit here is that issues like this one need to be resolved in the appropriate technical forum: ARC review, code review, and so forth. I would not like to see the OGB become involved with this sort of issue except as an appeal of last resort; we do not have the appropriate technical expertise to evaluate the ramifications of these changes, nor do we have the bandwidth to evaluate the thousands of technical decisions made by hundreds of project teams. What we can do is ensure that we have processes in place which will lead to the creation of finished software that conforms to the community's values, and that those processes are followed at certain points in a project's life cycle. At this point in Indiana's lifecycle, this disagreement should be addressed within the project team, possibly with the assistance of the ARC. Prior to "completion" (whether by integration into some existing consolidation, formation of a new consolidation, or delivery of a product on behalf of the OpenSolaris Community), all of the appropriate reviews need to be completed successfully. But we aren't there yet, so it makes no sense that ogb-discuss is still being cc'd here. -- Keith M Wesolowski "Sir, we're surrounded!" FishWorks "Excellent; we can attack in any direction!" _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
