Re: The future of arch-commits
On 15.05.2022 23.53, Kristian Klausen wrote: So, is there any reasons for not deprecating it? How are you using it and could that need be met in some other (and perhaps better) way? So from the response I got so far, it sounds like the archive isn't used. If I don't get any new responses in the next few days, I will just migrate arch-commits to mailman3 without migrating the archive and with archiving disabled. Cheers, Kristian OpenPGP_signature Description: OpenPGP digital signature
Mailman3 migration and news draft
Hi all, As hinted in my last message, I'm in the process of migrating our mailing lists from mailman2 to mailman3[1]. We are migrating away from mailman2 as it is basically unmaintained and requires Python 2 which is EOL. At the time of writing the following active lists haven't been migrated: - arch-commits - arch-general - arch-security - aur-dev - aur-general - aur-requests - pacman-contrib - pacman-dev I'm planning to migrate the remaining lists soon and likely migrating arch-general and aur-general as the last two lists. As part of the migration I'm disabling the "mangling" of the mails to keep the DKIM signature intact (i.e. no rewrite of the "from" header nor prefixing the subject with the list name), this means "reply list" must be used when replying to the list. For that reason I think the change is worth a news item, so the users know they must use "reply list" and that they may need to update their filters. I have created a draft here[2] which I hope to post after migrating the remaining lists (feel free to edit). [1] https://gitlab.archlinux.org/archlinux/infrastructure/-/issues/59 [2] https://md.archlinux.org/mDhhaF0WRaOPMmyYqifn2Q Cheers, Kristian Klausen OpenPGP_signature Description: OpenPGP digital signature
[arch-dev-public] Re: Mailman3 migration and news draft
Hi there, Le 17/05/2022 à 22:27, Kristian Klausen a écrit : Hi all, As hinted in my last message, I'm in the process of migrating our mailing lists from mailman2 to mailman3[1]. We are migrating away from mailman2 as it is basically unmaintained and requires Python 2 which is EOL. Great thing! At the time of writing the following active lists haven't been migrated: - arch-commits - arch-general - arch-security - aur-dev - aur-general - aur-requests - pacman-contrib - pacman-dev I'm planning to migrate the remaining lists soon and likely migrating arch-general and aur-general as the last two lists. As part of the migration I'm disabling the "mangling" of the mails to keep the DKIM signature intact (i.e. no rewrite of the "from" header nor prefixing the subject with the list name), this means "reply list" must be used when replying to the list. For that reason I think the change is worth a news item, so the users know they must use "reply list" and that they may need to update their filters. I have created a draft here[2] which I hope to post after migrating the remaining lists (feel free to edit). Definitively worth a news item, I was confused not to see the list name in the email title and it breaks my workflow (which does not use filtering as that is not suitable to me, I need the list name to be visible in my INBOX view, so in the email title). wCPO pointed on IRC that sieve can add the [listname] part again in the email title as per https://superuser.com/questions/1502589, but we need the editheader extension to be enabled. Are there real concerns doing this? Thanks, Bruno/Archange
