The purpose of this thread is threefold. First, I would like to start a focused discussion, as to why people would want an OSH (OpenSolaris Hosted) binary set, so that we can accommodate the widest set of needs with our efforts. (OSH as a hopefully non controversial working name).
Second, this thread is meant as an educational thread, so that those who aren't convinced that there is a legitimate need for OSH, have been given the full story. Third I have started receiving questions regarding what the idea of an OpenSlaris distro is and what it's goals are. (In another thread, that I am trying to keep focused.) It is very important that these particular threads that I am starting keep focused for reasons that I hope are self explanatory. If you feel that there should be a new related thread of discussion, but potentially disruptive, please contact me offline, and I will work with you to start the thread, or point you to an existing thread that is already discussing said issue. (Even if it's not potentially disruptive.) Various drivers behind an effort to produce OSH. 1) There is a desire for a minimal/core OpenSolaris distro, that other distro packagers can leverage to create their own distros. Building a distro from this core *may*, in the future, allow other distros to also be hosted at OpenSolaris.org. This OS core must, for the sake of practicality, allow layers to be added on top to get to Nevada. 2) Currently their is no Open development platform. The only allowed development platform is, a closed source, proprietary platform: Sun Solaris (Express). Ideally guardianship for this development platform should be moved into the community. (Yes this seems in opposition to bullet #1, but keep reading) 3) Currently the barrier of entry to getting involved with OpenSolaris is high, both from a conceptual point of view, as well as a work required point of view. (I can't just download a ISO and install an up to date dev platform) 4) Currently the barrier to entry for immigrants is high. Driver support, that shall we say "does not lead the field". Installation and configuration can be confusing to those that have not studied Solaris. I think these are generally acknowledged as goals in the community, but this is where we have a distro that focuses on this issue specifically. 5) Although AOL has proved that mass mailings of optical media can be made into a scalable distribution model, this only worked because AOL self updated upon install. OpenSolaris needs a quicker and simpler distribution method. (Which allows free mirroring of ISOs, binary and source packages, without lengthy legal reviews. This ties into the desire to have a completely unencumbered base distro set) 6) Sun (Ian/Indiana/Others) wants a second Solaris distro that will be the Fedora to Sun's RHEL (Solaris). They wish to do this and still leave a clear migration path from one distro to another. (Unlike Fedora). ;) 7) Currently there isn't a method for non-Sun distros to offer optional non open source bits. We would want to establish a standard and precedent for doing so, that all distros could leverage. (I'm thinking mostly HW support issues). 8) Currently, by continuing to use closed source bits as the standard, there is minimal incentive to close (open?) the loop. 9) Current HW requirements are a bit on the high end. I can't run this on an old 386, or for that matter on an old P/PII I have lying around. I feel that if we set our goals properly we could accommodate all these desires and wishes within the Scope of a single "approachability" CG (community group) project. Some possible design criteria that could allow this to come to pass: 1) A goal to make all components fully modularized packages/components. This even applied to the ON (OS/Networking) consolidation. This will allow alternate distributions to very easily pick and choose components for their distribution. (Distributions would of course be free to ignore the reference and use their own build/packaging methods) This would also allow for the building of a very compact miinimal core, using the same components that are used to construct a "Complete" user focused distro. (Meeting the needs and desires of multiple groups, e.g. appliance builders, distro builders, hobbyists working w/ old HW, etc.) 2) Be strict about making the System fully Open Source (This is mandatory for this to be an OpenSolaris project). Optionally allow a method to pull in closed source bits if desired by the installer, or distro packager. (This would eventually require involvement by technical as well as legal participants). This said we would have to work out a prioritized roadmap, that covered everyone's desires. Please feel free to contact me offline, if you feel that there are flaws in what I have laid out. I don't want to clutter this thread with a large amount of dissident traffic. If you must reply on list, please completely change the topic. (No "was".) Let's please try to keep on topic. (Read the subject of the thread before hitting send). Please start reaching out to your User groups and see if we can find more interested parties there. Finally, I have decided to add a trailing tag of [OSH-thread] so that going forward anyone interested/not-interested in these threads that for now, I am starting, can setup an appropriate mail filter. Keep in mind that the only CG that I are focused on living in is "approachability" I think in the short term we will work in the general approach-discuss list, as time goes on I expect a project to form in approachability, and then when enough interest is established the project would earn promotion into a full OSCG (OpenSolaris Community Group.) -Brian P.S. - Remember if you want a new related thread, I ask that you please contact me offline, so that we can keep this discussions focused. _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
