3 ms·
It's perfectly ok not to be a community project, but you should be upfront about it. What I find strange is the hostility towards forking. I mean, why use the
by spacechild1 6y ago
It's perfectly ok not to be a community project, but you should be upfront about it.
What I find strange is the hostility towards forking. I mean, why use the GPL then? If you want to create a commercial app, but still share (some) code, you can do it this way: https://github.com/aseprite/aseprite#license https://github.com/aseprite/aseprite#license
- busterarm 6y agoBecause GPLv3 allows the license exemption that allows him to license VCV Rack to anyone trying to make and sell a commercial plugin. https://github.com/VCVRack/Rack/blob/v1/LICENSE.md https://github.com/VCVRack/Rack/blob/v1/LICENSE.md It's actually a fairly interesting business model.
- spacechild1 6y agoBut why use the GPL if you don't want people to fork? Just publish the source code under a custom EULA that does exactly what you want.
- busterarm 6y agoThe UI isn't under GPL and has a no-derivatives license. It's not so easy. Plus letting people use/make/distribute plugins for free probably keeps most people friendly to the project. Hence the one fork stopping work.