On Jan 20, 2008 6:24 PM, John Sonnenschein <johnsonnenschein at gmail.com> wrote: > > On 20-Jan-08, at 12:53 PM, Shawn Walker wrote: > > > As part of encouraging the sustained growth and success of > > community-based distributions, it is highly desirable that a new > > project oriented towards ON Community Group developers be created. > > This new project would maintain a branch of the main ON tree that > > integrates patches from community developers on a rapid basis as they > > are approved for inclusion. It will build the resulting source tree on > > frequent basis (to be determined, with the initial goal being weekly). > > This will allow community developers to quickly see and test the > > results of their contributions while encouraging innovation and > > providing an easy method for developers to obtain feedback from other > > community members. > > This paragraph sounds suspiciously like a fork of ON to me. > > perhaps Shawn would like to clarify; If patches are rapidly included, > sidestepping sponsorship ( which I am assuming Shawn means ), would > that not also sidestep ARC and code review ?
As Roy Fielding pointed out, neither ARC nor C-Teams are technically applicable to OpenSolaris. As such, nothing would be sidestepped ;) > What then if ARC derails the case, or a show-stopper bug is found ? > Will the patches be rapidly removed ? What if a project under the CG's > scope has come to depend on the functionality. The choices are to > keep the patch in the tree ( violating ARC ), or to remove it ( and > possibly damage some project ). > What if the sky falls? But seriously, from what I understand, projects internal to Sun already face the same problems. As I mentioned before it is impossible to "violate ARC" for OpenSolaris projects. These problems aren't really unique either; they are problems every open source project faces. Cheers, -- Shawn Walker, Software and Systems Analyst http://binarycrusader.blogspot.com/ "To err is human -- and to blame it on a computer is even more so." - Robert Orben
