I think any project that originates from an established code base, instead of growing organically, is going to experience some pain during a transition from one development model to another.
If Apache's governance model isn't suitable, have any others been considered, or tried? Regards, Peter. ----- Original message ----- > On 09/ 7/14 12:24 AM, Peter Firmstone wrote: > > 1. Document your governance model, I'm a member of an Apache project, > > we have clear rules that assist in resolving differences > > Unfortunately, OpenSolaris adopted the Apache governance model and it was > a poor fit (Apaches rules for governing a large body of loosely related > projects didn't map well to a community trying to generate a single > unified OS) and too heavy-weight at the time it was introduced. A big > problem was driving things the wrong way around - we built out all this > governance structure and then hoped people would show up to use it, and > they saw more overhead than benefit and were turned off by it. > > That's left the OpenSolaris offshoots wary of governance and refusing to > admit that some level is necessary for ensuring decisions get made, and > thus left them floundering and directionless. > > -- > -Alan Coopersmith- alan.coopersm...@oracle.com > Oracle Solaris Engineering - http://blogs.oracle.com/alanc
_______________________________________________ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
