From ncoghlan at gmail.com Fri Jul 20 09:02:35 2018 From: ncoghlan at gmail.com (Nick Coghlan) Date: Fri, 20 Jul 2018 23:02:35 +1000 Subject: [Linux-SIG] Migrating this list to MM3 Message-ID: Hi folks, We're shortly going to be migrating this list from Mailman 2 to Mailman 3 (I'll be sending the request after I post this, and the actual migration will then take place at a convenient time for the Mailman instance admins). If you only ever access the mailing list via email, and never tinker with your subscription settings or look up threads in the list archives, then you shouldn't notice any real changes other than some of the headers on mails from the list changing a bit (such as the new Archived-At header appearing on each message). If you do use the website to change your subscription settings or look up threads in the list archives, or have wished you had a more web-forum-like interface for accessing the list, then the rest of this email is likely to be of interest :) == Changes to subscription management (and list moderation) == Mailman 3 relies on a more conventional user account management model than the historically list-centric model in Mailman 2. This means that either before or after the migration, folks that want to modify their subscription settings will need to go to https://mail.python.org/mm3/ and register for an account. If you use GitLab, GitHub, Google, or Facebook, then you can go straight to https://mail.python.org/mm3/accounts/login/, select one of those options, and grant the required access to look up your email address. (At least for GitHub, the request will come from Mark Sapiro's developer key, and I believe that's the case for the other services as well) If your address on the linked service matches your subscription address, then you're done. If it doesn't match, then you can head to https://mail.python.org/mm3/accounts/email/ to register more addresses (and hence link any related subscriptions to your account). If you don't use any of those services, or simply don't want to use them with mail.python.org, then head to https://mail.python.org/mm3/accounts/signup/ to create a conventional username-and-password based account. Regardless of how you sign up, the primary authentication mechanism is access to the relevant email address - the old MM2 plain text email password isn't used at all. After the migration, the current https://mail.python.org/mailman/listinfo/linux-sig URL will automatically redirect to https://mail.python.org/mm3/mailman3/lists/linux-sig.python.org/ For a working example of what that will look like, see https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ == Changes to list archiving (and the native web gateway) == After the migration, the current list archive at https://mail.python.org/pipermail/linux-sig/ will remain in place in order to preserve existing links, but will no longer be updated with new messages. That page will also be updated with a link to the new archiver/web gateway page. That page will be at https://mail.python.org/mm3/archives/list/linux-sig at python.org/, and not only features stable and predictable URLs for each post, but also includes a native web gateway, allowing folks to both create new threads and reply to existing ones using the web page, without needing to explicitly subscribe to the list first. Again, distutils-sig provides an example of what that will look like in practice, with the new archive at https://mail.python.org/mm3/archives/list/distutils-sig at python.org/, and the post-migration legacy archive at https://mail.python.org/pipermail/distutils-sig/. Cheers, Nick. P.S. This migration may or may not be related to the fact that list admin powers in MM3 are linked to admin's regular user accounts, rather than their knowledge of list specific admin passwords that they may or may not have recorded anywhere ;) -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia