On Wed, Jun 25, 2014 at 2:55 AM, Stephen Frost <sfrost@snowman.net> wrote:
(I'm gonig to stick to a technical comment, since Stephen and Dave have already said most of the things I'd otherwise say on the policies anyway. I do, fwiw, agree that there is a problem here that we need to find a way to solve)
> If adding new lists to majordomo is painful (and I can imagine it might
> be), can we please set up a low-SLA mailman instance somewhere on > postgresql.org so that every list request doesn't have to turn into an > argument? If this is a PITA for the infra team, can we ask OSUOSL for one?
Unfortunately, it is not that simple. There is no such thing as a siple "low-SLA" mailman the way mailman works today. There's a reason (ok there's more than one reason) that the mailman integration with pgfoundry was such horrible crap. And there's really not any good way around that the way it works today. And mj2 is even worse.
I do have some foolish hope in mailman3 when it comes to this. They do, actually, support postgresql backends for example, and they have an API. And by some miracle, development seems to have picked up again recently and they're now in beta (though they haven't even managed to update their own website to reflect that info even though it's months ago).
It's not something we can use now, but I hope it gets there at some point.
That still only solves part of the problem though. Just dealing with bounce management and abuse and whatnot still takes time. But at least with the right tools, you have a better choice.
Email, sadly, is a time consuming business to be in.