Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org
Date: Sun, 27 Jul 2025 00:44:09 +0200
Message-ID: <20250726224409.GS29660@pb2> (raw)
In-Reply-To: <9ba27e8b-f890-4b34-a2a0-6245bb050145@rothenpieler.org>


[-- Attachment #1.1: Type: text/plain, Size: 2103 bytes --]

Hi Timo

On Sat, Jul 26, 2025 at 10:41:57PM +0200, Timo Rothenpieler wrote:
> On 7/26/2025 10:24 PM, Kacper Michajlow wrote:
> > On Sat, 26 Jul 2025 at 22:14, Timo Rothenpieler <timo@rothenpieler.org> wrote:
> > > 
> > > On 7/26/2025 10:01 PM, Derek Buitenhuis wrote:
> > > > On 7/26/2025 8:29 PM, Timo Rothenpieler wrote:
[...]
> > Also, I don't think the current ML workflow is very sophisticated on
> > ffmpeg-devel, so there are likely not many tools to migrate to the new
> > one.
> 
> You'd be surprised about the sophisticated tooling a lot of people have
> built around patch wrangling via a mailing-list.
> 
> A lot of people will need to learn an entire new workflow, and I can
> absolutely understand that being forced to do so from one day to the next is
> very disruptive and off putting.

yes, we need decissions that everyone is on board with, even if they
did not vote for the winning choice.

I think the gitlab vs forgejo decission was such a decission, it had
a very clear outcome.

This testing period can show that forgejo works better and that it leads
to more contributors and fewer unreviewed patches.
Or it can fail to do so.

I think having the result of that testing, could convince most people
which is the right choice


[...]
> 
> > It's just my personal opinion and it doesn't reflect anyone else in
> > the community.
> 
> I'm completely with you that we desperately need to move forward.
> But there just are a lot of people who've been with the project for a long
> time who are not comfortable with it or outright reject it.
> Do we really want to just leave them behind, and not even give them a chance
> to learn new tools?

yes, exactly, i think we should make sure everyone moves together

and just speaking about myself how do i replace git send email ?
do we have a drop in replacement for that ?

will reply to the suggestion in a seperate mail

thx
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

No great genius has ever existed without some touch of madness. -- Aristotle

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 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".

  parent reply	other threads:[~2025-07-26 22:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22  3:53 Lynne
2025-07-22  8:44 ` Kacper Michajlow
2025-07-22  9:15   ` Jacob Lifshay
2025-07-25  3:40     ` compn
2025-07-25  3:58       ` Jacob Lifshay
2025-07-25  4:36         ` compn
2025-07-25 11:41         ` Nicolas George
2025-07-25 14:20           ` Kieran Kunhya via ffmpeg-devel
2025-07-23  4:05   ` Lynne
2025-07-22 15:01 ` Leo Izen
2025-07-23  4:01   ` Lynne
2025-07-22 23:04 ` Michael Niedermayer
2025-07-23  4:01   ` Lynne
2025-07-23  9:16     ` Michael Niedermayer
2025-07-23  9:39       ` Kieran Kunhya via ffmpeg-devel
2025-07-23  9:59         ` Michael Niedermayer
2025-07-23 10:02           ` Kieran Kunhya via ffmpeg-devel
2025-07-23 11:48           ` Nicolas George
2025-07-25  4:05           ` compn
2025-07-26 14:57             ` Michael Niedermayer
2025-07-23  9:38     ` Michael Niedermayer
2025-07-23 11:49       ` Nicolas George
2025-07-26 17:03 ` Derek Buitenhuis
2025-07-26 19:29   ` Timo Rothenpieler
2025-07-26 20:01     ` Derek Buitenhuis
2025-07-26 20:14       ` Timo Rothenpieler
2025-07-26 20:24         ` Kacper Michajlow
2025-07-26 20:29           ` Derek Buitenhuis
2025-07-26 20:41           ` Timo Rothenpieler
2025-07-26 20:45             ` Derek Buitenhuis
2025-07-26 21:07             ` Kacper Michajlow
2025-07-26 21:18               ` Timo Rothenpieler
2025-07-26 22:44             ` Michael Niedermayer [this message]
2025-07-26 22:57               ` Timo Rothenpieler
2025-07-26 22:48             ` Michael Niedermayer
2025-07-26 20:28         ` Derek Buitenhuis
2025-07-26 20:14     ` Kacper Michajlow
2025-07-26 20:23       ` Timo Rothenpieler
2025-07-26 20:29         ` Kacper Michajlow
2025-07-26 20:33           ` Derek Buitenhuis

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=20250726224409.GS29660@pb2 \
    --to=michael@niedermayer.cc \
    --cc=ffmpeg-devel@ffmpeg.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