[FFmpeg-devel] To be or not to be working with libav (was: [PATCHv3] On2 VP7 decoder)
vittorio.giovara at gmail.com
Sun Apr 6 20:41:03 CEST 2014
On Sunday, April 6, 2014, Nicolas George <george at nsup.org> wrote:
> Le septidi 17 germinal, an CCXXII, Vittorio Giovara a écrit :
> > The easiest solution would be to stop the daily merge and let the two
> > projects live on their own
> You keep suggesting that: what good do you think that would achieve?
Foss projects foster on innovative ways of tackling problems, and that
pushes developers to improve their code. When a project keeps pulling
features from another and adding on top of it, it stifles competition and
demotivates developers, with the end result that *less* open source code is
Also Libav code is so ill received most of the times that I seriously can't
figure out why this is still happening. The two projects have completely
separate design approach and dev model so it's really difficult to
understand, in my opinion
When a new feature arrives in avconv, what happens if it is not merged into
> ffmpeg? Shall it be left out? Or re-implemented independently?
Being left out until someone actually needs it is a way. Otherwise you just
get complaints and unnecessary features that might collide with your design
goals. See for example the mv visualization deprecation and undeprecation
of a few days ago or many others I could quote.
> The first one is bad for the users, the second one is a waste of
This whole downstream situation is bad for users and developers. This is
why I'm insisting to get past each other differences and see if there is
room for collaboration, rather than one-way pulling.
> Nicolas George
More information about the ffmpeg-devel