On Wed, Apr 16, 2008 at 4:50 PM, Shawn Walker <swalker at opensolaris.org> wrote: > On Wed, Apr 16, 2008 at 3:00 PM, Bill Sommerfeld <sommerfeld at sun.com> > wrote: > > > > On Wed, 2008-04-16 at 12:04 -0500, Shawn Walker wrote: > > > > We're talking in the context of Solaris Next, as I understand it. If > > > > the repository software is unable to deliver the functionality, then > Sun > > > > will likely find it hard to provide no matter how much I pay them. > > > > > > I'm still confused as to why software requirements are being proposed > > > to ARC instead of pkg-discuss. > > > > these requirements have architectural implications for the whole of > > solaris. they're in scope for the ARC. > > Yes, but they should be proposed to the pkg project, and then proposed > by the pkg project to ARC. > > The current way is backwards to me.
I just want to be clear that I am in no way attempting to impune anyone's character or actions here. As someone that has no relevant internal experience with Sun, and based on my own experiences with employers and open source projects, this process seems rather foreign to me. Specifically, there is no guideline or even suggestion on OpenSolaris.org that project contributors subscribe to arc-discuss as well as a project's mailing list. Nor, to my knowledge, is there anything that documents this "reverse-ARC" possibility for projects. I'm also concerned that having discussions outside of the primary mailing list for a project is going to create a gap in communication among OpenSolaris.org project members. In the case of ips, we are fortunate that all of the project leaders are likely subscribed to arc-discuss, are familiar with internal Sun processes, and understand the processes. This is going to be foreign territory for open source developers (such as myself) that are not used to processes like these. I'm not sure what can be done here to improve things for OpenSolaris.org projects, but I'm not certain how positively many developers unfamiliar with Sun processes might react to this process unless something is done to help guide them. Cheers, -- Shawn Walker "To err is human -- and to blame it on a computer is even more so." - Robert Orben
