Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: James Almer <jamrial@gmail.com>
Subject: Re: [FFmpeg-devel] Mailman3 Upgrade
Date: Mon, 18 Aug 2025 21:22:53 -0300
Message-ID: <4155a4c2-415d-4a15-b860-916e31c17d36@gmail.com> (raw)
In-Reply-To: <38b3fd27-ad44-48e7-8d23-e5030262905d@rothenpieler.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1863 bytes --]

On 8/18/2025 7:08 PM, Timo Rothenpieler via ffmpeg-devel wrote:
> Hi!
> 
> As you might have noticed, a bunch of big Mail-Hosters have introduced 
> new, even stricter, requirements. Primarily it's Microsoft, but others 
> seem to already have followed suit.
> So we had to configure the list to send all mails as coming from the 
> list itself.
> 
> At least to me this seems highly annoying and makes it hard at times to 
> immediately see who the mail is even from.
> 
> 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?

IMO yes. The archive, while ugly, should not be a blocker to make the 
mailing list more usable for everyone (Plus it allows us to update the 
server distro).

> 
> In theory the migration should go without anyone noticing. It worked for 
> nut-devel, but that's not exactly the most active list.
> 
> 
> 
> Timo
> 
> _______________________________________________
> 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".


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

  reply	other threads:[~2025-08-19  0:23 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 [this message]
2025-08-19  6:55 ` Martin Storsjö via ffmpeg-devel

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=4155a4c2-415d-4a15-b860-916e31c17d36@gmail.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=jamrial@gmail.com \
    /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