See https://wiki.opendaylight.org/view/TSC:Main for call information, agenda, and the like. Thnx, --dmm

Maybe make a "Core Architectural Principles" or similar after Hackfests (so it would be # 5). Then link your's off that? That way we have a place we can perhaps have discussions around this or other

Hi, Phil Robb is inviting you to this WebEx meeting:

Rob, we haven't closed on this yet but I have put it on the agenda for Thursday (which should be posted today (RSN)). --dmm

Did we settle on something here? If so, I didn't see it. My pref would be to extend our existing meeting rather than have another one, because we always loose time trying to make sure everyone is on

* Rob Sherwood (rob.sherwood@...) wrote: The problem we have right now is no clear path forward to a single core code base. As a consequence, we can't really even point would-be users or

It time frames are the problem, those can be adjusted. As I mentioned it is more important that we make progress in a timely fashion than the actual date of this or that (at least until we get to

Hi Dave, I definitely recognize that there is a lot of pressure (from press, developers, even from ourselves) to show that the daylight community can make progress and produce useful code, but I'm not

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?

Thanks for pointing this out. For those who haven't taken a look at this page, it has some reasonable principles. Also agree with Colin that these are general principles, not project specific. --dmm

The list of desirable features which you're asking for are at least partially documented here: https://wiki.opendaylight.org/view/OpenDaylight_Controller:Architectural_Principles Presumably we should

Yes, again an issue of degrees. Makes sense. BTW, it might not have come across in (b). but of course making progress is more important than any exact dates. That said I would like to resolve this

* David Meyer (dmm@...) wrote: Agreed, non-starter. I actually think this is quite similar to or at least a variant of what you've outlined in your proposal below. BTW, let's keep this to the

[04/29/2013] As you may know, there have been several proposals floated to deal with the problems created by the fact that we have two controller code bases. These include but not limited to:

As discussed during the TSC meeting of 2013-04-25, the TSC has the following comments on TSC_policy.doc: (i). Comment to the Board: The TSC recommends replacing the word 'mature' in

Hi Phil, In general Tuesdays work for me I don't have anything recurring that cannot be shuffled. / Chris From: Phil Robb <probb@...> Date: Thursday, April 25, 2013 7:15 PM To: "tsc@..."

5-6 EST is getting a bit late for east coast folks. --Tom From: Phil Robb <probb@...> Date: Friday, April 26, 2013 11:28 AM To: Thomas Nadeau <tnadeau@...> Cc: "tsc@..." <tsc@...> Subject: Re:

2:00pm PDT on Tuesdays works for me generally, but I have a conflict on 5/7 till 2:30p. Best, abhishek

Hi Tom: Thanks for your quick response. Some of the attendees have a conflict at 1:30pm PDT on Tuesdays. Would 2pm PDT on Tuesdays work? We will start after next week (on May 7th). Does 2:00pm PDT

From: Phil Robb <probb@...> Date: Thursday, April 25, 2013 10:15 PM To: "tsc@..." <tsc@...> Subject: [OpenDaylight TSC] Increasing TSC meetings to twice per week Can we make it at 1:30? If we keep it