All, I will be finishing up the draft req's I have researched for the ports project this weekend. There are some very fundamental changes I have included which changes how software distribution works on Solaris today. Software management is much, much more than simple fetching, and this document attempts to encasulate this as much as possible.
I will have it completed and posted up so everyone can view and make comments by this coming Monday morning. I feel that getting this out as soon as possible is very important. Thoughts? Steve On 5/4/07, Brian Gupta <brian.gupta at gmail.com> wrote: > > I am OK with all of this, with partial reservations on [5]. My > > reservations are not based on the substance of [5], but on the > > logistics of [5]. I am operating under the assumption that > > defining "core" Solaris is probably a task to be shared with Sun > > Microsystems, Inc., whereas defining "core" OpenSolaris would be a > > task to be delegated to the Community, or a Community-delegated > > Working Group, or any other such Community-based entity. > > Can we agreed that the current consumer of the work done through > OpenSolaris.org is Sun Microsystems? (Through Solaris, and Sun's > downstream customers) > > The weekly builds are after all called Solaris Express, not > OpenSolaris express. > > That said, a Sun employee is by fact a representative of Sun, as their > involvement in OpenSolaris is paid for by Sun. I don't think there is > a need to make a distinction between Solaris and OpenSolaris at this > time. > > > But, maybe things have recently changed dramatically and I am simply > > unaware of these changes. > > Seems to me changes are afoot. > > > Either way, I will not hold the entire draft hostage to these > > reservations, so it's a conditional "Yes" from me, pending some > > future refinements and adjustments. > > Great. Anyone else? > _______________________________________________ > ports-discuss mailing list > ports-discuss at opensolaris.org > http://opensolaris.org/mailman/listinfo/ports-discuss >
