3 ms·
I often deliberately publish code with no license. It means any hobbyist can play around with it, but no company with a legal team will touch it. It appears a
by londons_explore 4y ago
I often deliberately publish code with no license.
It means any hobbyist can play around with it, but no company with a legal team will touch it.
It appears as an oversight rather than a deliberate decision to restrict who can do what.
And often that's exactly what I want.
- irdc 4y ago> It means any hobbyist can play around with it Not in legal terms it doesn't. In the absence of a licence, a copyrighted work may not be distributed in any way. So you could theoretically sue those hobbyists. Just bite the bullet and pick any of the common licenses. Sounds like you'd want one of CC-*-NC or perhaps AGPL.
- londons_explore 4y agoExcept no hobbyist seems to worry about such things. Occasionally I get messages asking me about the license, and I usually reply to them asking what they want to do/build and then I give them permission for whatever it is they want to make (for free).
- irdc 4y ago> Except no hobbyist seems to worry about such things. The hobbyists that you know or have contacted you don't seem to worry about these things. I can assure you this hobbyist takes licensing very seriously, and I'm not the only one. I may at some point want to distribute my work, and having a dependency without a license makes that pretty much impossible.
- pseudalopex 4y agoThe 2nd sentence sounds like hobbyists worrying about such things.
- wink 4y agoI 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.