TSC@lists.opendaylight.org

Home Messages Hashtags Subgroups

Messages

Between

and

Re: project names

Chris - This makes sense to me. One question about implementation: who/what is the naming authority for projects? Would the project proposal suggest their own name, or would the name be assigned to a

By Benson Schliesser <bensons@...> · #93 ·

project names

I've been meaning to bring this up for some time now... I believe we should establish some guidelines on project names. The current bootstrap projects have named themselves in ways that are not

By Chris Wright <chrisw@...> · #92 ·

Re: motions and voting

I would be in favor of instituting wording to this effect. Thanks Chris for bringing this up.

By Rob Sherwood · #91 ·

motions and voting

I like the way this is handled in the OpenStack Technical Committee: Motions Before being put to a vote, motions presented before the TC should be discussed publicly on the development

By Chris Wright <chrisw@...> · #90 ·

Reminder: TSC call today at 1000 PDT

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

By David Meyer <dmm@...> · #89 ·

Re: Resolving the multiple controller code bases issue

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

By David Meyer <dmm@...> · #88 ·

Invitation to WebEx meeting: OpenDaylight TSC Meeting

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

By Phil Robb · #87 ·

Re: Increasing TSC meetings to twice per week

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

By David Meyer <dmm@...> · #86 ·

Re: Increasing TSC meetings to twice per week

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

By Rob Sherwood · #85 ·

Re: Resolving the multiple controller code bases issue

* 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

By Chris Wright <chrisw@...> · #84 ·

Re: Resolving the multiple controller code bases issue

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

By David Meyer <dmm@...> · #83 ·

Re: Resolving the multiple controller code bases issue

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

By Rob Sherwood · #82 ·

Re: Resolving the multiple controller code bases issue

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?

By Ed Warnicke (eaw) <eaw@...> · #81 ·

Re: Resolving the multiple controller code bases issue

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

By David Meyer <dmm@...> · #80 ·

Re: Resolving the multiple controller code bases issue

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

By Colin Dixon <ckd@...> · #79 ·

Re: Resolving the multiple controller code bases issue

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

By David Meyer <dmm@...> · #78 ·

Re: Resolving the multiple controller code bases issue

* 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

By Chris Wright <chrisw@...> · #77 ·

Resolving the multiple controller code bases issue

[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:

By David Meyer <dmm@...> · #76 ·

TSC comments on TSC_policy.doc

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

By David Meyer <dmm@...> · #75 ·

Re: Increasing TSC meetings to twice per week

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@..."

By Christopher Price <christopher.price@...> · #74 ·

14341 - 14360 of 14433

Home Hashtags Subgroups Terms