3 ms·
I'm an advocate for OSS in many circumstances, but you have to understand that one of the consequences of open-sourcing your software is that things like this c
by lylejohnson 15y ago
I'm an advocate for OSS in many circumstances, but you have to understand that one of the consequences of open-sourcing your software is that things like this can happen.
I can't tell if the blog's author is upset so much about the fork as he is the idea that someone other than Jigowatt is making money off of this plugin. The whole Git and GitHub ethos has certainly removed a lot of the stigma once associated with forking.
- freddealmeida 15y agoI agree. I certainly don't see anything wrong with forking a project if the licence allows it. Of course, I never understood why there was a stigma attached to forking in the first place. This article is a bit unnecessary.
- badgergravling 15y agoThere's nothing wrong with forking, and it's clearly allowed under the GPL licence, and is legal and above board. But there are good reasons for forking - for instance, if the code has languished for ages, and there are forks which split the potential development and user community. There's always two sides to every story, and I'm involved with Jigoshop, but certainly Jigoshop/Jigowatt supported a team of developers to work on a project which resulted in two of the team leaving just as the stable version was about to be released, there was a low offer of acquisition of copyright of the product, and an offer of collaboration which had certain conditions attached to it, so would not have been workable, and forking is being used as a business mechanism, rather than a method of evolving the software