[CentOS-es] FW: [CentOS-announce] [Infra] - Planned outage : lists.centos.org (migration to mailman3) : please read

[orkcu]

Hola a todosYa se que esta lista no tiene trafico desde hace bastante tiempo pero aun así creo que es importante pasar este mensaje.Un saludoRoger
-------- Original message --------From: Fabian Arrotin <arrfab en centos.org> Date: 2024-04-02  10:27 a.m.  (GMT-05:00) To: "The CentOS developers mailing list." <centos-devel en centos.org> Cc: CentOS mailing list <centos en centos.org>, ci-users en centos.org, centos-announce en centos.org Subject: [CentOS-announce] [Infra] - Planned outage : lists.centos.org (migration to mailman3) : please read Due to a needed upgrade , we'll have to move the existing CentOSmailman instance (aka https://lists.centos.org) to a new server/host.Migration is scheduled for """"Tuesday April 8th, 7:00 am UTC time"""".You can convert to local time with $(date -d '2024-04-08 07:00 UTC')The expected "downtime" is estimated to ~60 minutes , time needed to :- take last mailman2 backup- reimport / convert mailman2 archives to mailman3 DB- DNS propagation for A/AAAA/MX recordsHere are also some important information about the mailman2 => mailman3 migration :# Renamed listsWorth knowing that, based on open discussion on the centos-devel list (see whole thread at https://lists.centos.org/pipermail/centos-devel/2024-March/165576.html), existing lists will be *renamed* , so while we'll put aliases for incoming mails, each list member will start receiving list mails from new list name. So start updating your filters if you filter on email address instead of "subject:"Here is the overview of the new lists names :arm-dev at centos.org => arm-dev at lists.centos.orgcentos at centos.org => discuss at lists.centos.orgcentos-devel at centos.org => devel at lists.centos.orgcentos-announce at centos.org => announce at lists.centos.orgcentos-automotive-sig at centos.org => automotive-sig at lists.centos.orgcentos-{cz,de,es,fr,nl,pt-br,zh}@centos.org => discuss-{cz,de,es,fr,nl,pt-br,zh}@lists.centos.orgci-users at centos.org => ci-users at lists.centos.orgcentos-gsoc: => gsoc at lists.centos.orgcentos-mirror at centos.org => mirror at lists.centos.orgcentos-mirror-announce at centos.org => mirror-announce at lists.centos.orgcentos-newsletter at centos.org => newsletter at lists.centos.orgcentos-promo at centos.org => promo at lists.centos.orgcentos-virt at centos.org => virt at lists.centos.org# AuthenticationMailman2 had no real concept of authentication so you could just subscribe to one or more lists, and have a password associated with your email address for that/these subscription(s).Mailman3 itself is split into "core" and "webui" components, so when we'll import mailman2 lists/config into mailman3, your existing subscriptions will continue to work *but* not your password.Mailman3 will be configured to support SSO, and so if you already have a FAS/ACO account (https://accounts.centos.org) you'll be able to login directly into new webui and manage your settings/subscriptions *if* your ACO email address of course matches the one you initially subscribed with for lists.centos.org.If that's not the case, either create an ACO/FAS account that will match and you'll be then able to "link" your mailman3 account with FAS and so manage your settings/subscriptions.If you don't want to, there is always the documented process : https://docs.mailman3.org/en/latest/userguide.html#making-a-mailman-accountThanks for your understanding and patience.on behalf of the Infra team,-- Fabian ArrotinThe CentOS Project | https://www.centos.orggpg key: 17F3B7A1 | @arrfab[@fosstodon.org]