One of the original purposes of the Netstack mailing list was not to clutter the Openstack mailing list with design and development discussions. Now that Quantum is going into core for Folsom it makes sense to merge with the main mailing list. Having two separate mailing lists started to become slightly awkward when we starting discussing the integration with nova. This means that most Quantum core devs have already to look for Quantum-related messages on both mailing list. Having a single one will probably make their life a bit easier.
I think the point Chris made at the summit was about development-specific mailing lists. I agree with that, but I would prefer to see something Openstack-wide. For instance something like openstack-dev, openstack-users, openstack-discuss, etc.? Salvatore > -----Original Message----- > From: netstack- > bounces+salvatore.orlando=eu.citrix....@lists.launchpad.net > [mailto:netstack- > bounces+salvatore.orlando=eu.citrix....@lists.launchpad.net] On Behalf Of > Vikram Visweswaraiah > Sent: 24 April 2012 08:37 > To: Dan Wendlandt > Cc: netstack@lists.launchpad.net > Subject: Re: [Netstack] Closing down this list. > > I meant to comment on this during one of the Quantum sessions. I'm not > sure the discussion should be centered around lists as much as the ability to > tag the subject so it can be filtered. Assuming the mailer can support this, > you could retain project specific email ids as aliases to the main openstack > list. Posts to any project alias get tagged with the project, but still get > sent to > the main openstack list. Everyone sees everything, the tags help with > filtering. > > Thanks! > -V > > On Apr 23, 2012, at 11:51 AM, Dan Wendlandt wrote: > > > Hi David, > > > > I'll leave the list operational for a bit (as I suspect some people will > > have > missed the announcement), but will redirect all discussions to the main > openstack list. I think having Quantum in the title of the email will help us > pick out relevant emails. > > > > We still have an unresolved discussion around having project-specific dev > lists, raised by Chris Wright. My gut says that the right long-term approach > is > to have project specific *-dev lists, with a single "openstack" list for users > questions and community-wide topics, but we'll see. > > > > Dan > > > > > > On Thu, Apr 19, 2012 at 1:34 PM, David Medberry > <david.medbe...@canonical.com> wrote: > > I believe we are closing down this list (or has it already happened) and > folding netstack work into the main openst...@lists.launchpad.net > > > > Has this already begun--I'm not seeing much in here today (though likely > because of the conference.) > > > > -- > > Mailing list: https://launchpad.net/~netstack > > Post to : netstack@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~netstack > > More help : https://help.launchpad.net/ListHelp > > > > > > > > -- > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Dan Wendlandt > > Nicira, Inc: www.nicira.com > > twitter: danwendlandt > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > -- > > Mailing list: https://launchpad.net/~netstack > > Post to : netstack@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~netstack > > More help : https://help.launchpad.net/ListHelp > > > -- > Mailing list: https://launchpad.net/~netstack > Post to : netstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~netstack > More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
