[09:17] <guruprasad> pabs3, lists.launchpad.net is using Mailman 2 and we are evaluating its future (the future of the current code, the future of mailing list hosting itself, etc.) since Mailman 2 stops us at Python 3 and Mailman 3 is an incompatible rewrite.
[09:18] <guruprasad> If and when we do something about this, we will preserve all the archives - one of the ideas was to host a static export of the last copy of all the data before we make any destructive changes.
[09:18] <pabs3> great
[09:18] <guruprasad> And yes, archiving to archive.org sounds like a useful thing to do too
[09:18] <pabs3> btw, there is a WIP mailman2 fork for Python 3 https://github.com/jaredmauch/mailman2-python3
[09:19] <guruprasad> There are 3rd party mailing list archive services that archive many Launchpad mailing lists, but us doing it using archive.org makes it first-party involvement and likely to be more comprehensive.
[09:19] <guruprasad> pabs3, yes, cjwatson has mentioned that a few times but we still need to assesss it thoroughly and see if it fits in the model of what we want to do with mailing list hosting.
[09:21] <pabs3> given a full list of all the mailing list names, I can do the archive.org saving using the ArchiveBot crawler https://wiki.archiveteam.org/index.php/ArchiveBot
[09:22] <guruprasad> pabs3, thanks! The service is still live and will continue to work in its current state till we decide on what to do with it.
[09:22] <pabs3> cool
[09:23] <guruprasad> Launchpad has a lot of private mailing lists of importance too and we need to come up with a solution that works for those too.
[09:23] <guruprasad> So there is a lot of investigation and evaluation to do from our side for this.
[09:29] <pabs3> I see