Garrett D'Amore wrote: > Shawn Walker wrote: >> This is the sort of project that needs to stay in sync with whatever >> the ON community is doing so they can be aware of big gate or process >> changes, and so that they can work together. > > I don't like the idea of making this project formally subservient to the > ON Core Contributors (who are ultimately also its C-Team). The point of > this consolidation is to deal with stuff that has been *excluded* from ON.
Does this mean that the new consolidation has some sort of a "first refusal" agreement with ON? In other words, can you (or "should you") deliver via the new consolidation without bothering to see whether ON would reject you, or do you have to apply to ON first? I think part of the goodness of the consolidations that feed into the OpenSolaris distribution is that the software is made easily available. It's all packaged up and shipped properly. Thus, having projects that might consider this new consolidation deliver though an established consolidation instead, all else being equal, would be a good thing for all users and should be encouraged. How exactly do the products of this consolidation's work get distributed? And how does this consolidation encourage folks to do things with longer-term benefits? -- James Carlson 42.703N 71.076W <carls...@workingcode.com> _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
