Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine whether to transition Mailman or migrate to a different mailing list service #2

Open
dlglin opened this issue Feb 12, 2020 · 0 comments

Comments

@dlglin
Copy link
Member

dlglin commented Feb 12, 2020

  1. Transferring mailman to google groups seems possible, but time consuming and fragile — you basically send all of the messages to google one at a time.
    The messages are recorded in order but without the original timestamps and authors. This doesn’t seem great.

  2. Transferring mailman is possible — below are the references I found, and the locations of most (all?) of the pieces of mailman on the webwork.maa.org server.
    mailman does not use a database as far as I can tell which might make wholesale transfer easier. Our mailman is version 2.1.13.
    This post https://mail.python.org/pipermail/mailman-users/2016-October/081482.html seems to indicate that the transfer and upgrade is doable. The uptodate release is 3.3 https://www.list.org/

  3. I hadn’t thought of Tani’s idea to simply freeze and preserve the current archives and start using google groups. What do others thing of that idea?
    Can we freeze the current pipermail archive? — or is it dynamically served?

  4. I don’t yet have a good plan for Mailman that I’m completely happy with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant