<html><head><style type="text/css">body {word-wrap: break-word; background-color:#ffffff;}</style></head><body><div style="font-family: sans-serif; font-size: 16px">I'm not sure what ccan's overall goal is but according to cpan<br><br><a href="http://www.cpan.org/misc/cpan-faq.html#How_is_Perl_licensed">http://www.cpan.org/misc/cpan-faq.html#How_is_Perl_licensed</a><br><br>Most of the modules on cpan are licensed gnu gpl or perl artistic. Maybe ccan might want to consider a suggestion to contributers to keep, if at all possible, licenses to a few common ones (and list those common licenses).<br><br>There really are only a handful of different licensing goals. And multiple nuances, while sometimes deathly important to the developer, ends up creating headaches for.all the downstream users because of incompatibilities.<br><br><br><br>Greg<br><br><br><br><br><br><br><br></div>-----Original message-----<br><blockquote style="; border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div style="font-family: sans-serif; font-size: 14px"><b>From: </b>Tim Post <echo@echoreply.us><b><br>To: </b>Rusty Russell <rusty@rustcorp.com.au><b><br>Cc: </b>ccan@lists.ozlabs.org<b><br>Sent: </b>Wed, Oct 20, 2010 16:29:19 GMT+00:00<b><br>Subject: </b>Re: [ccan] ISC license?<br><br></div>On Wed, 2010-10-20 at 15:25 +1030, Rusty Russell wrote:<br>> Hi Joey,<br>> <br>> Finally glanced at your AVL code; noted the ISC license. I'm not<br>> particularly fussed, but I found this note:<br><br>Where I work, that license is described (more or less as) "Avoid unless<br>it would take months to implement the code in question otherwise, get<br>approval before using it".<br><br>This is for the same reason that is cited by the folks at GNU. We also<br>avoid other licenses that have similar wording, but these are mostly<br>written by people who (for whatever reason) aren't happy with existing<br>licenses and decide to write their own.<br><br>Rusty, it might actually be worth listing the licenses in the same table<br>that lists the modules, at least pending some anticipated love to the<br>ccan web site.<br><br>For instance, I might be working on something that is GPL2 only, which<br>means GPL2+ or LGPL2+ is just fine for me. However, we have some stuff<br>that is GPL3, for instance. <br><br>I know the licenses are listed on each individual module page, but<br>imagine 500 modules. It really helps to click stuff that looks<br>interesting when you know you can actually use it :)<br><br>Cheers!<br>--Tim<br><br><br><br>_______________________________________________<br>ccan mailing list<br>ccan@lists.ozlabs.org<br><a href="https://lists.ozlabs.org/listinfo/ccan">https://lists.ozlabs.org/listinfo/ccan</a><br></blockquote></body></html>