Date 1 - 2 of 2
[OpenDaylight Discuss] Results of the OpenDaylight board call of 05.15.2013 and its relationship to the issues we've been discussing
toggle quoted message Show quoted text
I want to re-iterate Big Switch's position that we're against "top down" TSC or Board votes on technical design and implementation questions, and we feel the current issue falls in to that category. The communities we've found successful are the ones that have strong processes, but rely on volunteerism and leaders close to the code to drive technical direction.
I understand the concern that we've given ourselves a deadline of Q3 to produce an initial release. However, on behalf of Big Switch, we feel that in the trade-off between the scope, date and community building, we'd put community first. Let those close to the code come together and sort this out, and keep our role as a TSC focused on removing the barriers that would prevent that from happening bottoms-up.
So, even though I personally believe that the net-virt code base is the better technical starting point to get the most mature code fastest, I'm going to _abstain_ from tomorrow's vote and would encourage the other TSC members who are concerned about this process to do likewise. There is are healthier ways to solve this.
PS @Chris: the feature of pushing modules to nexus is actually a function of maven, not OSGI
On Wed, May 15, 2013 at 10:13 PM, Chris Wright <chrisw@...> wrote:
Chris Wright <chrisw@...>
* Rob Sherwood (rob.sherwood@...) wrote:
PS @Chris: the feature of pushing modules to nexus is actually a functionYes, I know. The point being that the bundle <-> repo connection is
papered over by as build.
|1 - 2 of 2|