<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Could the lgpl not be chosen instead? Would this not allow the tests to be distributed along as they don't ship a custom version of propEr as somebody else states?<div>Also is it really the case that the tests could not be distributed, or more a case that it is totally fine to distribute the tests along as the person receiving the tests downloads proper themselves? the code that is not tests would still run fine.<div><br></div><div>Also what was the original reasoning behind choosing the gpl in this case? </div><div><br></div><div>Regards</div><div><br></div><div>James<br><div><br></div><div><br></div><div>also +1 to try to convince Kostis to release PropEr with a better license!</div><div><br><div><div>On 14 Jun 2011, at 13:33, Eric Merritt wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p>I talked with Kostis about this at the erlang factory. He said he is going to provide the exception to the gpl for open source projects. I think he just has not had time to do the actual work.</p>
<div class="gmail_quote">On Jun 14, 2011 7:26 AM, "Richard Carlsson" <<a href="mailto:carlsson.richard@gmail.com">carlsson.richard@gmail.com</a>> wrote:<br type="attribution">> On 06/14/2011 02:02 PM, Ulf Wiger wrote:<br>
>> On 14 Jun 2011, at 01:09, Vik Olliver wrote:<br>>>> On 14/06/11 11:01, Francis Joanis wrote:<br>>>>> I have a question about the GPL licensing of the tool itself:<br>>>>> since it is GPL, doesn't it require to make the written tests<br>
>>>> themselves and to some extent the application under test GPL as<br>>>>> well?<br>>>><br>>>> Only if you distribute the tests. If you keep them to yourself,<br>>>> you don't owe anyone anything. The GPL respects privacy.<br>
>><br>>> This could become an obstacle to adoption similar to what's been seen<br>>> with Quviq QuickCheck: people who have Open Source projects need to<br>>> publish (=distribute) test suites as well. Just as it's not very<br>
>> helpful to distribute test suites that require an expensive tool,<br>>> people might be reluctant to publish PropEr-based tests if it<br>>> requires them to convert to GPL.<br>>><br>>> Kostis did say that they would make an exception for OSS projects. I<br>
>> could not find any such exception when quickly scanning the repos.<br>>><br>>> BR, Ulf W<br>> <br>> As I have remarked before on this list, I believe the normal GPL (all <br>> versions) cannot be used for Erlang modules, because the dynamic loading <br>
> and linking of classes/modules at runtime is not considered to be any <br>> different from static linking - at least according to the FSF.<br>> <br>> The standard Erlang library modules and the runtime system BIFs are <br>
> published under the Erlang Public License, which is an even more <br>> restrictive variant of MPL. The MPL is not compatible with GPL <br>> (<a href="http://en.wikipedia.org/wiki/Mozilla_Public_License#Compatibility_with_GPL">http://en.wikipedia.org/wiki/Mozilla_Public_License#Compatibility_with_GPL</a>), <br>
> due to some of its restrictions, so it should follow that the EPL is <br>> also not compatible.<br>> <br>> If you want to enforce copyleft in your code, but not force it on other <br>> libraries that link with your code, you can use LGPL instead of GPL. <br>
> (Preferably, use v3, which is compatible with Apache License 2.)<br>> <br>> <a href="http://www.gnu.org/licenses/lgpl-java.html">http://www.gnu.org/licenses/lgpl-java.html</a><br>> <br>> /Richard (not a lawyer)<br>
> _______________________________________________<br>> erlang-questions mailing list<br>> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>> <a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</div>
_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>http://erlang.org/mailman/listinfo/erlang-questions<br></blockquote></div><br></div></div></div></body></html>