On Saturday, April 20, 2013 4:50:35 PM UTC-4, Phil Hagelberg wrote:
>
>
> I recommend the EPL; it's what you get when you
> run `lein new myproject`, and I feel like Rich made a pragmatic choice
> with a license that is copyleft without being virally so.
>
My understanding is that "copyleft" roughly means, "any changes you make to
the program (and then subsequently distribute) must be licensed under the
same terms as the original program".
The EPL only appears to be copyleft if the contributor *chooses* to
distribute the source code along with the object code. They can just as
well choose to distribute object code only.
(If you want to guarantee that your source code --- plus future
(distributed) modifications by others --- remains free, the LGPL would be a
good choice.)
> If there is some reason you want to avoid copyleft, (corporate paranoia,
> etc.) then the Apache license seems like the best bet among non-copyleft
> ones, {snip}
>
Agreed.
--
--
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.
