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. Cheers, stef On Fri 14 Sep 2012 12:48:34 AM PDT, Thierry Carrez wrote: > Duncan McGreggor wrote: >> Given no option Bs, the simplicity of option C is most appealing to me. > > Option C is actually like a B0 (single list for user/operators/general > questions), but named openstack-operators instead of openstack, > openstack-general or openstack-user[s]. > > I'm not a big fan of that option because there is no clear list for > general discussion or newcomers questions. Where do you post things that > are not "how to operate" and "how to develop", but rather affect all our > community ? For example an election nomination discussion ? The > -operators name seem a lot too restrictive for that. > > That's why I actually prefer "openstack" (B2) as it's much clearer where > those "general discussions" would belong. With option C (B0) we'll end > up with general discussions scattered all over the place, people having > to join all lists, redirected threads and a lot of cross-posting. > _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
