Looks like there is general agreement. For those who are concerned about confusion of too many lists, there are already 11 public lists at http://lists.openstack.org. What really is missing of course, is a general list called openstack when new people show up at lists.openstack.org. 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.
List Description Community The OpenStack Community team is the main contact point for anybody running a local OpenStack User Group. Fits [no description available] Foundation Foundation set up discussion list Foundation-board OpenStack Foundation Board of Directors Grizzly-Summit-Planning Grizzly summit planning OpenStack-announce Announces about OpenStack new releases, stable releases and security advisories OpenStack-dev OpenStack Development Mailing List Openstack-docs OpenStack Documentation Mailing List OpenStack-HPC High-Performance Computing OpenStack List OpenStack-operators Discussion list for operators of OpenStack OpenStack-partner [no description available] ------------------------------------------------- Brian Schott, CTO Nimbis Services, Inc. [email protected] ph: 443-274-6064 fx: 443-274-6060 On Sep 14, 2012, at 3:03 PM, Thierry Carrez <[email protected]> wrote: > Stefano Maffulli wrote: >> I think the best option then is to clone openstack@launchpad in the new >> host and leave operators as is (at least for the moment). Suboptimal, >> maybe, but I believe it solves the issue at hand (consolidate lists on >> one host) and doens't create extra work or stress. >> >> If nobody stops me, I'll go on and contact Canonical's folks to get >> more details and will post a migration plan to this list soon. > > I think that's a safe bet. For those following at home, that would be > option A2, which can potentially be turned into option B2 by merging > openstack-operators@ into openstack@ in the future. > > Regards, > > -- > Thierry Carrez (ttx) > Release Manager, OpenStack > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
