From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org
Date: Sat, 26 Jul 2025 21:29:23 +0200
Message-ID: <c16b0eef-03a5-4e28-a7fb-79916a9f7838@rothenpieler.org> (raw)
In-Reply-To: <eb23bc68-6634-4c3a-acb2-5b99323a3d97@gmail.com>
On 7/26/2025 7:03 PM, Derek Buitenhuis wrote:
> On 7/22/2025 4:53 AM, Lynne wrote:
>> ---
>> src/contact | 11 +++++++++++
>> src/index | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 2 files changed, 63 insertions(+)
>
> So I am a bit unclear, is development now Forgejo or ML, or both?
>
> Because right now, it seems like both, and that is basically the worst
> possible outcome. It is very difficult to follow both, and the amount
> of people reviewing or even looking at patches on either is now significantly
> splintered/reduced, allowing lower quality code to wade itself in the meantime,
> IMO.
>
> Also, as far as I can tell, the git access list was not really carried over in
> any way.
>
> It all seems a bit chaotic and directionless... or rather, with 0 plan.
It's still an extended test. You cannot push to it, since it's just a
mirror.
How do you expect to suddenly switch every last person over from the ML
to a new tool?
There's always going to be a transition period where both are in use,
gradually shifting.
So yes, for now there needs to be eyes on both.
Hopefully pushing to it/hitting the merge button should be possible soon
(hinges on cooperation with Videolan), making more people look at it and
subscribe to E-Mail notifications of what's going on there.
I also still intend to write a script that forwards at least PRs to the
ML for the time being, without causing the massive spam that just
forwarding notifications does.
_______________________________________________
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".
next prev parent reply other threads:[~2025-07-26 19:29 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 [this message]
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-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=c16b0eef-03a5-4e28-a7fb-79916a9f7838@rothenpieler.org \
--to=timo@rothenpieler.org \
--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