Re:Why your next project should be public domain
by pbnjay on Thursday July 11, 2013 @09:52AM
(#6025975)
If the code is never put into a public project I don't see how this would have any effect. I'm not required to abide by every license on everything I slap together on my laptop, it's when I distribute it or allow others (outside my organization) to use it that matters.
[ Parent
| on HN ]
Re:Why your next project should be public domain
by steveklabnik on Thursday July 11, 2013 @10:16AM
(#6026125)
It depends on what kind of license it is: if it's an end-user license, then yes, you do (in theory) have to abide by it.
You're right that if it's just a copyright on the source code, then it's probably a restriction on redistribution, which means you couldn't _use_ that code for evil and then share it with others. But using it for evil for yourself: totally fine.
Re:Why your next project should be public domain
by pbnjay on Thursday July 11, 2013 @10:37AM
(#6026256)
For an end-user license, sure. But even so the license restrictions only apply to the _recipients_. So if I'm the NSA and use GPL code, and only distribute it to NSA colleagues, I only have to provide my NSA colleagues with the license and code. (IANAL, but seems pretty clear to me on this)