<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=utf-8"><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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;
color:black;}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.plaintextchar0
{mso-style-name:plaintextchar;}
span.emailstyle19
{mso-style-name:emailstyle19;}
span.EmailStyle22
{mso-style-type:personal;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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="#000000" vlink="#000000"><div class=WordSection1><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>David Webber wrote:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-family:"Calibri",sans-serif'>> </span><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>What I see happening here is a "lawyer perspective" on how software gets written and delivered compared to an actual developers perspective and how the software is really being packaged.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri",sans-serif'>Don't worry. In this case, the lawyer and the developer completely agree with each other. :-)<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri",sans-serif'>/Larry<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> David RR Webber (XML) [mailto:david@drrw.info] <br><b>Sent:</b> Tuesday, September 8, 2015 9:53 AM<br><b>To:</b> CAVO <cavo@opensource.org><br><b>Subject:</b> Re: [CAVO] [License-review] Submission of OSET Public License for Approval<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>Larry,<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>What I see happening here is a "lawyer perspective" on how software gets written and delivered compared to an actual developers perspective and how the software is really being packaged.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> A main justification for having this alteration of MPL 2.0 seems to be <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> that the GPL license family would be inappropriate because it would <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> cause problems, possibly even contractually insurmountable ones, in <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> procurement. So my point is that this seems to assume that the <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> products being offered for procurement contain no GPL-licensed code, <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> and perhaps only contain OSET-PL plus code under noncopyleft licenses.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>Typically the software developer is NOT tampering with the layers of source code around at all - in fact they are striving to use those AS IS - and NOT embedding any of the source code in their solution. Quite the reverse - they are only interested in using compiled libraries and API calls to avoid making their life more complex. If there are bugs or changes/enhancements desired - these will be referred back to the managing project for resolution. Similarly standalone services - such as Apache server - will be used out-the-box and configured using the control files, user management accounts, profiles and parameters that are available for that purpose.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>When it comes to delivery there are then three choices:<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>a) Providing detailed install instructions to manually locate each component from the original project site, download, install, and configure.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>b) Provide a package that performs a) for the user with assistive menus and hand-holding - selecting the specific components and installing them<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>c) Pre-built package and installer - developer obtains all the necessary downloads - creates an install package - fully automates b) for the user.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>What this means is in terms of license compatibility is that the great majority of the solution stack as simply used as is - and therefore the individual license terms apply - and no conflicts can occur.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>Where a developer is actually using software components IN THEIR OWN CODE then they need to ensure that those parts are licensed appropriately. However - I do not see that this provides ANY CONFLICTS for election officials or parties. They are essentially using each component part according to the individual licensing terms - and not attempting to modify the underlying code in any way.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>David<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><o:p> </o:p></span></p></div><blockquote style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 6.0pt;margin-left:6.0pt;margin-top:5.0pt;margin-bottom:5.0pt' id=replyBlockquote><div id=wmQuoteWrapper><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>-------- Original Message --------<br>Subject: Re: [CAVO] [License-review] Submission of OSET Public License<br>for Approval<br>From: "Lawrence Rosen" <<a href="mailto:lrosen@rosenlaw.com"><span style='color:windowtext'>lrosen@rosenlaw.com</span></a>><br>Date: Tue, September 08, 2015 12:28 pm<br>To: "'CAVO'" <<a href="mailto:cavo@opensource.org"><span style='color:windowtext'>cavo@opensource.org</span></a>><br>Cc: Lawrence Rosen <<a href="mailto:lrosen@rosenlaw.com"><span style='color:windowtext'>lrosen@rosenlaw.com</span></a>><o:p></o:p></span></p><div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>Heather Meeker wrote:<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> I do think this is a license compatibility point, in a way. <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> Permissive licenses for third-party components would allow <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> the code as a whole to be licensed under the terms of OSET. <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> But a copyleft license would not. <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>We are not just speaking of "components" but of a "solution stack" for elections. It <u>will</u> include GPL and MPL components. Inevitably. <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>All existing FOSS licenses (permissive and copyleft) are already compatible for aggregates such as comprehensive election systems. (See OSD #1.) The government agencies that acquire such systems are already faced with all those FOSS licenses. Good for FOSS!<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>This does not affect whether the OSET-PL should be approved by OSI. Lots of licenses already are. We are mostly focusing on the justification(s) you are asserting for it.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>/Larry<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>-----Original Message-----<br>From: Meeker, Heather J. [<a href="mailto:hmeeker@omm.com"><u><span style='color:blue'>mailto:hmeeker@omm.com</span></u></a>] <br>Sent: Tuesday, September 8, 2015 8:51 AM<br>To: License submissions for OSI review <<a href="mailto:license-review@opensource.org"><u><span style='color:blue'>license-review@opensource.org</span></u></a>><br>Subject: Re: [License-review] Submission of OSET Public License for Approval<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>Thanks. I do think this is a license compatibility point, in a way. Permissive licenses for third-party components would allow the code as a whole to be licensed under the terms of OSET. But a copyleft license would not. However, incompatibility with other copyleft licenses is not a problem we can solve own our own. We have tried to do as much as we can to solve it on the outbound side with our license compatibility terms. But on the inbound side, it's up to the third-party copyright owner.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>Assuming that such incompatibility does create an issue, then this question dovetails back to the question of whether we can be successful with the license. In other words, if I can rephrase your question a bit, is it possible to build a complete enough voting system without using code under incompatible licenses? It's a good point you raise. But as I have commented before, our likelihood of success is not the criterion for license approval.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>Sent from my tablet --Heather Meeker<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> On Sep 8, 2015, at 8:34 AM, Richard Fontana <<a href="mailto:fontana@sharpeleven.org" target="_blank">fontana@sharpeleven.org</a>> wrote:<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> My comment wasn't about license compatibility. Rather:<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> Clearly OSET favored some kind of copyleft license, and you've made a <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> few comments about the GPL that seem to imply (possibly reinforced by <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> the comments of the CAVO folks, unless this was in response to those<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> comments) that in this open source voting systems space there is a <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> background community preference for the GPL, maybe even specifically <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> GPLv3.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> A main justification for having this alteration of MPL 2.0 seems to be <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> that the GPL license family would be inappropriate because it would <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> cause problems, possibly even contractually insurmountable ones, in <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> procurement. So my point is that this seems to assume that the <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> products being offered for procurement contain no GPL-licensed code, <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> and perhaps only contain OSET-PL plus code under noncopyleft licenses.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> If they do contain GPL-licensed code -- for example, let's say a <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> software stack that includes the Linux kernel -- you've eliminated any <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> benefit you otherwise might have gotten from the novel features of <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> this license. (Similarly, if your stack includes any MPL 2.0 code, you <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> are stuck with the limitations of MPL 2.0 relative to the changed <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> features in OSET-PL.) One or more of the people from CAVO seemed to be <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> making a similar point.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> Thanks for the clarification about why MPL 2.0's 'Executable Forms'<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> provision is not sufficient for OSET's needs.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> Richard<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> On Mon, Sep 07, 2015 at 05:34:06PM +0000, Meeker, Heather J. wrote:<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> Re: Aren't you assuming that such an open source technology system <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> will not contain any GPL-licensed software....<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> No, we are not at the point of making such assumptions. We don't expect to limit this license to only one software package, so there are many possible configurations of software and attendant licenses. If this is a licensing compatibility concern, the OSET license is no less compatible with other licenses that most copyleft licenses already approved, and more so than some approved licenses. If this is a question of whether election procurement managers are likely to accept our license, then that is a different question. (Please see my prior post on this point.) <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> Re: One other question: MPL 2.0 allows using different terms for <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> 'Executable .....<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> So does OSET (we use the same provision as MPL2 2.0), but we are assuming that provisioning election systems will include delivery of source code -- or at least, that we need to allow for that possibility. <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> -----Original Message-----<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> From: License-review [<a href="mailto:license-review-bounces@opensource.org" target="_blank">mailto:license-review-bounces@opensource.org</a>] <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> On Behalf Of Richard Fontana<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> Sent: Sunday, September 06, 2015 11:03 AM<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> To: License submissions for OSI review<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> Subject: Re: [License-review] Submission of OSET Public License for <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> Approval<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> On Tue, Sep 01, 2015 at 10:18:59PM +0000, Meeker, Heather J. wrote:<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> Our stakeholder community—elections administrators and officials—are <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> very receptive to acquiring open source software-based election and <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> voting systems provided the software (and related support and <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> services) can be legally acquired through their procurement process. <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> A primary ingredient of their procurement process is terms and <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> conditions of software licensing that meet their regulatory requirements.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> While governments already often acquire open source technology on an <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> ad hoc basis under existing licenses, they face more, and different, <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> hurdles acquiring open source election systems. Open source <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> software that is merely part of a larger IT system is usually <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> covered by two documents—the open source license, and an overarching <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> (and often superseding) procurement agreement that fits with the <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> applicable regulations. Where an agency is acquiring an entire open <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> source technology system—especially technology to be used in public <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>>> elections and subject to competitive bidding—procurement regulations need to be handled properly within the four corners of the open source license.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> I'm trying to understand this particular point. Aren't you assuming <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> that such an open source technology system will not contain any <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> GPL-licensed software, perhaps not any copyleft software (perhaps not <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> any software under any other open source license -- in other words <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> are you assuming that the 'technology system' will consist solely of <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> software under the OSET-PL)? Because otherwise you have a <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> mixed-license product where only some portion of the product is <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> licensed in such a way as to meet your goals.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> One other question: MPL 2.0 allows using different terms for <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> 'Executable Forms', so presumably you could meet your objectives here <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> by way of an appopriate non-open-source license for the Excecutable <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> Form. Why is MPL 2.0 not suitable - is it because you expect to be <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> distributing 'Source Code' (as defined in OSET-PL/MPL 2.0) in a <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> procurement context, or is it because of some desire to be able to <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> claim that the license used in the procurement context is open source?<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> Richard<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> _______________________________________________<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> License-review mailing list<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> <a href="mailto:License-review@opensource.org" target="_blank">License-review@opensource.org</a><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> <a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review</a><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> _______________________________________________<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> License-review mailing list<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> <a href="mailto:License-review@opensource.org" target="_blank">License-review@opensource.org</a><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>>> <a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review</a><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> _______________________________________________<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> License-review mailing list<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> <a href="mailto:License-review@opensource.org" target="_blank">License-review@opensource.org</a><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>> <a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review</a><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>_______________________________________________<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>License-review mailing list<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><a href="mailto:License-review@opensource.org" target="_blank">License-review@opensource.org</a><o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review</a><o:p></o:p></span></p></div></div><div class=MsoNormal align=center style='margin-left:.5in;text-align:center'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'><hr size=3 width="100%" align=center></span></div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>_______________________________________________<br>CAVO mailing list<br><a href="mailto:CAVO@opensource.org"><u><span style='color:blue'>CAVO@opensource.org</span></u></a><br><a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/cavo"><u><span style='color:blue'>https://lists.opensource.org/cgi-bin/mailman/listinfo/cavo</span></u></a><o:p></o:p></span></p></div></blockquote></div></body></html>