[FFmpeg-devel] [RFC] Suggestion for a Nicer Integration with GitHub

[Soft Works]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of
> Nicolas George
> Sent: Thursday, 12 August 2021 10:51
> To: FFmpeg development discussions and patches <ffmpeg-
> devel at ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nicer Integration
> with GitHub


> TL;DR: Do not make posting patches on the mailing-list easier, make a
> two-tiered system where beginners learn to make high-quality patches
> before submitting them for review to the experienced developers.
> 
> You all seem to assume that attracting more developers is always a
> good
> thing.
> 
> It is if it attracts promising developers, i.e. if it widens the
> horizon.
> But more developers is not a good thing if it is done by lowering the
> bar, because the more developers will be mediocre and as such a drain
> on
> the time of core developers.

Assuming that developers who submit patches via GitHub would be less
skilled than those who work with a mailing list is arrogant and 
far away from reality.


I have my opinion about mailing-list development in the year 2021
and I could express that in a strong way and with a similar kind
of arrogance.

But it makes much more sense to accept that there are some who 
prefer to view patches in e-mail clients with hundreds of plus/minus
lines and others that prefer to view diffs in context and with 
a decent graphical representation.
That has nothing to do with skills. It's just a preference.
Right now, you are excluding all those that do not like to 
work "your way".


IMO there's one thing you really do not need to be concerned
about: getting rid of unskilled developers.
You all need to just continue like usual and this will happen
all the way without effort and without needing a rejection
form. :-)

Lastly - what I'm suggesting appears to work for GIT development.
Why shouldn't it work for ffmpeg then?

softworkz