Re: [openstack-dev] [Rdo-list] [TripleO] Should we rename "RDO Manager" to "TripleO" ?
On Mon, Feb 22, 2016 at 9:46 AM, Dan Princewrote: > Does this mean RDO Manager will be adopting use of the nicely rounded > owl mascot as well? > > http://tripleo.org/ > > As far as upstream branding goes this would really make it crystal > clear to me... :) "RDO Manager" won't exist anymore. People that have been using "RDO Manager" have been using TripleO. So, yes, owls will be had. :) David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Rdo-list] [TripleO] Should we rename "RDO Manager" to "TripleO" ?
+1 for this. Having already navigated the depths of RDO, this eliminates a big point of confusion. On Wed, Feb 17, 2016 at 8:27 AM, David Moreau Simardwrote: > Greetings, > > (Note: cross-posted between rdo-list and openstack-dev to reach a > larger audience) > > Today, because of the branding and the name "RDO Manager", you might > think that it's something other than TripleO - either something > entirely different or perhaps with downstream patches baked in. > You would not be the only one because the community, the users and the > developers alike have shared their confusion on that topic. > > The truth is, as it stands right now, "RDO Manager" really is "TripleO". > There is no code or documentation differences. > > I feel the only thing that is different is the strategy around how we > test TripleO to ensure the stability of RDO packages but it's already > in the process of being sent upstream [1] because we're convinced it's > the best way forward. > > Historically, RDO Manager and TripleO were different things. > Today this is no longer the case and we plan on keeping it that way. > > With this in mind, we would like to drop the RDO manager branding and > use TripleO instead. > Not only would we clear the confusion on the topic of what RDO Manager > really is but it would also strengthen the TripleO name. > > We would love the RDO community to chime in on this and give their > feedback as to whether or not this is a good initiative. > We will proceed to a formal vote on $subject at the next RDO meeting > on Wednesday, 24th Feb, 2016 1500 UTC [2]. Feel free to join us on > #rdo on freenode. > > Thanks, > > [1]: https://review.openstack.org/#/c/276810/ > [2]: https://etherpad.openstack.org/p/RDO-Meeting > > David Moreau Simard > Senior Software Engineer | Openstack RDO > > dmsimard = [irc, github, twitter] > > ___ > Rdo-list mailing list > rdo-l...@redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscr...@redhat.com > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Rdo-list] [TripleO] Should we rename "RDO Manager" to "TripleO" ?
+1 This has been very confusing and it would be nice to finally get that clearer. On Wed, Feb 17, 2016 at 7:49 PM, Haïkelwrote: > +1 it fuels the confusion that RDO Manager has downstream-only patches > which is not the case anymore. > > And I'll bite anyone who will try to sneak downstream-only patches in > RDO package of tripleO. > > Regards, > H. > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Juan Antonio Osorio R. e-mail: jaosor...@gmail.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Rdo-list] [TripleO] Should we rename "RDO Manager" to "TripleO" ?
+1 it fuels the confusion that RDO Manager has downstream-only patches which is not the case anymore. And I'll bite anyone who will try to sneak downstream-only patches in RDO package of tripleO. Regards, H. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Rdo-list] [TripleO] Should we rename "RDO Manager" to "TripleO" ?
+1. There are already arguably too many names involved in OpenStack, let alone having multiple names for the same thing. :) Thanks, Kevin From: rdo-list-boun...@redhat.com [rdo-list-boun...@redhat.com] on behalf of David Moreau Simard [d...@redhat.com] Sent: Wednesday, February 17, 2016 8:27 AM To: OpenStack Development Mailing List (not for usage questions); rdo-list Subject: [Rdo-list] [TripleO] Should we rename "RDO Manager" to "TripleO" ? Greetings, (Note: cross-posted between rdo-list and openstack-dev to reach a larger audience) Today, because of the branding and the name "RDO Manager", you might think that it's something other than TripleO - either something entirely different or perhaps with downstream patches baked in. You would not be the only one because the community, the users and the developers alike have shared their confusion on that topic. The truth is, as it stands right now, "RDO Manager" really is "TripleO". There is no code or documentation differences. I feel the only thing that is different is the strategy around how we test TripleO to ensure the stability of RDO packages but it's already in the process of being sent upstream [1] because we're convinced it's the best way forward. Historically, RDO Manager and TripleO were different things. Today this is no longer the case and we plan on keeping it that way. With this in mind, we would like to drop the RDO manager branding and use TripleO instead. Not only would we clear the confusion on the topic of what RDO Manager really is but it would also strengthen the TripleO name. We would love the RDO community to chime in on this and give their feedback as to whether or not this is a good initiative. We will proceed to a formal vote on $subject at the next RDO meeting on Wednesday, 24th Feb, 2016 1500 UTC [2]. Feel free to join us on #rdo on freenode. Thanks, [1]: https://review.openstack.org/#/c/276810/ [2]: https://etherpad.openstack.org/p/RDO-Meeting David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] ___ Rdo-list mailing list rdo-l...@redhat.com https://www.redhat.com/mailman/listinfo/rdo-list To unsubscribe: rdo-list-unsubscr...@redhat.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev