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: Wed, 23 Jul 2025 11:38:00 +0200
Message-ID: <20250723093800.GI29660@pb2> (raw)
In-Reply-To: <c9edbcdd-402d-4fec-97bc-0659400372fb@lynne.ee>


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

Hi Lynne

On Wed, Jul 23, 2025 at 01:01:06PM +0900, Lynne wrote:
> 
> 
> On 23/07/2025 08:04, Michael Niedermayer wrote:
> > Hi Lynne
> > 
> > On Tue, Jul 22, 2025 at 12:53:29PM +0900, Lynne wrote:
[...]
> > > +  <p>
> > > +    We are also hoping that this will significantly reduce the amount of unmerged patches.
> > > +    If you submitted a patch which received no replies or conclusion, we apologize, and you are encouraged
> > > +    to resubmit it on the new platform.
> > > +  </p>
> > 
> > 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.
> > 
> > (and obviously someone has to do that, i do think such basic performance
> >   monitoring is important after/ during such a change)
> > 
> > later then (in a month or whatever) we should make an announcment with
> > the performance numbers
> 
> We all know there were plenty of patches left over. What we need to do is to

yes, but the patches arent "forgotten". Everyone, including myself have them
in their ffmpeg-devel mailbox.

Iam not reviewing them not because iam unaware of them but because its just
way too many patches for one person, who than also has many other things to do
besides reviewing patches.

Once one understands this, the solution should be clear
1. we have to split up responsibilities, that is the maintainers system
   each area should have a maintainer who would not waste time with noise outside
   her area. And also not have to endlessly argue with people not maintaining the
   specific code.
2. hire more reviewers/maintainers, so we have more manpower, FFlabs and STF are
   options here, both these options should be used.
3. better tools to get the right patches to the right reviewer with less work,
   I hope forgejo will achieve this
4. We should try to shift work that others can do, away from key people,
   so they have more time for work that we have noone else who can do it.

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

z(9) = an object that transcends all computable functions describable
in finite terms. - ChatGPT in 2024

[-- 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-23  9:38 UTC|newest]

Thread overview: 15+ 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-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-23  9:38     ` Michael Niedermayer [this message]
2025-07-23 11:49       ` Nicolas George

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=20250723093800.GI29660@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