Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Diederick C. Niehorster" <dcnieho@gmail.com>
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 23:06:40 +0200
Message-ID: <CABcAi1jdgV9u=cW-4E25g_Lwm+=UkTdoGHFu6R=3QSO3JQs6NA@mail.gmail.com> (raw)
In-Reply-To: <20250727204747.GU29660@pb2>

On Sun, Jul 27, 2025 at 10:48 PM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> Imagine people try to game this and we thus have more contributions and
> more reviewed, fewer unreviewed patches. That sounds like a good thing
> to me
>
> [...]
> Maybe iam just odd but i want to know if forgejo or the ML actually works
> better for the FFmpeg community before I decide how I vote.
> I assumed others also want to know that before they vote
>

IIRC, this test was supposed to run for a month. Given its a shift to
a new way of working, it will take a while before it catches on,
according to the above metrics. Probably longer than a month.
Are you, one of the main active reviewers, giving the forge a test
this month, using it exclusively instead of the ML? That alone will
sway the statistics tremendously.

All the best,
Dee
_______________________________________________
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-07-27 21:07 UTC|newest]

Thread overview: 47+ 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-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 [this message]
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-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='CABcAi1jdgV9u=cW-4E25g_Lwm+=UkTdoGHFu6R=3QSO3JQs6NA@mail.gmail.com' \
    --to=dcnieho@gmail.com \
    --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