atom feed24 messages in net.launchpad.lists.openstackRe: [Openstack] Mailing-list split
FromSent OnAttachments
Thierry CarrezApr 27, 2012 3:04 am 
Daniel P. BerrangeApr 27, 2012 3:46 am 
Jim MeyeringApr 27, 2012 4:11 am 
Monty TaylorApr 27, 2012 5:41 am 
Monty TaylorApr 27, 2012 5:46 am 
Duncan McGreggorApr 27, 2012 6:44 am 
Monty TaylorApr 27, 2012 8:26 am 
Duncan McGreggorApr 27, 2012 8:31 am 
Stefano MaffulliApr 27, 2012 9:33 am 
Everett ToewsApr 27, 2012 12:52 pm 
Matt JoyceApr 27, 2012 2:33 pm 
Duncan McGreggorApr 27, 2012 2:42 pm 
Stefano MaffulliApr 27, 2012 5:59 pm 
Jim MeyeringApr 28, 2012 2:45 pm 
Everett ToewsApr 30, 2012 9:12 am 
Stefano MaffulliApr 30, 2012 10:08 am 
Everett ToewsApr 30, 2012 11:00 am 
Duncan McGreggorApr 30, 2012 11:06 am 
Matt RayApr 30, 2012 11:37 am 
Jan van EldikMay 1, 2012 1:13 pm 
Duncan McGreggorMay 11, 2012 1:12 pm 
Duncan McGreggorMay 11, 2012 1:20 pm 
Duncan McGreggorMay 17, 2012 8:40 am 
Duncan McGreggorMay 17, 2012 8:46 am 
Subject:Re: [Openstack] Mailing-list split
From:Duncan McGreggor (dun@dreamhost.com)
Date:Apr 27, 2012 8:31:28 am
List:net.launchpad.lists.openstack

On Fri, Apr 27, 2012 at 11:27 AM, Monty Taylor <mord@inaugust.com> wrote:

On 04/27/2012 09:44 AM, Duncan McGreggor wrote:

On Fri, Apr 27, 2012 at 8:46 AM, Monty Taylor <mord@inaugust.com> wrote:

Hey everyone!

On 04/27/2012 05:04 AM, Thierry Carrez wrote:

To avoid Launchpad list slowness, we would run the new openstack-dev list off lists.openstack.org. Given the potential hassle of dealing with spam and delivery issues on mission-critical MLs, we are looking into the possibility of outsourcing the maintenance of lists.openstack.org to a group with established expertise running mailman instances. Please let us know ASAP if you could offer such services. We are not married to mailman either -- if an alternative service offers good performance and better integration (like OpenID-based subscription to integrate with our SSO), we would definitely consider it.

Just to be clear - I definitely think that mailing lists are an important part of dev infrastructure and would love for this to be a fully integrated part of all of the rest of our tools. However, the current set of active infrastructure team members have huge todo lists at the moment. So the biggest home run from my perspective would be if someone out there had time or resources and wanted to join us on the infra team to manage this on our existing resources (turns out we have plenty of servers for running this, and even a decent amount of expertise, just missing manpower). The existing team would be more than happy to be involved, and it would help avoid get-hit-by-a-truck issues. We're a pretty friendly bunch, I promise.

Any takers? Anybody want to pony up somebody with some bandwidth to admin a mailman? Respond back here or just find us in #openstack-infra and we'll get you plugged in and stuff.

Thanks! Monty

Count me in, Monty.

I've been managing mailman lists for about 12 years now (and, incidentally, Barry and I are bruthas from anutha mutha), so I'd be quite comfortable handling those responsibilities. I can couple it with the python.org SIG mail list that I manage, so there'd be zero context switching.

You make me very happy! Let's work out the details and stuff...

Right on.

Check it out - it's like we're, you know, a collaborative community or something!

:-D

d