<div dir="ltr">Karl, Richard, anyone else: any thoughts on this?</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Nov 11, 2013 at 1:59 PM, Luis Villa <span dir="ltr"><<a href="mailto:luis@lu.is" target="_blank">luis@lu.is</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">That seems like a reasonable addition to me, and addresses real, recent confusion.</p>
<p dir="ltr">Karl and Richard are on planes today, and I would like to hear their thoughts before taking it live, though. </p>
<p dir="ltr">Thanks, Engel! <br><span class="HOEnZb"><font color="#888888">
Luis</font></span></p><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On Nov 10, 2013 10:38 AM, "Engel Nyst" <<a href="mailto:engel.nyst@gmail.com" target="_blank">engel.nyst@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello license-discuss,<br>
<br>
I would propose an additional paragraph to the FAQ, for the question<br>
What is "free software" and is it the same as "open source"?<br>
<br>
The text currently says:<br>
> One of the tactical concerns most often cited by adopters of the term<br>
> "open source" was the ambiguity of the English word "free", which can<br>
> refer either to freedom or to mere monetary price; this ambiguity was<br>
> also given by the OSI founders as a reason to prefer the new term<br>
> (see "What Does `free' Mean, Anyway?", and similar language on the<br>
> marketing for hackers page, both from the original 1998 web site).<br>
<br>
At this point in the text, I'd suggest to insert a little explanation on the ambiguity in the use of the term of open source as well. Quick draft...<br>
<br>
> On the other hand, the term "open" applied to the source is sometimes<br>
> used in the sense of merely "provided" or "visible", but the open<br>
> source definition sets the criteria for "open source" to software<br>
> licenses that guarantee a set of perpetual and irrevocable<br>
> rights to every recipient.<br>
<br>
The text should then probably skip "furthermore", and continue...<br>
<br>
> The FSF uses a shorter, four-point definition of software freedom<br>
> when evaluating licenses, while the OSI uses a longer, ten-point<br>
> definition. The two definitions lead to the same result in practice,<br>
> but use superficially different language to get there.<br>
<br>
I hope it will help with a number of misunderstandings.<br>
______________________________<u></u>_________________<br>
License-discuss mailing list<br>
<a href="mailto:License-discuss@opensource.org" target="_blank">License-discuss@opensource.org</a><br>
<a href="http://projects.opensource.org/cgi-bin/mailman/listinfo/license-discuss" target="_blank">http://projects.opensource.<u></u>org/cgi-bin/mailman/listinfo/<u></u>license-discuss</a><br>
</blockquote></div>
</div></div></blockquote></div><br></div>