Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org
Date: Fri, 01 Aug 2025 11:49:43 +0300
Message-ID: <E2D2DC9A-22DE-47D3-A789-3D9241218469@remlab.net> (raw)
In-Reply-To: <8ec2eab1-1a2e-4607-9186-3d55c9335e3a@rothenpieler.org>



Le 26 juillet 2025 23:14:08 GMT+03:00, Timo Rothenpieler <timo@rothenpieler.org> a écrit :
>> You do it once, decisively, with no point where it is both dev paths simultaniously.
>> VideoLAN managed it, and countless companies and other projects have managed it with
>> no overlap. Many of which I have experienced first hand. It's one thing to slowly
>> move projects from an org/community over, but having several extant methods of
>> contributing and reviewing the same repo's code is pretty much the #1 thing that
>> is avoided.
>
>Videolan hat the exact same transitional period, where both the ML and Gitlab were in use for at least a couple months to half a year.

That is misleading. Different projects were migrated at different times, over a period of several years. But there never was cohabitation of -devel MLs and gitlab repos for code review and patch submission, for any project.

As the one person who had both most contributions and most objections to Gitlab, I think I'd know.

>vlc-devel is still active to this day, even with the very occasional stray patch still landing there, just not for patches.

Yes, but that's not Derek's point.

Also vlc-devel is pretty moribond at this point. The occasional non-code technical discussions take place mostly in the issue tracker or in meetings.


>How do you intend to get everybody into one boat to move over all at once?
>VLC has a central governing body who is able to make such decisions and force the issue if need be.
>FFmpeg does not, so I don't see who would be able to make such a call, and specially then also have everyone follow it.

FFmpeg has a GA who can vote on this, just like VideoLAN. It's just not formalised in a legal document.
_______________________________________________
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-08-01  8:50 UTC|newest]

Thread overview: 51+ 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-31 19:38           ` Rémi Denis-Courmont
2025-07-31 21:16             ` Nicolas George
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-27 12:07   ` Niklas Haas
2025-07-27 12:41     ` Nicolas George
2025-07-27 20:47     ` Michael Niedermayer
2025-07-27 21:06       ` Diederick C. Niehorster
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
2025-07-26 22:57               ` Timo Rothenpieler
2025-07-26 22:48             ` Michael Niedermayer
2025-07-27  9:40             ` Nicolas George
2025-07-27  9:39           ` Nicolas George
2025-07-27 16:48             ` Kacper Michajlow
2025-07-30 21:55               ` Nicolas George
2025-07-26 20:28         ` Derek Buitenhuis
2025-08-01  8:49         ` Rémi Denis-Courmont [this message]
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=E2D2DC9A-22DE-47D3-A789-3D9241218469@remlab.net \
    --to=remi@remlab.net \
    --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