Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Vittorio Giovara <vittorio.giovara@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] MAINTAINERS: remove myself from FFmpeg
Date: Tue, 19 Dec 2023 15:34:53 -0500
Message-ID: <CABLWnS8PSBoa-ZzGzE-xu18oMBceEAuD63HNTjgvM-mD-kaMQA@mail.gmail.com> (raw)
In-Reply-To: <ZYGWllrMC5BVHmLk@phare.normalesup.org>

On Tue, Dec 19, 2023 at 8:12 AM Nicolas George <george@nsup.org> wrote:

> Rémi Denis-Courmont (12023-12-07):
> > You have had heated arguments against Paul in recent times too. You have
> also
> > argued a lot of exercising your review privileges, which sounds like a
> very
> > libavish notion to me
>
> Only because you were not there at the time to get a first-hand
> impression. That patches should be reviewed if possible was the policy
> way before libav. That came with a set of implicit rules: waiting a few
> days, then pinging, then waiting a few days and only then pushing
> without review. The role of maintainer would affect the reasonable value
> for “a few” days.
>
> Paul insistence on pushing after barely 24 hours on code with a
> maintainer that is not him always contradicting the way of doing things.
>
> Furthermore, his refusal to give more time to the maintainer when asked
> to is not just that: it is a level of rudeness and incivility
> incompatible with working together with other people.
>
> But Paul's attitude was annoying but never a real problem: resist his
> eagerness a little and soon he finds something else to do and forgets
> about pushing immediately for weeks or months.
>
> For reference, libav turned the practice that patches should be reviewed
> into a hard rule that patches must be reviewed. At the same time, since
> they had kicked out or disgusted a significant part of the projects'
> maintainers, they had nobody capable of actually reviewing the code. As
> a result, when a patch was proposed by a major libav contributor, after
> the ping somebody else who did not know the code would post a clueless
> “LGTM”.
>
> (The online archives of libav-devel seem to have disappeared, so I
> cannot link to the example I bookmarked.)
>

I am not too sure that bringing up a topic from 12 days ago with arguments
from 12 years ago is bringing any value to the conversation. Just as a
note, remember that a clueless LGTM is a better review than NO review, and
in fact it's the system that it's employed in any modern software house:
the master branch is usually protected and any PR/MR needs both CI pass and
at least a read from a developer.

Oh and for the sake of your (and our readers') time, don't bother replying,
I'm not interested in discussing 12 years ago affairs or modern development
practices here. I do invite you to evaluate whether your vision of ffmpeg
is still the one shared by the community as a whole though.

Regards
-- 
Vittorio
_______________________________________________
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:[~2023-12-19 20:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07  7:29 Paul B Mahol
2023-12-07  8:54 ` Jean-Baptiste Kempf
2023-12-07  8:59   ` Nicolas George
2023-12-07  9:06     ` Jean-Baptiste Kempf
2023-12-07  9:10       ` Nicolas George
2023-12-07  9:12         ` Jean-Baptiste Kempf
2023-12-07  9:14           ` Nicolas George
2023-12-07  9:16             ` Jean-Baptiste Kempf
2023-12-07 14:59     ` Leo Izen
2023-12-07 16:32       ` Nicolas George
2023-12-07 16:48         ` Leo Izen
2023-12-07 16:39     ` Rémi Denis-Courmont
2023-12-19 13:11       ` Nicolas George
2023-12-19 20:34         ` Vittorio Giovara [this message]
2023-12-20  9:17           ` Nicolas George
2023-12-07 12:32 ` Michael Niedermayer
2023-12-07 14:29   ` Ronald S. Bultje

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=CABLWnS8PSBoa-ZzGzE-xu18oMBceEAuD63HNTjgvM-mD-kaMQA@mail.gmail.com \
    --to=vittorio.giovara@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