On Tue, 19 Aug 2025, Timo Rothenpieler via ffmpeg-devel wrote:
mailman2 has no good way to deal with that in a more reasonable way.
Mailman3 is already set up, and can be migrated to at a moments notice.
The only problem with it is that I really don't like the new archives.
It has ways to better deal with it, like better DMARC/SPF/... support in
general, and support for ARC signing.
As an example, I already migrated nut-devel:
https://lists.ffmpeg.org/archives/list/nut-de...@ffmpeg.org/latest
Sooner or later, we will have to migrate no matter what.
Python2 is on its way out, and we will have to upgrade to an OS version that
does not ship it anymore eventually.
So the question is, should I just migrate ffmpeg-devel, and if that goes
well, pull over all the other lists as well?
In theory the migration should go without anyone noticing. It worked for
nut-devel, but that's not exactly the most active list.
Can the old archives be kept in their current location (assuming they
don't fully alias the new URLs?) even if they don't get updates, in order
to keep current references working? References to old mails through such
URLs is quite common.
Judging from nut-devel, the old archives for that seem to be intact and
available, so hopefully this is not an issue.
// Martin
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
