[142826] in North American Network Operators' Group
Re: NANOG List Update - Moving Forward
daemon@ATHENA.MIT.EDU (Ben McGinnes)
Thu Jul 14 09:59:33 2011
Date: Thu, 14 Jul 2011 23:57:51 +1000
From: Ben McGinnes <ben@adversary.org>
To: nanog@nanog.org
In-Reply-To: <20110713133709.GA22505@gsp.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig948455076C9CB5998D737330
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 13/07/11 11:37 PM, Richard Kulawiec wrote:
> On Tue, Jul 12, 2011 at 04:13:10PM +0200, Mattias Ahnberg wrote:
>> I might have missed some discussion; but why are we moving
>> away from mailman, and what software is in the new system?
>=20
> Seconded. Mailman is presently the gold standard for mailing list
> management
Apparently the main exception to this is where you're running multiple
lists with similar names, such as when creating lists for multiple
languages (e.g. announce@example.com, announce@it.example.com,
announce@jp.example.com, etc.). This is the problem the Document
Foundation found itself with and they opted for mlmmj (with the
exception of one list which does use Mailman), but it has other issues
and I definitely wouldn't want to see NANOG go down that path. Since
NANOG doesn't need to deal with the similar names/multilingual
problem, that shouldn't be an issue.
Regards,
Ben
--------------enig948455076C9CB5998D737330
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
iEYEAREKAAYFAk4e9d8ACgkQNxrFv6BK4xPwbQCfVcjbVSxVztK6l/rjeVpapUQU
NmkAoOKe4y5hm5ipxjZMdIdYM010sZAU
=q3Uj
-----END PGP SIGNATURE-----
--------------enig948455076C9CB5998D737330--
