3 ms·
libav was the hostile fork, not FFmpeg. Someone removed write permissions from key contributors (or contributor. I forget) and just about everyone sided with th
by fluoridation 3y ago
libav was the hostile fork, not FFmpeg. Someone removed write permissions from key contributors (or contributor. I forget) and just about everyone sided with those contributors, thus the instigators were forced to rename their project. The development effort stayed on FFmpeg, even as the libav people tried porting back the changes. Eventually libav passed into irrelevance as it failed to acquire mindshare and distributions stopped including it.
- Xenoamorphous 3y agoIt's been a while since I read the story but I believe it did prompt some changes in ffmpeg management, that's why I was saying it was a hostile fork success story.
- dralley 3y agoglibc would be a better example in that case.