* Thomas Nadeau (tnadeau@...) wrote: Come to think of it, we don't actually have "the development" list. We have "the discuss" list, or "the TSC" list. Capturing the spirit here, it'd be

* David Meyer (dmm@...) wrote: That's boilerplate from the original. OpenStack has a TC (Technical Committee), which is built of PTLs (Project Technical Leads) and 5 community voted

Thanks Tom. A few questions/comments in line. --dmm

I have tried to capture the details of our discussion last week. Please comment on the proposal below so that we can amend the process as soon as possible. --Tom Email-based or Proxy-based

Thanks Chris. --dmm

* Chris Wright (chrisw@...) wrote: FYI, I updated the wiki landing page to include a pointer to the account system. The direct link is

* Aleksandar Miljusevic (miljusevic@...) wrote: It's editable now. You need to log in. Perhaps you simply need an account? thanks, -chris

The lead administrator for the OpenDaylight tools is Andrew Grimberg (cc-ed). In short, I would suggest making this a forward looking policy as opposed to an immediate implementation. I.e. keep the

In discussing this with Phil he pointed out that we need to bring the developer tools admins into this conversation before we make any decisions. Basically we need to know what is possible with our

Hello all, Is editing of the Controller Project's Modules/Bundles and Interfaces Page going to be open to the public at some point? Aleksandar Miljusevic

Fwiw, I'm very supportive of this with the caveat that it may hard to find neutral names for things and we may need to open it up to suggestions. Maybe using some sort of prefix like

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

From: David Meyer <dmm@...> Date: Thursday, May 2, 2013 2:51 PM To: "tsc@..." <tsc@...> Subject: Re: [OpenDaylight TSC] OpenDaylight TSC] project names Agree. The names should perhaps indicate their

That is the TSC with a proposed name from the project proposer, if you ask me. In principle, the TSC would keep the naming consistent. --Tom

* Benson Schliesser (bensons@...) wrote: The initial project proposal comes with a name of their choosing that must comply w/ our TBD guidelines (for example, not calling

Chris, >> 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

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

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

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

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