<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.gmailquote
{mso-style-name:gmail_quote;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Matthew, <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Have you considered the <a
href="http://www.eclipse.org/org/documents/epl-v10.php">Eclipse Public License</a>?
It meets the set of constraints you have set out, including widespread
commercial adoption.</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Daniel Corbe
[mailto:daniel.junkmail@gmail.com] <br>
<b>Sent:</b> Thursday, September 27, 2007 11:08 AM<br>
<b>To:</b> Matthew Flaschen<br>
<b>Cc:</b> License Discuss<br>
<b>Subject:</b> Re: OSI Approval process<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Ultimately we were advised by legal counsel NOT to use the
LGPL due to the extended use of the term "Library" throughout the
license agreement and how that can potentially be misconstrued in court due to
the fact that the software in question is actually not a library but rather a
full blown application. <o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I personally think this fear is unfounded; however, my
lawyers aren't technical people and I don't have a law degree so I'm going to
accept the advice at face value. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>-Daniel<o:p></o:p></p>
<div>
<p class=MsoNormal><span class=gmailquote>On 9/19/07, <b>Matthew Flaschen</b>
<<a href="mailto:matthew.flaschen@gatech.edu">matthew.flaschen@gatech.edu </a>>
wrote:</span><o:p></o:p></p>
<p class=MsoNormal>Daniel Corbe wrote:<br>
> Once I have a usable systems framework I'll want to concentrate on writing
<br>
> applications which can make use of this work. For this I will
want to be a<br>
> lot less permissive about sub-licensing code. Mainly because it
will be in<br>
> a user-facing context as opposed to a developer-facing context. <br>
><br>
> I want the code to remain open,<br>
<br>
Exactly what do you mean by "open" here?<br>
<br>
> and I want the intent of the license to<br>
> reflect free and unrestricted distribution of my code (which includes <br>
> incorporation into commercial offerings). This rules out the
GPL as it<br>
> violates the spirit of my intentions.<br>
<br>
Of course, GPL allows interpretation into commercial offerings. It<br>
doesn't allow incorporation into proprietary offerings. Which do you
mean? <br>
<br>
> I want something<br>
><br>
> A) Less permissive than the MIT/BSD license<br>
> B) Something that is certainly a great deal clearer than the BSD license<br>
> C) Something more permissive than the GPL. <br>
<br>
Have you considered the LGPL? It will allow you to keep the
"library"<br>
code open, but the overall work using the library can still be proprietary.<br>
<br>
Matt Flaschen<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>