Upgrading python-ideas to MM3?
Hi folks, A number of smaller python.org mailing lists have been successfully migrated to the PSF's Mailman 3 infrastructure, for example, the core-workflow mailing list: https://mail.python.org/mm3/archives/list/core-workflow@python.org/ The biggest practical gain from the upgrade is to allow folks that prefer a more forum-like experience to use the native web gateway rather than subscribing to the list. (Although it does come with some general account management improvements as well, since you get one user account with multiple list subscriptions, rather than multiple independent subscriptions that happen to share an email address). So far we've refrained from upgrading any of the "big" lists with lots of subscribers, but it seems to me that python-ideas could be a good test case on that front: * anything we discuss here necessarily isn't urgent, so if the migration encounters unexpected problems, it's OK if list activity is disrupted for a while * for newcomers to the core development process, python-ideas is typically going to be more relevant to them than the other big lists Cheers, Nick. P.S. As per https://github.com/python/core-workflow/issues/200#issuecomment-361818530, subscription migrations are based on email addresses, so the key point affecting individual users and list moderators is that you'll need to either go to https://mail.python.org/mm3/accounts/login/ and log in using a 3rd party service that already has your subscription email associated with it, or else go to https://mail.python.org/mm3/accounts/signup/ and create a new account directly with the appropriate email address. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
Besides the login issues (or non-issues), assuming best case scenario, would the migration be seamless from my inbox’s point of view? Would I have to re-subscribe? From: Python-ideas [mailto:python-ideas-bounces+tritium-list=sdamon.com@python.org] On Behalf Of Nick Coghlan Sent: Thursday, March 1, 2018 12:29 AM To: python-ideas <python-ideas@python.org> Subject: [Python-ideas] Upgrading python-ideas to MM3? Hi folks, A number of smaller python.org <http://python.org> mailing lists have been successfully migrated to the PSF's Mailman 3 infrastructure, for example, the core-workflow mailing list: https://mail.python.org/mm3/archives/list/core-workflow@python.org/ The biggest practical gain from the upgrade is to allow folks that prefer a more forum-like experience to use the native web gateway rather than subscribing to the list. (Although it does come with some general account management improvements as well, since you get one user account with multiple list subscriptions, rather than multiple independent subscriptions that happen to share an email address). So far we've refrained from upgrading any of the "big" lists with lots of subscribers, but it seems to me that python-ideas could be a good test case on that front: * anything we discuss here necessarily isn't urgent, so if the migration encounters unexpected problems, it's OK if list activity is disrupted for a while * for newcomers to the core development process, python-ideas is typically going to be more relevant to them than the other big lists Cheers, Nick. P.S. As per https://github.com/python/core-workflow/issues/200#issuecomment-361818530, subscription migrations are based on email addresses, so the key point affecting individual users and list moderators is that you'll need to either go to https://mail.python.org/mm3/accounts/login/ and log in using a 3rd party service that already has your subscription email associated with it, or else go to https://mail.python.org/mm3/accounts/signup/ and create a new account directly with the appropriate email address. -- Nick Coghlan | ncoghlan@gmail.com <mailto:ncoghlan@gmail.com> | Brisbane, Australia
On 1 March 2018 at 17:19, Alex Walters <tritium-list@sdamon.com> wrote:
Assuming all goes well (which it did for both core-mentorship and core-workflow), then folks shouldn't need to do anything to maintain their existing subscription settings. The only folks that should notice a change are: * list moderators (since the admin login arrangements change) * anyone changing their list subscription settings through the web UI (since that changes to the MM3 admin) * anyone creating links to emails archived post-migration (since the old pipermail archives will stop getting updated, but post-migration emails will have their archive link in the Archived-At header) Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
01.03.18 07:28, Nick Coghlan пише:
What about permanent links? Will https://mail.python.org/pipermail/python-ideas/2018-March/049108.html be accessible after migration?
On 1 March 2018 at 17:33, Serhiy Storchaka <storchaka@gmail.com> wrote:
Yeah, the existing archives will remain untouched (but will also stop getting updated). New and migrated messages get archived based on a content-addressable hash (e.g. https://mail.python.org/mm3/archives/list/core-workflow@python.org/message/2...), with a thread view that will happily accommodate discussions that span a change of month. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Thu, 1 Mar 2018 15:28:57 +1000 Nick Coghlan <ncoghlan@gmail.com> wrote:
That URL fails for me. You probably mean https://mail.python.org/mm3/archives/list/core-workflow@python.org/ As long as there's a gmane (NNTP) gateway I can live with the MM3 UI experience. Regards Antoine.
Besides the login issues (or non-issues), assuming best case scenario, would the migration be seamless from my inbox’s point of view? Would I have to re-subscribe? From: Python-ideas [mailto:python-ideas-bounces+tritium-list=sdamon.com@python.org] On Behalf Of Nick Coghlan Sent: Thursday, March 1, 2018 12:29 AM To: python-ideas <python-ideas@python.org> Subject: [Python-ideas] Upgrading python-ideas to MM3? Hi folks, A number of smaller python.org <http://python.org> mailing lists have been successfully migrated to the PSF's Mailman 3 infrastructure, for example, the core-workflow mailing list: https://mail.python.org/mm3/archives/list/core-workflow@python.org/ The biggest practical gain from the upgrade is to allow folks that prefer a more forum-like experience to use the native web gateway rather than subscribing to the list. (Although it does come with some general account management improvements as well, since you get one user account with multiple list subscriptions, rather than multiple independent subscriptions that happen to share an email address). So far we've refrained from upgrading any of the "big" lists with lots of subscribers, but it seems to me that python-ideas could be a good test case on that front: * anything we discuss here necessarily isn't urgent, so if the migration encounters unexpected problems, it's OK if list activity is disrupted for a while * for newcomers to the core development process, python-ideas is typically going to be more relevant to them than the other big lists Cheers, Nick. P.S. As per https://github.com/python/core-workflow/issues/200#issuecomment-361818530, subscription migrations are based on email addresses, so the key point affecting individual users and list moderators is that you'll need to either go to https://mail.python.org/mm3/accounts/login/ and log in using a 3rd party service that already has your subscription email associated with it, or else go to https://mail.python.org/mm3/accounts/signup/ and create a new account directly with the appropriate email address. -- Nick Coghlan | ncoghlan@gmail.com <mailto:ncoghlan@gmail.com> | Brisbane, Australia
On 1 March 2018 at 17:19, Alex Walters <tritium-list@sdamon.com> wrote:
Assuming all goes well (which it did for both core-mentorship and core-workflow), then folks shouldn't need to do anything to maintain their existing subscription settings. The only folks that should notice a change are: * list moderators (since the admin login arrangements change) * anyone changing their list subscription settings through the web UI (since that changes to the MM3 admin) * anyone creating links to emails archived post-migration (since the old pipermail archives will stop getting updated, but post-migration emails will have their archive link in the Archived-At header) Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
01.03.18 07:28, Nick Coghlan пише:
What about permanent links? Will https://mail.python.org/pipermail/python-ideas/2018-March/049108.html be accessible after migration?
On 1 March 2018 at 17:33, Serhiy Storchaka <storchaka@gmail.com> wrote:
Yeah, the existing archives will remain untouched (but will also stop getting updated). New and migrated messages get archived based on a content-addressable hash (e.g. https://mail.python.org/mm3/archives/list/core-workflow@python.org/message/2...), with a thread view that will happily accommodate discussions that span a change of month. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Thu, 1 Mar 2018 15:28:57 +1000 Nick Coghlan <ncoghlan@gmail.com> wrote:
That URL fails for me. You probably mean https://mail.python.org/mm3/archives/list/core-workflow@python.org/ As long as there's a gmane (NNTP) gateway I can live with the MM3 UI experience. Regards Antoine.
participants (4)
-
Alex Walters -
Antoine Pitrou -
Nick Coghlan -
Serhiy Storchaka