toggle quoted messageShow quoted text
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 could be resolved.
On May 2, 2013, at 1:49 PM, "Benson Schliesser" <bensons@...> wrote:
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 project? In either case, I think the TSC would be responsible for ensuring that project names comply with the spirit of your proposal.
On 5/2/13 2:39 PM, Chris Wright wrote:
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 appropriate and create confusion.
The code under "controller" project is named "OpenDaylight Controller."
The code under "net-virt-platform" project is named "OpenDaylight SDN
Controller Platform." While those projects may aspire towards those
names, they haven't, IMO, earned those names yet.
I suggest that names should be more like codenames (with appropriate
trademark vetting still done).
I suggest that the current names be changed to reflect the above
I suggest that the project lifecycle document be updated to take this
into account. Perhaps as part of Graduation review, we'd allocate a
ODP-wide name that's no longer just the code name.
So, for example, we'd have proposal named HotSidewalk, which upon Graduation
(based on it's functionality) becomes OpenDaylight EggFryer.
TSC mailing list
TSC mailing list