2013/4/20 Phil Hagelberg <p...@hagelb.org>

> Anyway, everything else about the post appears solid except for one
> thing. It recommends the MIT license, which has no patent protection
> whatsoever; this could open you and your users up to liabilities in ways
> that are impossible to predict given that the United States Patent
> Office's tendency to grant patents without examining them first. So I
> strongly caution against using licenses which don't include patent grant
> clauses unless it's for throw-away code. While the Apache license can be
> annoying in all the boilerplate it requires, at least it doesn't have
> this problem.
>

Ii wasn't immediately clear to me, but it makes sense, given how short
the MIT license is.

What licenses does it make sense to recommend?

I'll update the post because, indeed, we [maintainers] can't ignore patent
protection.
-- 
MK

http://github.com/michaelklishin
http://twitter.com/michaelklishin

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to