Hello TSC Members: Here is the meeting access information for today's meeting. This is the same information currently on the wiki: When it's time, start the meeting from here: https://meetings.webex.c

After looking in depth into the implications of Colin and Dave's proposal, we ran into a bunch of concerns. Attached is a proposal which we believe addresses those concerns while trying to keep to (at

Folks, As TSC members will recall, I set a date of 05/13/2013 to have proposals for the single controller project on the table, and Rob asked a few questions about this on today's TSC call. Now, while

Hello Everyone: To provide a clean change to the TSC meeting invitation as we move from 1 hour to 2 hour meetings, I will be canceling the original meeting, and then sending a new invitation for the 2

This event has been canceled and removed from your calendar. OpenDaylight TSC Meeting OpenDaylight Technical Steering Committee meeting. Please hold this time for the weekly OpenDaylight TSC meeting.

more details » OpenDaylight TSC Meeting Meeting URL: https://meetings.webex.com/collabs/meetings/join?uuid=MA3SRND964PIX06V2LS3SXX3RE-9VIB Access Information Meeting number: 194 548 370 Meeting passwo

* Kyle Forster (kyle.forster@...) wrote: This is a community effort. The whole premise of Opendaylight is founded on that tenant. We have project lifecycle and charter language to protect this. What y

* David Meyer (dmm@...) wrote: I absolutely agree here. It is fundamental to the functioning of our community. That's right. The path forward for "DE plan in new repo" is a project proposal which, ass

I'm going to put the new repository question (as outlined by Kyle Forester in an email of Wed, May 15, 2013 at 7:04 AM) to a voice vote on the TSC call on Thursday. The options are: [] Dixion-Erickson

All, As you know today (05.14.2013) was the day on which I wanted to have the single controller code base issue resolved. What I had said is that if we couldn't get the projects to agree on a way forw

I posted a question on the discuss list. However, I have a variant of the question for the TSC and would appreciate some clarification: What in our current/approved project lifecycle describes the cur

All, During the board call this afternoon I outlined the issues that we have been facing around repositories, projects and committer lists. After an hour of thoughtful and spirited discussion the foll

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. T

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

Hi Ed: Is there also a similar page for concurrency model used by the controller project? I was investigating porting of net-virt host-tracker to controller (using SAL as the south bound interface), a

Hi Ed - Thanks much for this. A question that came up that I wanted to reflect over on list -- which component of the model driven SAL is intended to do reconciliation in the case where you have multi

Resending with edits provided from folks like Chris and Dave. --Tom Email-based or Proxy-based Voting This proposal amends the existing TSC voting procedures that stipulate that voting by TSC members

Hello TSC Members: Please find the meeting minutes attached. Phil. -- Phil Robb Director - Networking Solutions The Linux Foundation (O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb

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

HI Alejandro, The current tests in the controller project are using JUnit for the individual bundles, and separate integration tests are written in their own bundles using Pax-Exam. Whenever a commit