<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)"><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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>The quotation from my 2005 Open Source Licensing book drew an update from Peter Deutsch. He asked that I update the history. Here it is:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoPlainText style='margin-left:.5in'>While your account was accurate for quite a few years, Artifex eventually abandoned the AFPL / GPL division, I believe because they found that it was a bit of complexity that didn't affect their revenue from commercial licensing. Instead, they simply offered the choice of either GPL or a straight commercial license. In addition, I believe they offered performance-enhancing replacements for certain modules that were only available to commercial licensees. (The ones I remember hearing about were things like halftoning or shading code that used processor-specific SIMD capabilities.) At the same time, they put quite a bit of energy into identifying and taking legal action against commercial users who were violating the GPL, of which there were an astoundingly large number. For the last several years this actually resulted in substantial revenue, from retroactive commercial license payments and from new commercial license agreements: some offenders started complying with the GPL, some obtained commercial licenses, and some stopped using the code altogether.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This email from Peter is a reminder that open source is an <u>evolving</u> ecosystem.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>/Larry<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>BCC: <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='mso-ligatures:none'>Lawrence Rosen<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;mso-ligatures:none'>707-478-8932<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;mso-ligatures:none'>3001 King Ranch Rd., Ukiah, CA 95482<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:8.0pt;mso-ligatures:none'><a href="mailto:lrosen@rosenlaw.com">lrosen@rosenlaw.com</a><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>