5 ms·
This is obviously much better than proprietary as people can potentially benefit in the future from your work and I thank you for being so kind as to share it a
by michaelmrose 10y ago
This is obviously much better than proprietary as people can potentially benefit in the future from your work and I thank you for being so kind as to share it and yet I would probably use something significantly crappier to have real open source and several other things seem problematic.
-- Others are unlikely to contribute to the proprietary fork.
-- What do you do about contributions to the gpl3 version they would be copyright their creators and couldn't be part of a closed source version even the authors without copyright assignment.
-- Do you backport fixes to the gpl version. It would be far simpler to say use the new version wherein issue foo is fixed. If you do its a lot more work if you don't the gpl version isn't just a older version its a known broken pos that will never be fixed.
-- What if people offer fixes to the gpl version will they be expected to assign copyright so you can use them in the proprietary version?
-- 3 years is an eternity. In 1 year someone could make their own version of whatever it is you are doing that is actually open source if it was really worth having it would also have none of the above complications.
- chubot 10y agoYeah I agree... I like this idea in theory. But in practice I think you will end up with two major versions: "latest commercial version" and "latest GPL version". And then people will want to patch the GPL version and not the latest. 3 years is a lot of delta... git is really good at applying patches, but I wouldn't want disincentivize massive refactorings.
- rocqua 10y agoThese concerns are why I tend to dislike the GPL.
- wcoenen 10y agoI don't see anything GPL-specific about these concerns. The same concerns apply when you replace the GPL by any other non-proprietary license.
- k_sze 10y agoIf I understand correctly, I think it is somewhat GPL-specific. You basically can't port fixes and new features from a GPL codebase to another codebase that is not under a GPL-compatible license. I think you don't have this issue with more permissive licenses like MIT/BSD. At least then you have a chance of having the commercial-licensed one having all the fixes from the open-source version, in addition to its own fixes and new features. (My understanding of open source/free software licenses can be quite fuzzy, so correct me if I'm wrong.)
- martingxx 10y agoYou can't port fixes and new features unless you have a license to do so. That's true in all cases. If you only license you have is GPL, it doesn't allow you to use those in a non-Free way, which I think is the point you are making, and I agree that's how it works. But that's a feature of GPL, not a bug. If you are a company producing code and trying to make a living from it, it's risky to release code as BSD/MIT unless you can afford to have someone clone it, close it and sell an improved version, passing it off as their own without giving you anything (like Microsoft did with the BSD TCP stack, and with NCSA mosaic for example). If you release as GPL however, that can't happen. It's much safer in that regard, and more socially considerate too, which is why it's the license of choice for most Linux distro vendors and other major open source vendors such as MySQL.
- k_sze 10y agoYes, I do understand that people can take the BSD/MIT codebase and make a proprietary/closed source version. In that case you don't even see how the bug fixes are implemented in the new closed source version. So you are free to independently come up with the most obvious, efficient fix. My point is that with GPL, the implementation of the fixes/new features is right in front of you, you see it, yet you can't merge it into your GPL-incompatible codebase. Let's say we are talking about a security fix that turns out to be really easy. Somebody patched it in the GPL version, the fix turns out to be dead-easy and obvious, but now you can't use the same dead-easy and obvious fix in your own non-GPL version because it would be a violation of GPL. So now you have to come up with a suboptimal, ugly fix. In this case, GPL makes it painful for the original author of the proprietary version.
- michaelmrose 10y agoThe gpl is pretty much designed to maximize the freedom of the user by creating an environment where its impossible for to fork the work and keep it to yourself. Its even hard for the creator as he could end up competing with his work so far + the community. This might mean it is not in useful to you but it doesn't make it bad. In other news your motor home is probably not the best option to commute to work and living in your car isn't the best experience.
- belorn 10y ago> What do you do about contributions to the gpl3 version Lets define contributions. The author of the project can request that contributions to their official branches are done with additional permission for the proprietary version. If people don't accept, they have to fork the whole project. We also have contributions to unofficial patches inside distribution repositories. Debian patches would for example not be able to be directly patched into the proprietary fork without additional permissions.
- boyter 10y agoTo be honest I am not looking for collaboration at this point. The orginal reason for posting the source is because this indexes your source code and many raised concerns that it could potentially be phoning home with your code. Being able to see the code and build the binary distribution to hash check solves that issue. The reason for the time delay is because I want to look after anyone who does use his in the event of my death or otherwise. It means you are unlikely to be stranded in the future. I do want to move closer and closer to a full GPL model, however I also want to be paid. If the full version is GPL then what is a strategy to achieve this? I could feature gate but this is also hated by many as seen by the nginx model. If someone can come up with a better model then "sell support" and have a clean soul I will be all over it. Till then this works in a way that's adventagous for myself without being too restrictive in the future for others.
- blackorzar 10y agoDefine that all the external contributions must be dual licenced Apache Public License v2 and GPL, that way you can integrate it to your lead version (commercial licence) because APL2 allows it, and also you can release it after 3 years in the GPL branch (or rebase it to the current GPL edition right away). This way you don't need the contributors to sign anything and aligns well with your model.