3 ms·
Forking a project should be reserved for when a project becomes - by some objective criteria - abandoned and there is enough support for the project to continue
by icebraining 11y ago
Forking a project should be reserved for when a project becomes - by some objective criteria - abandoned and there is enough support for the project to continue. Then and only then should a project with a large amount of traction be forked.
What about Hudson/Jenkins and OpenOffice/LibreOffice? And egcs?
I think criticizing forking is misguided; the fork is a consequence of the problem, not the cause, and it can often be the best resolution of a bad situation.
Consider what would have happened if it was impossible to fork ffmpeg: the developers who created libav would still have a problem with how ffmpeg was developed, and they could very well simply leave it. That would mean a loss to ffmpeg itself (which used the libav patches), a loss of the libav developers, and for what?