Open Stack

----- Original Message -----
> From: "Ben Nemec" <openstack at nemebean.com>
> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
> Sent: Friday, 21 August, 2015 11:00:31 PM
> Subject: Re: [openstack-dev] [TripleO] Moving instack upstream
> 
> On 08/19/2015 12:22 PM, Dougal Matthews wrote:
> > 
> > 
> > 
> > 
> > ----- Original Message -----
> >> From: "Dmitry Tantsur" <dtantsur at redhat.com>
> >> To: openstack-dev at lists.openstack.org
> >> Sent: Wednesday, 19 August, 2015 5:57:36 PM
> >> Subject: Re: [openstack-dev] [TripleO] Moving instack upstream
> >>
> >> On 08/19/2015 06:42 PM, Derek Higgins wrote:
> >>> On 06/08/15 15:01, Dougal Matthews wrote:
> >>>> ----- Original Message -----
> >>>>> From: "Dan Prince" <dprince at redhat.com>
> >>>>> To: "OpenStack Development Mailing List (not for usage questions)"
> >>>>> <openstack-dev at lists.openstack.org>
> >>>>> Sent: Thursday, 6 August, 2015 1:12:42 PM
> >>>>> Subject: Re: [openstack-dev] [TripleO] Moving instack upstream
> >>>
> >>> <snip>
> >>>
> >>>>> I would really like to see us rename python-rdomanager-oscplugin. I
> >>>>> think any project having the name "RDO" in it probably doesn't belong
> >>>>> under TripleO proper. Looking at the project there are some distro
> >>>>> specific things... but those are fairly encapsulated (or could be made
> >>>>> so fairly easily).
> >>>>
> >>>> I agree, it made sense as it was the entrypoint to RDO-Manager. However,
> >>>> it could easily be called the python-tripleo-oscplugin or similar. The
> >>>> changes would be really trivial, I can only think of one area that
> >>>> may be distro specific.
> >>>
> >>> I'm putting the commit together now to pull these repositories into
> >>> upstream tripleo are we happy with the name "python-tripleo-oscplugin" ?
> >>
> >> Do we really need this "oscplugin" postfix? It may be clear for some of
> >> us, but I don't that our users know that OSC means OpenStackClient, and
> >> that oscplugin designates "something that adds features to openstack
> >> command". Can't we just call it python-tripleo? or maybe even just
> >> "tripleo"?
> > 
> > +1 to either.
> > 
> > Having oscplugin in the name just revealed an implementation detail, there
> > may be a point where for some reason everyone moves away from OSC.
> 
> FWIW, I would prefer tripleo-client.  That's more in line with what the
> other projects do, and doesn't carry the potential for confusion that
> just naming it "tripleo" would.

How about tripleo-cli? I objected to client because it suggested there was a
server (which may happen, but hasn't yet).

> 
> > 
> >>
> >>>
> >>>
> >>>
> >>> __________________________________________________________________________
> >>> OpenStack Development Mailing List (not for usage questions)
> >>> Unsubscribe:
> >>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >>
> >> __________________________________________________________________________
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> > 
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > 
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>