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] Pushing without approval avfilter/vf_vignette: use AVFilterContext for logging
Date: Tue, 12 Aug 2025 19:20:52 +0200
Message-ID: <aJt39L-NcuYx5kLc@phare.normalesup.org> (raw)
In-Reply-To: <20250812120446.GB32174@haasn.xyz>

Niklas Haas (HE12025-08-12):
> As far as my understanding goes, only people with write access to the
> repository status have the ability to merge or approve PRs.

This is obviously wrong: write access to the repository is
all-or-nothing, expertise in parts of the code is not. This is why we
have maintainers.

With the recent clarification of who approved the series, we now know
that you had reliable but non-expert non-maitainer approval, which
should have let you wait a little less but not push immediately.

>								If you do not
> feel somebody can be trusted with write access, that is a separate issue
> irrelevant to this discussion.

Well, Michael has been giving these away like hotcakes recently, I can
think of two cases in recent months, but it is entirely unrelated to
this discussion.

> That aside, the person who reviewed the PR also has about 100x more activity
> than you

So what?

> Where in "MAINTAINERS" is this written?

An unfortunate oversight that will soon be rectified. But I believe it
should be common knowledge for somebody who has been in the project for
as long as you have, or for somebody who exchanged mails with me
recently on the very subject of libavfilter.

> Having a clearly defined process is a human solution to a human problem.

A bot is not a human solution.

-- 
  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-12 17:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250812090205.A5F4D68B0ED@ffbox0-bg.ffmpeg.org>
2025-08-12  9:16 ` Nicolas George
2025-08-12  9:34   ` Niklas Haas
2025-08-12  9:35     ` Niklas Haas
2025-08-12  9:38     ` Gyan Doshi
2025-08-12  9:51       ` Niklas Haas
2025-08-12  9:53         ` Nicolas George
2025-08-12 10:04           ` Niklas Haas
2025-08-12 17:20             ` Nicolas George [this message]
2025-08-12 15:57           ` James Almer
2025-08-12 17:13             ` Nicolas George
2025-08-12 12:35         ` Tristan Matthews via ffmpeg-devel
2025-08-12 15:59           ` Kacper Michajlow
2025-08-12 16:02             ` Niklas Haas
2025-08-12 21:22             ` Jean-Baptiste Kempf
2025-08-13  0:43               ` Michael Niedermayer
2025-08-13  0:57                 ` Timo Rothenpieler
2025-08-13 10:42                   ` Michael Niedermayer
2025-08-12 16:15           ` Yalda
2025-08-12 17:08             ` Nicolas George
2025-08-12 17:24               ` Yalda
2025-08-12  9:50     ` 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=aJt39L-NcuYx5kLc@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