A leadership change at FFmpeg
A leadership change at FFmpeg
Posted Aug 3, 2015 17:16 UTC (Mon) by lu_zero (guest, #72556)In reply to: A leadership change at FFmpeg by andrey.turkin
Parent article: A leadership change at FFmpeg
And sadly lots of people seem to argue about bad is our code (and yet take it as-is) or we hare horrible people (and yet not even knowing us). I'm not really looking forward to see another batch of death threats on our direction again, but I'm sure the one opening this thread won't be the last.
I postponed to do most of the interesting and non-paid stuff mainly because I have a dayjob that is not so related to Libav and after I got people telling me FFmpeg is asking for donations pigging backing on my work I rather wait. If I need to do something I do.
The reason why Libav
- is managed through consensus
- does not have territorial codebases (MAINTAINERS in FFmpeg)
- does have a quite simple and immediate Code of Conduct (see the about page)
is spurred from the fact the way FFmpeg is managed was horrid and only the most abrasive personalities would survive.
The reason why Libav requires
- compulsory review before commit
- a (optional, until we get enough hardware) CI run before it hits (see https://wiki.libav.org/Oracle)
- has lots on emphasis on making the code CLEAR first (see https://wiki.libav.org/CodingStyle)
is that we do want to make sure more people are able to contribute and everybody can actually touch all the codebase safely.
There is no fence, anybody can pick a patch and send it over the mailing list, Libav is an open project.
Regarding QSV btw:
http://article.gmane.org/gmane.comp.video.ffmpeg.devel/19...
Great way to take my and Anton's code and break it...
Posted Aug 13, 2015 11:07 UTC (Thu)
by jch (guest, #51929)
[Link] (1 responses)
I think the warning message in Debian's "ffmpeg" command-line tool alienated a lot of people.
Posted Aug 14, 2015 22:59 UTC (Fri)
by nix (subscriber, #2304)
[Link]
A leadership change at FFmpeg
A leadership change at FFmpeg
