3 ms·
It's both, honestly. (1) I can't incorporate Hibiki into anything (A)GPL licensed, which many of my projects are. (2) Ideologically I can't get behind somethi
by notRobot 5y ago
It's both, honestly.
(1) I can't incorporate Hibiki into anything (A)GPL licensed, which many of my projects are.
(2) Ideologically I can't get behind something non-free, even though I completely understand why you wrote the license the way that you did. Realistically all it's going to do is hinder adoption (see parent comment of mine).
(3) You can say I'm not going to get into trouble, but your license says otherwise, and I really can't use something unless I'm 100% sure I'll be in the okay, ya'know?
- sawka 5y agoFair enough. I realize the AGPL integration is a deal breaker. For point 3, true, which is why I could offer a proprietary license that does say you'd be 100% okay (although it still wouldn't work for point 1).
- notRobot 5y agoThe problem is -- everything that I write is FOSS! So I can neither use your current license, nor a proprietary license I purchase from you! I am happy to pay for a FOSS license, but obviously that will then allow other people to use the code without paying for it, because of the nature of FOSS.
- learc83 5y agoDon’t try to please everyone. If someone is a FOSS purist, they aren’t going to accept a license with any of the restrictions that prevent companies from offering a hosted service.