John Plocher wrote: > Thus my open ended questions to you - given the state of the FOSS > guidelines, the apparent intent of both these projects to be > there for our customers, but not be part of the core OS, as well > as the ongoing conversations about a future repo based ecosystem, > what FOSS Integration rules make sense for projects like these? When we have a "future repo based system", we can have that discussion. For now, we have the BWOS (Big Wad of Stuff in Sun parlance).
My personal view about this particular issue is that we need to maintain the ability to communicate to all users (not just administrators) as to the "stability level" for all items (and we are caught with the existing practice of "if not stated, its committed"). The man pages seem like the obvious place. Basically, if its not broken, don't fix it. It could actually be a place where OpenSolaris exceeds over its competition. One stop shopping (at least for maps) is a GoodThing(tm). I don't think this bit of the "FOSS guidelines" needs to be changed. Your broader point is a good one, that a number of these "guidelines" do need to be reconsidered. However, it doesn't seem wise to assume any reconsideration until it actually happens. What if our initial (or personal) assumptions are wrong? - jek3
