cbpporter Messages: 1401 Registered: September 2007
Ultimate Contributor
mr_ped wrote on Thu, 06 July 2017 04:22
GPL requires you to publish modified sources. But only to your customers, doesn't mean you must provide them as free download on Internet for everyone.. but the very first customer who will download it may freely post it on Internet, if he wish so, so count GPL as "must publish src".
I didn't know that bit that you were not required to publish it yourself. Thanks!
Otherwise this is high level stuff I found on my own. I'm having problems googling the detail stuff.
The bit where a package is its own license and not the sum license of its dependencies was one such detail.
Another is if you need to register as a copyright owner. I'm about to release a new hand written C++ bit of code on GitHub next week. I can choose its license, but how do I determine the copyright. Do I put just 2017 because it is 2017? Who do I put as the copyright owner? Does the year count? When does it expire? Are some years netter than others or is it not important.
I also want to upload some generated C++ code. The input is not C++, the output is C++. Is the output the same license as the input? Does the license of the generator impact the license of the output?
That perhaps because nobody really cares that much. The lore is "GPL is bad for bussiness, rest is OK". (Note that "bad for bussiness" does not need to imply a negative thing in all cases). IMO thats all that is to be known.