Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Recommendations to facilitation patch reviews on forgejo/ML?
Date: Sat, 2 Aug 2025 17:38:40 +0200
Message-ID: <aI4xAO0f8vJ2lxps@phare.normalesup.org> (raw)
In-Reply-To: <CABWZ6ORauvEO5Yw3zX24sNbWNYMtiK4NLHOj+nHgSupQAFZc_g@mail.gmail.com>

Romain Beauxis (HE12025-08-02):
> Casual contributors eventually become knowledgeable about the
> framework/code base which eventually leads to some of them becoming
> seasoned developers and reviewers.
> 
> If you want to grow the number of people working with the project, you've
> got to be able to open the funnel and welcome new contributors.

It does not work like that. The issue is not the total number of people
working on the project but the ratio of senior members capable of
reviewing patches over patch submissions.

By opening “the funnel” wider, you might attract more people
contributing patches, but these people will not become capable of
reviewing patches.

Somebody who has what it takes to become a reviewer does not need the
funnel to be widened for them.

> That being said, I understand that these tools are making your work more
> difficult and how this potentially reduces again the ability for people to
> get reviews.

Precisely.

> On a personal level, I can attest, regardless of the tools being used, it
> is currently incredibly hard to get feedback on your contributions.

And it will become worse, because your good contributions will be
drowned in crappy contributions by people who just needed to click on
“login with github” and “create a pull request” without even reading our
guidelines.

Regards,

-- 
  Nicolas George
_______________________________________________
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-08-02 15:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29 21:42 Romain Beauxis
2025-07-29 21:52 ` Nicolas George
2025-08-01 23:17   ` Romain Beauxis
2025-08-02  9:59     ` Nicolas George
2025-08-02 12:48       ` Kacper Michajlow
2025-08-02 12:50         ` Nicolas George
2025-08-02 15:07       ` Romain Beauxis
2025-08-02 15:38         ` Nicolas George [this message]
2025-07-31 11:12 ` Rémi Denis-Courmont
2025-08-01 23:19   ` Romain Beauxis

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=aI4xAO0f8vJ2lxps@phare.normalesup.org \
    --to=george@nsup.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