I think 2 is going to be implausible at this late date. Ed

I've added a bullet to the Proposal Page pointing to the Project Lifecycle page: https://wiki.opendaylight.org/view/Project_Proposals:Main "Review the Project Lifecycle to get a clear picture of how p

Phil, Could you get the section numbers in the Lifecycle here: http://www.opendaylight.org/project-lifecycle-releases so that the references to them in proposals for edits make a bit more sense? Ed

I was simply seeking clarification as you sit on both the TSC and board meetings and could thus speak directly :) Everything is new and moving fast :) Ed

Actually... this suggests a possible suggestion to the board that they email such taskings to the TSC to the TSC list ccing whatever list the board has so everyone is on page :) Ed

Please find enumerated below the comments of the TSC on the Boards TSC-policies doc. In addition, please find attached a redline of that doc. This is an output of the 2013-04-25 TSC meeting. Please re

Happy to move to a more reasonable place… suggestions? Would it make sense to hang them off of: https://wiki.opendaylight.org/view/Main_Page before the 'OpenDaylight Project Documentation' section? El

Benson, The Project Lifecycle already includes this in the proposal. Clearly a naming problem (for example a trademark or branding or other issue) would preclude acceptance of the proposal until it co

In the TSC call today I was asked to aggregate the information currently put out there about the Model Driven SAL and send it out to discuss to draw greater attention to it. The initial email (there a

A few thoughts inline… I am a little concerned with this provision. Consider for example a vote raised over the Christmas holidays, with only three TSC members voting at all. The TSC charter is pretty

I was asked by the TSC to send out the Proposed Simultaneous Release Plan we discussed in todays TSC call to the list. You can find it here: https://wiki.opendaylight.org/view/Simultaneous_Release:Sim

One other thing to keep in mind, it's normal for a project to be responsible for it's own unit tests and 'local' integration tests (by local I mean integration among the bundles it provides). Clearly

I would like to propose that we hold the VTN project creation review and vote to accept it at the next TSC meeting (this coming Thursday June 13). The proposal is here: https://wiki.opendaylight.org/v

I would like to propose that we discuss and vote on the Simultaneous Release Plan: https://wiki.opendaylight.org/view/Simultaneous_Release:Simultaneous_Release_Plan_2013 at next Thursdays (June 13) TS

Guys, I put together a preliminary page of 'code prep suggestions' for new projects… not binding things, but rather 'so you are cleaning up your code to open source it… these are good things to think

Benny, There have been lots of folks who are talking about bringing OF 1.3 support. As we go into the Simultaneous Release process: https://wiki.opendaylight.org/view/Simultaneous_Release:Simultaneous

Benny, There have been lots of folks who are talking about bringing OF 1.3 support. As we go into the Simultaneous Release process: https://wiki.opendaylight.org/view/Simultaneous_Release:Simultaneous

The TSC today asked that we poll the community for those interested in bringing project they would like to see included in the first Simultaneous Release. The current proposed Simultaneous Release Pla

Kudo san, Might I respectfully suggest that we use a lower case convention for repo names? In this case that would be 'vtn' rather than 'VTN'. Would that be acceptable to you?

Excellent! :) I suspect the 'formal' process of joining once the TSC has approved the Simultaneous Release Plan will look something like adding yourself to the Simultaneous Release Plan wiki page in t