2 ms·
I'd formulate it like so. * Use BSD/MIT for a utility. You want the utility to be universally available, and included into larger systems to make them more use
by nine_k 4y ago
I'd formulate it like so.
* Use BSD/MIT for a utility. You want the utility to be universally available, and included into larger systems to make them more useful and compatible to each other. A compression library, a file format, a single-purpose program like sshd would benefit from a permissive license.
* Use GPL for a platform. If your stuff allows to build things based on it, if it is intended to serve as a backbone and a foundation, protect if from being grabbed by proprietary hands. Instead, make it safe for participants large and small (but especially large) to contribute to it openly without fear that somebody else would grab their contribution and turn it into a proprietary fork. Something like an OS kernel, or a desktop environment, or an application / database / etc server, or a compiler, may benefit from being released under GPL.
I don't have a strong opinion about programming languages: as long as the toolchain is open-source under whatever license, it usually thrives on its own merits, not due to licenses prodding its use one way or another. The language specification of course needs to be open for re-implementation, and the standard library should be licensed so that it could be included in closed-source projects.
Dual licensing (copyleft + paid commercial) is also a reasonable option.
- kitsunesoba 4y agoWhere would you say a UI framework (e.g. AppKit, Qt, etc) falls under this? Seems to straddling between utility and platform, and while I can see the benefit in keeping proprietary forks at bay one would probably want to enable the widest possible usage.