On 2 Apr 2014, at 13:30, Tavian Barnes wrote:
One question - could you consider also licensing it under Apache 2.0
or
something else the OSI has approved as an open-source license? WTFPL
basically means we could never use it in Google, nor could Googlers
contribute back to it, owing to its lack of warranty disclaimer and
very
vague rights grant.
I'm surprised that you wouldn't be able to use it internally (it's
basically public domain), but good point about your own contributions.
I'll re-license to Apache to keep things simple.
It comes down to this (remembering that IANAL). WTFPL and other
near-public-domain licenses simply are too vague and weak to be secure
bases to defend against a later intellectual property claim. It's like
saying "yeah, use it, whatever" and then the vagueness leaves open
future lawsuits of "well, I didn't mean they could use it in this
specific context." So it becomes an Admiral-Akbar-style trap, legally
speaking, and companies are at-risk if they then use the code. Which is
why the OSI rejected it as an open-source license.
<shrug>
Thanks for being open to alternatives, though. Mighty awesome of you.
Christian.
--
You received this message because you are subscribed to the Google Groups
"google-guice" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-guice.
For more options, visit https://groups.google.com/d/optout.
