[openstack-dev] [all][rdo][kolla] Recommending the RDO tag for the mailing list
Steven Dake (stdake)
stdake at cisco.com
Tue Dec 20 16:57:34 UTC 2016
As David mentioned I had certainly not suggested moving all discussion from RDO list. This is why I invited the Kolla community to join rdo-list if they so choose. I think some heads up around “these are issues you may face” is warranted as David’s email  points out. It is very difficult for everyone to be on all lists and pay attention to everything.
It is easy for OpenStack community members to set a [rdo] filter for low volume traffic like David’s heads up around RDO that lacked a tag for those that need that information. Most of the kolla community who is deeply affected by this particular problem wasn’t aware of it and tracking it down in our mail clients is a little onerous without any tag at all.
Hope that clears things up ☺
From: David Moreau Simard <dms at redhat.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date: Tuesday, December 20, 2016 at 7:02 AM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [all][rdo][kolla] Recommending the RDO tag for the mailing list
I believe Steven is referring to the recent post regarding issues with
CentOS 7.3 .
Arguably, that particular email was sent to openstack-dev,
openstack-operators as well as rdo-list.
I think it's okay to tag things relevant to RDO in openstack-dev but
that doesn't mean we're moving the discussions from rdo-list to
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Tue, Dec 20, 2016 at 5:19 AM, Erno Kuvaja <ekuvaja at redhat.com> wrote:
> On Mon, Dec 19, 2016 at 2:21 PM, Steven Dake (stdake) <stdake at cisco.com> wrote:
>> I am in favor of using a new tag called [rdo] such that RDO (or its
>> transitive dependencies) can be discussed and filtered by email clients as
>> it relates to development topics that affect the broader OpenStack
>> ecosystem. As RDO is a community driven project which is very much related
>> to OpenStack, I think sharing a little bit of OpenStack list bandwidth isn’t
>> too much to ask.
>> Further I’d invite the broader Kolla team to subscribe to the rdo-list,
>> which is a much more comprehensive coverage of RDO (both users and devs with
>> significant traffic) and filter rdo-list as you prefer:
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> Hi Steven,
> I'm not sure I understand the intention fully here. openstack-dev is
> super gluttered already as it is, can you give an example what would
> be appropriate discussion in openstack-dev [rdo] rather than having
> that discussion on rdo-project mailing list?
> My initial thought is that I'd very much would not like to open the
> openstack-dev to any 3rd party projects (yes I'm fully aware that rdo
> is very much related to OpenStack and my employer, it does not make it
> any less 3rd party to OS development) to discuss their matters. So my
> initial reaction would be "Please no".
> - Erno 'jokke' Kuvaja
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev