[FFmpeg-devel] [VOTE] FFmpeg leader
Sat Oct 2 22:40:12 CEST 2010
On 10/2/10 8:05 AM, Diego Biurrun wrote:
> On Fri, Oct 01, 2010 at 11:12:23PM -0700, Baptiste Coudurier wrote:
>> On 10/1/10 11:09 PM, Jason Garrett-Glaser wrote:
>>> On Fri, Oct 1, 2010 at 10:57 PM, Felipe Contreras
>>> <felipe.contreras at gmail.com> wrote:
>>>> On Sat, Oct 2, 2010 at 8:47 AM, Jason Garrett-Glaser
>>>> <darkshikari at gmail.com> wrote:
>>>>> And since your maintainership covers all of ffmpeg, that gives you the
>>>>> right to change whatever you want without asking anyone.
>>>>> How about no.
>>>> In some projects, like git.git, the maintainer sends his patches to
>>>> the mailing list like everybody else. If nobody shouts, he pushes. I
>>>> believe this is the most sensible approach; the maintainer should not
>>>> be considered a flawless god whose opinion is above everybody else,
>>>> and thus his patches should not be considered error free, nor
>>> I agree. Not even Linus commits his patches unquestionably; Michael
>>> should be the same.
>> Well FFmpeg is not like the kernel (where everybody is paid to do the
>> job) nor a major project like git which has many contributors.
> FFmpeg is smaller than the kernel, but smaller than git? I cannot find
> any numbers to support this theory, on the contrary...
Not really, I mean that git is a "major" project that everybody knows
about. I think more people know about git than ffmpeg, I guess they have
more contributors, but maybe I'm wrong about this.
>> I would personnally be really annoyed to send patches to files I
>> maintain. I do however pay really attention to comments made on -cvslog,
>> and I address them. Many people review on -cvslog as well.
>> Given the coverage FFmpeg svn has now thanks to FATE, this is reasonable
>> IMHO, and avoids the burden.
> I agree for not too large changes to files you maintain, but if you make
> large changes or API changes, then review and comments will always be
> valuable. You just sent a patch for MOV autocrop, which is something
> you maintain...
Yes, I tend to follow "principles", I'm glad people fix typos in files I
maintain or fix really obvious mistakes.
I myself fixed the h263 encoder yesterday, and I perfectly fine with
people doing the same in the code I maintain.
Besides, this is not the first time I fix issues like the h263
resolution check directly and I've not received the wrath of Michael nor
anybody. That shows, IMHO, that people are reasonable and understand.
The problem is the bikeshed and being unreasonable about features and
The comments on the mov auto-crop once again show it.
We maintainers can hardly code and review at the same time, because we
Key fingerprint 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA
FFmpeg maintainer http://www.ffmpeg.org
More information about the ffmpeg-devel