3 ms·
I don't think that's helpful, because that's just not how licenses work. Please at least add that sentence to the repo then. Unless your definition of "hobbyis
by wink 4y ago
I don't think that's helpful, because that's just not how licenses work. Please at least add that sentence to the repo then.
Unless your definition of "hobbyist playing around with it" also includes "oh, I accidentally made something useful which uses your code, but now I have to rewrite it because I can't in turn use a useful license".
- rep_lodsb 4y agoIt's the ultimate "contagious" license, and it doesn't waste the petabytes of disk space that are by now certainly taken up by copies of GPL-version-whatever! To really make a point, one could include an empty file for the license (and code of conduct as well).
- wink 4y agoI'm a big fan of being overcommunicative in this regard. I'd hazard a guess that 9 out of 10 people with small code repos without a license have not bothered, or forgot, or didn't know and 1 or less out of 10 want to convey an active non-license (All rights reserved?) as the parent commenter, that's why I am in favor of spelling that out explicitly. Personal opinion of how useful toy code that you can look at but not use or even let you be inspired from is notwithstanding, but I'm not trying to argue here.
- rep_lodsb 4y agoAs long as there is no money involved, nobody will get sued for being inspired by - or even copying - that "toy code". That is what *non-commercial* software should be about.