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] [PATCH] web: announce code.ffmpeg.org
Date: Wed, 30 Jul 2025 23:55:10 +0200
Message-ID: <aIqUvmowHLyu9nwQ@phare.normalesup.org> (raw)
In-Reply-To: <CABPLASS+2=w8N+Sd8h38vYbtEDqReKBENfbwFe3f7s4_zoHNjQ@mail.gmail.com>

Kacper Michajlow (HE12025-07-27):
> I'm talking about ffmpeg specifically. ffmpeg is not a Linux kernel,

Nobody talked about the Linux kernel, I do not know what nonsense you
are spewing here.

But you do not seem tu realize that the best hackers in the project (not
you) have nothing to do with the best hackers in the Linux kernel.

> I don't mean to offend

You know perfectly well that any sentence that starts like that is a lie
and is meant to offence.

> Tools are only good as you use them.

Yet, other people manage to use mail efficiently to interact with the
project.

So, what does it mean when a person does not manage to achieve a task
when others do?

Option 1: that person is incompetent.
Option 2: that person is using bad tools.
Option 3: both.

(Remember, choosing good tools is part of competence.)

> Instead of insulting and antagonizing people every other day, why
> don't you use your superior email and tooling to actually help with
> reviewing patches and implementing code?

The fact that you do not realize that I have been doing that for fifteen
years shows how little you know.

Also, I was only invited officially after more than four years of
contributing, including non trivial patches and significant new
features. Apparently, nowadays, all it takes is a few months of moving
code around and fixing warnings.

> And what process is that? Those vague guidelines in the "Contributing"
> document?

The one you should be building for yourself if you have what it takes to
be useful here.

> The web forges may not be perfect and employ a certain pipeline of
> working, but they make the entry point the same for every contributor.

I do not care about every contributor, I care about skilled
contributors.

> "We". The current move is not happening without a reason and not
> happening on a whim.

It is happening because many people here are too nerdy to remember that
a human problem cannot be fixed with technical solution. The issue with
reviewing patches is that we do not have enough people who know the code
well enough to review them. Making it easier to flood us with crappy
patches written by AI will not make it better.

> I understand fear of a change.

Please keep this condescending bullshit to yourself.

-- 
  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-07-30 21:55 UTC|newest]

Thread overview: 51+ 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-31 19:38           ` Rémi Denis-Courmont
2025-07-31 21:16             ` Nicolas George
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
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-30 21:55               ` Nicolas George [this message]
2025-07-26 20:28         ` Derek Buitenhuis
2025-08-01  8:49         ` Rémi Denis-Courmont
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=aIqUvmowHLyu9nwQ@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