<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 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:black;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:12.0pt;color:black'>There is a lot of recent news about the SSPL license reactions by Red Hat and OSI and others. FWIW (despite the fact that I don't use MongoDB), I agree with their decisions to forego MongoDB software because of its overbroad "copyleft" and "corresponding source" SSPL license requirements. Requiring licensees to disclose the source code of much of their other networking software is a burden too painful.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'>But I also understand and appreciate the MongoDB business case dilemma. If they just give their software away without some copyleft conditions for free network use, they will not profit much from it.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'>SSPL and that MongoDB issue is not a unique situation. There is also a lot of AGPL license resistance by licensees for many of the same reasons of "overbroad copyleft" and its definition of "corresponding source". I asked Bruce Perens and John Cowen about it privately. They reminded me of the <i>Oracle v. Google</i> case, where various courts had various opinions about whether APIs (and thus the interactions among software components) could be "fair use" or could alternatively require copyleft and licensing. This was recently described on the OSI license-discuss@ email list as "Intimacy in open source," quoting the AGPL and the GPLv3 discussion drafts. </span><span style='font-size:12.0pt'>I'll suggest instead that all software (especially open source software!) is intended to be intimate with other software, and thus the word "intimate" is both overbroad and completely vague. So is the phrase "corresponding source."<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'>Bruce pointed out that we should consider instead the "intent" of the license authors, rather than focus on vague words like "intimacy." The FSF has written volumes about its GPL and AGPL copyleft requirements. We think we know their intent.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>I like his word "intent." It is an important word in law and with software licenses. But in civil litigation or criminal cases, "intent" can't be used vaguely, or the defendant won't be convicted. Licenses and laws should say exactly what they mean. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>So, if our community can come up with an adequate definition of "corresponding source" (or "intimacy") in the open source software context to enforce the <u>intent</u> of our network services copyleft licenses, I'm all ears. Neither SSPL nor AGPL currently meet that clarity requirement.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'>/Larry<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'>Lawrence Rosen<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;color:black'>Rosenlaw (</span><span style='color:black'><a href="http://www.rosenlaw.com/"><span style='font-size:8.0pt'>www.rosenlaw.com</span></a></span><span style='font-size:8.0pt;color:black'>) <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;color:black'>LinkedIn: LawrenceRosen<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;color:black'>3001 King Ranch Rd., Ukiah, CA 95482<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;color:black'>Cell: 707-478-8932 <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;color:black'>This email is licensed under </span><span style='color:black'><a href="https://creativecommons.org/licenses/by/4.0/"><span style='font-size:8.0pt'>CC-BY-4.0</span></a></span><span style='font-size:8.0pt;color:black'>. Please copy freely.</span><span style='font-size:12.0pt;color:black'> <img border=0 width=89 height=31 style='width:.9236in;height:.3263in' id="Picture_x0020_1" src="cid:image001.png@01D4AF33.4E97C870" alt="https://licensebuttons.net/l/by/4.0/88x31.png"></span><span style='font-size:8.0pt;color:black'><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>