<p>Makes sense to me.</p>
<div class="gmail_quote">On Apr 27, 2012 2:27 PM, "Everett Toews" <<a href="mailto:everett.toews@cybera.ca">everett.toews@cybera.ca</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I like this idea but what happens to the openstack-operators list in this scenario?<div><br></div><div>I don't think we'd want to have the openstack and openstack-operators list going along in parallel since it sounds like they would overlap. I propose that the members of the openstack-operators list would be (automatically or manually) migrated to the openstack list. Then the openstack-operators list would be set to read-only or maybe even removed completely to avoid confusion.</div>
<div><br></div><div>Comments? Feedback?</div><div><br></div><div>Everett<br><br><div class="gmail_quote">On Fri, Apr 27, 2012 at 4:04 AM, Thierry Carrez <span dir="ltr"><<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello everyone,<br>
<br>
TL;DR summary:<br>
Due to traffic exploding, we will split the current openstack list into<br>
user / usage topics (openstack list) and development / next-version<br>
topics (openstack-dev list).<br>
<br>
Long version:<br>
<br>
At the "Communication" session at the design summit [1] we looked at the<br>
state of our communication media in general, and mailing-list in<br>
particular [2].<br>
<br>
[1]<br>
<a href="http://folsomdesignsummit2012.sched.org/event/366accca0fda271fc23e82b9cb5162cc" target="_blank">http://folsomdesignsummit2012.sched.org/event/366accca0fda271fc23e82b9cb5162cc</a><br>
[2] <a href="http://etherpad.openstack.org/FolsomCommunication" target="_blank">http://etherpad.openstack.org/FolsomCommunication</a><br>
<br>
The traffic on the <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a> list doubled in the<br>
last 4 months [3], with more users and deployers asking for information<br>
on OpenStack projects. It becomes difficult for contributors to properly<br>
prioritize their ML reading, and we can no longer have all the<br>
discussions in the same place.<br>
<br>
[3] <a href="http://openstack.markmail.org/" target="_blank">http://openstack.markmail.org/</a><br>
<br>
The proposal is to split between:<br>
<br>
1/ Usage, deployment, Essex / current-stable discussions<br>
2/ Development, contribution, Folsom / forward-looking discussions<br>
<br>
A new list will be created for (2) and existing contributors will be<br>
asked to subscribe to that new list.<br>
<br>
Since we expect to have a more disciplined/focused group in that new<br>
list, we'll define a set of subject prefixes that should be used for<br>
easier client-side/at-a-glance filtering of discussions:<br>
<br>
[General] Affects all projects<br>
[Swift] [Nova] [Glance] [Quantum] [Horizon] [Keystone] Project-specific<br>
[Common] openstack-common<br>
[QA] [CI] [Docs] Discussions / Information on specific topics<br>
[...] Add your own here<br>
<br>
To keep that list usable, I suggest we aggressively enforce those topics<br>
and redirect inappropriate discussions to the other list when necessary.<br>
<br>
To avoid Launchpad list slowness, we would run the new openstack-dev<br>
list off <a href="http://lists.openstack.org" target="_blank">lists.openstack.org</a>. Given the potential hassle of dealing with<br>
spam and delivery issues on mission-critical MLs, we are looking into<br>
the possibility of outsourcing the maintenance of <a href="http://lists.openstack.org" target="_blank">lists.openstack.org</a> to<br>
a group with established expertise running mailman instances. Please let<br>
us know ASAP if you could offer such services. We are not married to<br>
mailman either -- if an alternative service offers good performance and<br>
better integration (like OpenID-based subscription to integrate with our<br>
SSO), we would definitely consider it.<br>
<br>
There was a suggestion during the session of using umbrella/siblings<br>
lists to aggregate content from multiple project-specific sublists. I<br>
reviewed the options and I think it introduces a lot of complexity,<br>
reduces flexibility in adding new topics, so client-side filtering<br>
sounds like a better bet. If most people use subject prefixes<br>
appropriately, keeping it simple is probably the best bet.<br>
<br>
We'll let you know when the new list is set up.<br>
<br>
Regards,<br>
<span><font color="#888888"><br>
--<br>
Thierry Carrez (ttx)<br>
Release Manager, OpenStack<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" target="_blank">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>
</font></span></blockquote></div><br></div>
<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>
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></blockquote></div>