1. Topics
  2. project names

project names

Rob Sherwood
 

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 "boostrap-controller-1" and "bootstrap-controller-2"?  

I'm sure that this could be a long conversation, but fundamentally I agree with Chris's point.

- Rob
.


On Thu, May 2, 2013 at 11:39 AM, Chris Wright <chrisw@...> 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
sentiment.

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.

Thoughts?

thanks,
-chris
_______________________________________________
TSC mailing list
TSC@...
https://lists.opendaylight.org/mailman/listinfo/tsc
Ed Warnicke (eaw) <eaw@...>
 

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 could be resolved.


Ed

On May 2, 2013, at 1:49 PM, "Benson Schliesser" <bensons@...> wrote:

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 project? In either case, I think the TSC would be responsible for ensuring that project names comply with the spirit of your proposal.

Cheers,
-Benson


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

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.

Thoughts?

thanks,
-chris
_______________________________________________
TSC mailing list
TSC@...
https://lists.opendaylight.org/mailman/listinfo/tsc
_______________________________________________
TSC mailing list
TSC@...
https://lists.opendaylight.org/mailman/listinfo/tsc
Thomas Nadeau <tnadeau@...>
 

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

On 5/2/13 2:49 PM, "Benson Schliesser" <bensons@...> wrote:

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 project? In either
case, I think the TSC would be responsible for ensuring that project
names comply with the spirit of your proposal.

Cheers,
-Benson


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

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.

Thoughts?

thanks,
-chris
_______________________________________________
TSC mailing list
TSC@...
https://lists.opendaylight.org/mailman/listinfo/tsc
_______________________________________________
TSC mailing list
TSC@...
https://lists.opendaylight.org/mailman/listinfo/tsc
Chris Wright <chrisw@...>
 

* 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.
The initial project proposal comes with a name of their choosing that
must comply w/ our TBD guidelines (for example, not calling yourself
"OpenDaylight *" and perhaps not using obviously generic terms that
simply describe what project does).

The ODP-wide name, which is likely of the form OpenDaylight GenericTerm,
I'd open up defining GenericTerm to the wider community.

thanks,
-chris
Benson Schliesser <bensons@...>
 

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 project? In either case, I think the TSC would be responsible for ensuring that project names comply with the spirit of your proposal.

Cheers,
-Benson

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

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.

Thoughts?

thanks,
-chris
_______________________________________________
TSC mailing list
TSC@...
https://lists.opendaylight.org/mailman/listinfo/tsc
Chris Wright <chrisw@...>
 

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

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.

Thoughts?

thanks,
-chris
1 - 6 of 6