Not sure if this has been proposed before or even it is at all feasible, but how about changing the last/first letter?<div><br></div><div>Quantum -> QuantuS, QuantuN, Cuantum...?</div><div><br></div><div>There are a plenty of options to go by.<br>
<br><div class="gmail_quote">On Mon, May 13, 2013 at 5:28 PM, Monty Taylor <span dir="ltr"><<a href="mailto:mordred@inaugust.com" target="_blank">mordred@inaugust.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
<br>
On 05/13/2013 11:03 AM, Doug Hellmann wrote:<br>
><br>
><br>
><br>
> On Sat, May 11, 2013 at 5:48 PM, Anne Gentle <<a href="mailto:anne@openstack.org">anne@openstack.org</a><br>
</div><div class="im">> <mailto:<a href="mailto:anne@openstack.org">anne@openstack.org</a>>> wrote:<br>
><br>
><br>
><br>
><br>
> On Sat, May 11, 2013 at 3:12 PM, Monty Taylor <<a href="mailto:mordred@inaugust.com">mordred@inaugust.com</a><br>
</div><div><div class="h5">> <mailto:<a href="mailto:mordred@inaugust.com">mordred@inaugust.com</a>>> wrote:<br>
><br>
><br>
><br>
> On 05/11/2013 04:07 PM, Asher Newcomer wrote:<br>
> > Or even better, just continue to call it openstack networking.<br>
> The code<br>
> > names only serve to confuse the uninitiated. They needlessly<br>
> steepen the<br>
> > learning curve and slow uptake.<br>
><br>
> The problem with OpenStack Networking (or getting rid of<br>
> codenames) is<br>
> seen with pre-incubation->incubation->integrated cycle.<br>
><br>
> A project cannot call itself "OpenStack Foo" until it actually _is_<br>
> openstack foo. So any new project by necessity has to start off as<br>
> something else.<br>
><br>
> But - if we then require them to drop that name and become<br>
> openstack foo<br>
> when they become incubated or integrated, then we've got what's<br>
> become a<br>
> stable project with a decent amount of contributors renaming itself.<br>
><br>
> Every. Time.<br>
><br>
> The code names aren't just cute. I kind of wish they were,<br>
> because it<br>
> would make several things much easier if we could just ditch<br>
> them and do<br>
> a pure openstack. code namespace. But the reality is that it<br>
> gets really<br>
> really tricky to deal with a bunch of things if they go away.<br>
><br>
><br>
> I told Monty and the TC this at the Summit (sorry I couldn't attend<br>
> the session about code names). I find this trickiness a weak<br>
> argument in the face of the invented names that are getting to be as<br>
> bad as U.S. pharmaceuticals. Plus it forces us to put a "lookup"<br>
> table in the docs forever. [1] Let's find a process for naming that<br>
> meets a few reqs:<br>
> - describes the service<br>
> - goes through a legal review<br>
> - enables new eyes to understanding it by reading the English word<br>
> that the service represents (that can be translated into a<br>
> meaningful word in other languages)<br>
><br>
> If we have to preface with Stackforge to indicate pre-incubation,<br>
> that's fine. Use Incubating or some such to indicate incubation.<br>
> Meaningful words have meaning.<br>
><br>
><br>
> +1<br>
><br>
> Use a namespace package "openstack" then each project has a unique<br>
> package under that for their meaningfully named package (compute,<br>
> networking, etc.).<br>
><br>
> We only have to rename projects if they start out with "bad" names to<br>
> begin with. Projects that want to be integrated should be developing on<br>
> stackforge and using the openstack namespace package.<br>
<br>
</div></div>It's just logically infeasible. If we were to make that choice, I'm<br>
pretty sure we'd have to stop everything that everyone is doing and just<br>
deal the fallout from doing it.<br>
<br>
In any case - we did have a session on this at the summit, and we did<br>
lay out a strategy for moving forward. The etherpad is here<br>
<br>
<a href="https://etherpad.openstack.org/ProjectsReNaming" target="_blank">https://etherpad.openstack.org/ProjectsReNaming</a><br>
<br>
tl;dr - we are going to rename quantum to a new codename, and we are<br>
going to do our best as a community to lessen the external usage of our<br>
codenames.<br>
<div class="im"><br>
> I acknowledge we still have to indicate what commands, daemon names,<br>
> and so on are related to a particular service. That issue is also<br>
> fixable with some resources and effort and pays off in easier<br>
> adoption and understanding.<br>
><br>
><br>
> The unified command line project will resolve the command issue because<br>
> all commands will be "openstack $noun $verb" (end users shouldn't have<br>
> to know which OpenStack component owns a resource in order to operate on<br>
> it via the command line). Daemon startup scripts could use a similar<br>
> framework, or just a naming convention ("openstack-compute-api",<br>
> "openstack-network-api", etc.).<br>
<br>
</div>I agree - having the unified command line client will be very helpful to<br>
lessening our externally-facing usages of code names.<br>
<div class="im"><br>
> Doug<br>
><br>
><br>
><br>
> Anne<br>
><br>
> 1. <a href="http://docs.openstack.org/grizzly/openstack-compute/install/yum/content/terminology-codenames.html" target="_blank">http://docs.openstack.org/grizzly/openstack-compute/install/yum/content/terminology-codenames.html</a><br>
><br>
><br>
><br>
> > On May 11, 2013 3:59 PM, "Davanum Srinivas" <<a href="mailto:davanum@gmail.com">davanum@gmail.com</a><br>
> <mailto:<a href="mailto:davanum@gmail.com">davanum@gmail.com</a>><br>
</div><div class="im">> > <mailto:<a href="mailto:davanum@gmail.com">davanum@gmail.com</a> <mailto:<a href="mailto:davanum@gmail.com">davanum@gmail.com</a>>>> wrote:<br>
> ><br>
> > Lattice<br>
> ><br>
> > -- dims<br>
> ><br>
> > On Sat, May 11, 2013 at 3:52 PM, Mark Turner<br>
> <<a href="mailto:mark@amerine.net">mark@amerine.net</a> <mailto:<a href="mailto:mark@amerine.net">mark@amerine.net</a>><br>
</div><div class="im">> > <mailto:<a href="mailto:mark@amerine.net">mark@amerine.net</a> <mailto:<a href="mailto:mark@amerine.net">mark@amerine.net</a>>>> wrote:<br>
> > > Tubes<br>
> > ><br>
> > > ;-)<br>
> > ><br>
> > ><br>
> > > On Sat, May 11, 2013 at 12:51 PM, Jason Smith<br>
> > <<a href="mailto:jason.smith@rackspace.com">jason.smith@rackspace.com</a><br>
> <mailto:<a href="mailto:jason.smith@rackspace.com">jason.smith@rackspace.com</a>><br>
</div>> <mailto:<a href="mailto:jason.smith@rackspace.com">jason.smith@rackspace.com</a><br>
<div class="im">> <mailto:<a href="mailto:jason.smith@rackspace.com">jason.smith@rackspace.com</a>>>><br>
> > > wrote:<br>
> > >><br>
> > >> Hello,<br>
> > >> I understand why we had to give up Quantum code name<br>
> but rather<br>
> > than just<br>
> > >> refer to it as networking let's come up with a new code<br>
> name!<br>
> > >><br>
> > >> Thoughts?<br>
> > >><br>
> > >> Thanks,<br>
> > >> -js<br>
> > >> _______________________________________________<br>
> > >> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> > >> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
</div>> <mailto:<a href="mailto:openstack@lists.launchpad.">openstack@lists.launchpad.</a>.net><br>
> > <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
<div class="im">> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>>><br>
> > >> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> > >> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
> > ><br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> > > Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
</div>> > <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
<div class="im">> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>>><br>
> > > Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> > > More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
> > ><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Davanum Srinivas :: <a href="http://davanum.wordpress.com" target="_blank">http://davanum.wordpress.com</a><br>
> ><br>
> > _______________________________________________<br>
> > Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> > Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
</div>> > <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
<div class="im HOEnZb">> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>>><br>
> > Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> > More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> > Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
> > Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> > More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
> ><br>
><br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
><br>
><br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</div></div></blockquote></div><br></div>