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 22:47:47 +0200 Message-ID: <20250727204747.GU29660@pb2> (raw) In-Reply-To: <20250727140722.GB7604@haasn.xyz> [-- Attachment #1.1: Type: text/plain, Size: 1671 bytes --] Hi Niklas On Sun, Jul 27, 2025 at 02:07:22PM +0200, Niklas Haas wrote: > On Wed, 23 Jul 2025 01:04:34 +0200 Michael Niedermayer <michael@niedermayer.cc> wrote: > > The announcment should probably mention that performance, as in number of > > submissions / percentage of applied / not reviewed patches will be > > monitored compared to the mailing list. > > https://en.wikipedia.org/wiki/Goodhart%27s_law I dont think the conditions of this are fullfilled [...] > Besides, > performance metrics can be gamed. Yes, if you know them AND you have an incentive to do so. Do you know them ? Do you (or anyone else here) have an incentive to game them ? I do think we all just want to make the right decission But theres a 3rd point, lets assume the metric is more contributions and more reviewed, fewer unreviewed patches. 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 > I think it would be better to just put it > to a vote, as was initially discussed (iirc). The only thing that should > matter is what the community *prefers* to use. For every vote, the people voting need to be provided with as much good information as possible. 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 thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Give a rich man 100$ and he will turn it into 1000$. Give a poor man 1000$ and he will spend it. [-- 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".
next prev parent reply other threads:[~2025-07-27 20:48 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 [this message] 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-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=20250727204747.GU29660@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