From: "Martin Storsjö via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: Timo Rothenpieler via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Cc: "Martin Storsjö" <martin@martin.st>,
"Timo Rothenpieler" <timo@rothenpieler.org>
Subject: Re: [FFmpeg-devel] Mailman3 Upgrade
Date: Tue, 19 Aug 2025 09:55:26 +0300 (EEST)
Message-ID: <2d10307f-a882-9c39-79f-60fdaba3142@martin.st> (raw)
In-Reply-To: <38b3fd27-ad44-48e7-8d23-e5030262905d@rothenpieler.org>
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-devel@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-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2025-08-19 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 22:08 Timo Rothenpieler via ffmpeg-devel
2025-08-19 0:22 ` James Almer via ffmpeg-devel
2025-08-19 6:55 ` Martin Storsjö via ffmpeg-devel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d10307f-a882-9c39-79f-60fdaba3142@martin.st \
--to=ffmpeg-devel@ffmpeg.org \
--cc=martin@martin.st \
--cc=timo@rothenpieler.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git