Post #2606060

@zkat The major problem with 'noncommercial licenses' ist that it is easy to tthrow the baby out with the bathwater. To construct an example: Imagine there is a mail client with such a non-commercial 'Community Software' license. Can I receive an email with it conceerning my (commercial) sticker business? Can I write a newsletter for said business with it? Can I change the code to make Newsletter usage easier? Can I write a plugin for said software, and ask for donations for a licensee for that plugin? What if the donation is quasi-mandatory? What if I change the software itself, for a very particular use-case, for one very particular user, and get paid for that, either as a consultant, or an employee? What if I slap a new logo on it and sell it as 'my own'? Clearly there is a line in there somewhere. If a 'Community license' should ever take of, that line needs to be defined, otherwise there is absolute chaos. The beauty of OSS is: There is a very clear, very simple line: Distribute your own source code with the compiled program. That's unambiguous.