[FFmpeg-devel] [PATCH v3 0/7] Merge lazy filter initialization in ffmpeg CLI

James Almer jamrial at gmail.com
Thu Mar 2 21:32:36 EET 2017


On 3/2/2017 2:27 PM, wm4 wrote:
> Well, you already announced that you'd leave the project a few months
> ago or so, but nothing happened. As an (apparently involuntary) de-facto
> project leader who refuses to fix the leadership associated problems of
> the project, it's of course not strange that you get attacked once in a
> while. Even if you deny being a project leader, you hold a tad too many
> central key positions.
> 
> I realize you probably just want to write code and not deal with these
> issues. But on the other hand it seems you're stuck in this position
> whether or not you or we want it. The best idea I can come up is to
> nominate a new project leader, but I don't know who could do that _and_
> keep the project together.

Big project decisions pass through the voting committee now. Is it flawed
and too crowded? yes, but it's better than total anarchy.

Nothing Michael's doing in this thread by reviewing your patchset is even
remotely related to being a project leader. His emails and regression
reports could have come from anyone else and have the same effect on this
patchset.

I understand your frustration, as i also had to go through several
iterations of a big merge like this one after Michael pointed out some
regressions, including identifying some false positives like the timebase
change he reported earlier today, but it doesn't justify lashing out at
people who are simply pointing out issues.

> 
> Currently, we as a project can't make decisions, and nobody even knows
> the damn rules we're supposed to play by. If it's just me, could
> someone please set me straight?

This is not true, we have had several votes by now with different results.
API decisions, deprecation/removal decisions, etc.
I liked some, i hated others, but respected all of them. Everyone did.



More information about the ffmpeg-devel mailing list