<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>Looks like there is general agreement. For those who are concerned about confusion of too many lists, there are already 11 public lists at <a href="http://lists.openstack.org">http://lists.openstack.org</a>. What really is missing of course, is a general list called openstack when new people show up at <a href="http://lists.openstack.org">lists.openstack.org</a>. What is also missing in some cases is a good description of what they are or were (such as Fits). Maybe operators dies a quiet death with zero traffic, but the archives should remain in place and searchable. Just put a DEPRECATED or DELETED label in the description or something. You can even delete the mail aliases for it if you want to disable the list, but don't edit history by artificially merging openstack@lp and openstack-operators@os archives. That just sounds like a lot of work likely to go wrong.</div><br><table width="100%" border="0" style="font-family: Times; position: static; z-index: auto; "><tbody><tr><td><strong><font size="+2">List</font></strong></td><td><strong><font size="+2">Description</font></strong></td></tr><tr bgcolor="#dddddd"><td><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/community"><strong>Community</strong></a></td><td>The OpenStack Community team is the main contact point for anybody running a local OpenStack User Group.</td></tr><tr><td><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/fits"><strong>Fits</strong></a></td><td><em>[no description available]</em></td></tr><tr bgcolor="#dddddd"><td><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation"><strong>Foundation</strong></a></td><td>Foundation set up discussion list</td></tr><tr><td><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board"><strong>Foundation-board</strong></a></td><td>OpenStack Foundation Board of Directors</td></tr><tr bgcolor="#dddddd"><td><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/grizzly-summit-planning"><strong>Grizzly-Summit-Planning</strong></a></td><td>Grizzly summit planning</td></tr><tr><td><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-announce"><strong>OpenStack-announce</strong></a></td><td>Announces about OpenStack new releases, stable releases and security advisories</td></tr><tr bgcolor="#dddddd"><td><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><strong>OpenStack-dev</strong></a></td><td>OpenStack Development Mailing List</td></tr><tr><td><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs"><strong>Openstack-docs</strong></a></td><td>OpenStack Documentation Mailing List</td></tr><tr bgcolor="#dddddd"><td><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-hpc"><strong>OpenStack-HPC</strong></a></td><td>High-Performance Computing OpenStack List</td></tr><tr><td><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"><strong>OpenStack-operators</strong></a></td><td>Discussion list for operators of OpenStack</td></tr><tr bgcolor="#dddddd"><td><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-partner"><strong>OpenStack-partner</strong></a></td><td><em>[no description available]<br><br></em></td></tr></tbody></table><div><br></div><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><div><div style="font-size: 12px; ">-------------------------------------------------</div><div style="font-size: 12px; ">Brian Schott, CTO</div><div style="font-size: 12px; ">Nimbis Services, Inc.</div><div style="font-size: 12px; "><a href="mailto:brian.schott@nimbisservices.com">brian.schott@nimbisservices.com</a></div><div style="font-size: 12px; ">ph: 443-274-6064 fx: 443-274-6060</div></div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On Sep 14, 2012, at 3:03 PM, Thierry Carrez <<a href="mailto:thierry@openstack.org">thierry@openstack.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Stefano Maffulli wrote:<br><blockquote type="cite">I think the best option then is to clone openstack@launchpad in the new <br>host and leave operators as is (at least for the moment). Suboptimal, <br>maybe, but I believe it solves the issue at hand (consolidate lists on <br>one host) and doens't create extra work or stress.<br><br>If nobody stops me, I'll go on and contact Canonical's folks to get <br>more details and will post a migration plan to this list soon.<br></blockquote><br>I think that's a safe bet. For those following at home, that would be<br>option A2, which can potentially be turned into option B2 by merging<br>openstack-operators@ into openstack@ in the future.<br><br>Regards,<br><br>-- <br>Thierry Carrez (ttx)<br>Release Manager, OpenStack<br><br>_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">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">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></blockquote></div><br></body></html>