Forking a project is a good thing? Yes, being able to create forks of a project is good. Having a fork, or several, of any given project gives people options, making it possible for users to be able to choose from different proposals the one that better works for them.
The real question when it comes to forks, is whether or not any values is added. If no value is added, then there is little motive for users to move to the fork and it adds to the stock of options made available to developers to work with.
Forks are valuable for the project's community at large, since they widen the capabilities of the software by adding features or simply by giving options on the way to implement it. It makes the software more robust, and less dependent on the continued existence of a single core of developers. The software can be taken to other places by other developers, without compromising the quality or the support given to keep it updated.
The value of good forks can't be overstated, since they make software better and the ecosystem healthy. They can drive innovation, since they make developers working hard to make their particular branch of the fork relevant. Users benefit the most out of this, since they get to choose among several options that need to give something of value to them in order to keep them using their offering.
Developers also benefit, since they have a wider network to rely on in order to help them solve any problem the could face. Also, it means that if they have doubts about something the odds are that there is someone that can help them.
Forks should be encouraged, but keep in mind that support should go to the ones that are add value and are well made.
No comments:
Post a Comment