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

[Hendrik Leppkes]

On Sat, Aug 14, 2021 at 2:42 AM Ronald S. Bultje <rsbultje at gmail.com> wrote:
>
> Hi,
>
> On Thu, Aug 12, 2021 at 4:51 AM Nicolas George <george at nsup.org> wrote:
>
> > Paul Buxton (12021-08-12):
> > > From the point of view of someone who is currently developing a filter
> > for
> > > ffmpeg and will be submitting a patch to the list for the first time, I
> > > think this is a great idea.Whilst following simple instructions to
> > prepare
> > > and submit a patch should't be outside the ability of anyone who is
> > capable
> > > of contributing. Using something like github allows a more automated
> > > workflow that can make the process smoother and even make lives easier
> > for
> > > the maintainers as it is possible for the automations to catch issues
> > > before they get sent on to you.
> >
> > Have you wondered why these periodical threads "we/you should make
> > FFmpeg more attractive" usually end up a discussion between disgruntled
> > newbies congratulating each other for their great ideas, with only the
> > occasional bored experienced developer stepping in?
> >
>
> Experienced dev speaking here: I absolutely 100% disagree with this
> statement. I would be much happier to actively contribute to FFmpeg if it
> used gitlab/hub. I find this mailinglist environment beyond horrendous. I
> can't understand why anyone would be OK with our current approach. I only
> grudgingly use it when I need to because I'm assuming I'm the minority and
> I'm willing to accept the majority consensus, but not because I support it
> or think it's a good idea.
>

As far as I can remember, the number of people that have spoken out in
favor of continued use of the ML solution is the minority, some are
just rather vocal about it, and the lack of a "perfect" replacement
solution has resulted in none being implemented.

Personally, I fully support Ronalds and Lynnes arguments. ML is not
fun to interact with, neither for maintaining your own patchset, nor
reviewing others. So many sets just get lost if the author doesn't
actively ping them regularly, and finding the history of a change is
always a quite annoying task
I'm in favor of any decently working hosted solution. I have worked
with GitHub, Gitlab, and bitbucket, and while none are "perfect" (I'm
not sure such a thing will ever exist), they are perfectly usable and
IMHO a much better experience all around.

I don't know if such a "bridge" is the solution, or if we should go
back to the discussion of moving the primary development to one of
those platforms.

- Hendrik