<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>Brent,</div><div><br></div><div>I share the concern of "what is really going on?" here - the stated needs are not exactly linked to clear business drivers and requirements and scenarios - there's a lot of legal contingency and "what iffing" covering here and maybes. <br></div><div><br></div><div>However - this is one interesting area:</div><div><br>Section 5.3 of the 2.0 license now requires that a licensee who does<br>not abide by the terms of the license must make the Covered Software<br>available in Source Code Form on a publicly available computer net<br>work for a period of no less than three (3) years<br></div><div></div><div><br></div><div>This is certainly an area that GPL3 has not specifically covered in detail - its assumed that the code is made available - but this has often been an issue - particularly in regard to the latest code - rather than some prior code set. And then also - the code can be made available - but use and verification of it can be made opaque by omission of components or instructions that are needed to actually replicate deployed build packages.</div><div><br></div><div>There are definitely issues with government contracts - but whether those are actually needed to be covered in the license is not clear. Certainly the government general assumes they "own" whatever is provided or touched during fufillment of a project - unless otherwise clearly noted.<br></div><div><br></div><div>David</div><div><br></div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [CAVO] Fwd: [License-review] Submission of OSET Public<br>
License for Approval<br>
From: Brent Turner <<a href="mailto:turnerbrentm@gmail.com">turnerbrentm@gmail.com</a>><br>
Date: Wed, September 02, 2015 3:47 am<br>
To: CAVO <<a href="mailto:cavo@opensource.org">cavo@opensource.org</a>><br>
<br>
<div dir="ltr">I'll punt this one to the big brains...but Meeker sounds like she is justifying a solution to a non-existent problem.. i.e . why would a new license be needed other than GPL. ? When asked previous who in government craved a special OSET created license.. the silence was notable. <div><br></div><div>BT</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 1, 2015 at 9:33 PM, Lawrence Rosen <span dir="ltr"><<a href="mailto:lrosen@rosenlaw.com" target="_blank">lrosen@rosenlaw.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>FYI. Larry</div><div><br></div><div><br></div><div><br></div><div><br></div><div><div style="font-size:100%">Sent from my Samsung Galaxy Tab®|PRO</div></div><br><br>-------- Original message --------<br>From: "Meeker, Heather J." <u></u> <br>Date:09/01/2015 3:18 PM (GMT-08:00) <br>To: <a href="mailto:license-review@opensource.org" target="_blank">license-review@opensource.org</a> <br>Cc: Gregory Miller <u></u>,John Sebes <u></u>,"Meeker, Heather J." <u></u>,<a href="mailto:christine@osetfoundation.org" target="_blank">christine@osetfoundation.org</a> <br>Subject: [License-review] Submission of OSET Public License for Approval <br><br> <div> <div class="MsoNormal" style="font-size:12pt;">1 September 2015<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">Members of the OSI License Review Community <u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;">VIA EMAIL to <a href="mailto:license-review@opensource.org" target="_blank">license-review@opensource.org</a><u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"> <u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;">CC: Christine M. Santoro, Esq., OSET Foundation General Counsel<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"> John Sebes, CTO, OSET Foundation / TrustTheVote Project<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">RE: Application for Consideration of the OSET Foundation OPL for OSD Compliance Approval<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">Greetings, Members of the OSI License Review Community:<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">The Open Source Election Technology Foundation (OSET) is pleased to submit the OSET Public License (OPL) for OSI license review and for discussion with the larger community. We believe the OPL falls into the special purpose category. We coordinated the drafting of this license, with review and input from other lawyers both within and outside of the Open Source Election Technology Foundation (OSET). <u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">OSET’s tax-exempt non-profit mission is to facilitate the development of technology to deliver free, and fair elections within an accountable and verifiable process. The public servants tasked with running our elections are poised to embrace the benefits of open source software licensing, but they also must work within the procurement rules of their profession. While we hesitated to create a new license, we have done so to meet the needs of our user community. Existing open source licenses do not deliver what our community needs, and we have written the OPL to meet these needs, and bridge the gap between open source licensing and many county and state government technology procurement regulations.<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">Our goal is for the OPL to facilitate the implementation of verifiable, accurate, secure, and transparent elections system technology that are not only federal- and state- certified, but also demonstrably worthy of the public’s trust. We believe this can only be accomplished using open source software. <u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">Our stakeholder community—elections administrators and officials—are very receptive to acquiring open source software-based election and voting systems provided the software (and related support and services) can be legally acquired through their procurement process. A primary ingredient of their procurement process is terms and conditions of software licensing that meet their regulatory requirements.<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">While governments already often acquire open source technology on an ad hoc basis under existing licenses, they face more, and different, hurdles acquiring open source election systems. Open source software that is merely part of a larger IT system is usually covered by two documents—the open source license, and an overarching (and often superseding) procurement agreement that fits with the applicable regulations. Where an agency is acquiring an entire open source technology system—especially technology to be used in public elections and subject to competitive bidding—procurement regulations need to be handled properly within the four corners of the open source license. <u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">Accordingly, OSET has based its license on the Mozilla Public License version 2.0 (“MPL”) with the addition of six modifications: <u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;">1. Governing Law<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;">2. Venue<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;">3. Government Rights<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;">4. March-in Rights<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;">5. Sovereign immunity <u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;">6. Deployment<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">These modifications address necessary requirements for the provisioning of election software to county and state government agencies and their contractors. Election technology procurement takes place primarily at the local (state, county, and jurisdictional) level; however, we would like the license to work at the federal level as well.<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">Also, we are mindful of the benefit of compatibility with other licenses. Like MPL 2.0, the OPL is compatible with GPL and LGPL 3.0. So, all software issued under OPL can be used in GPL and LGPL projects that have adopted the version 3 licenses. Therefore, any project that does not require the added provisions of OSET is free to elect not to use them, and to use GPL, or LGPL instead. We think this is the best way to address our constituents’ needs while limiting the compatibility problems of a new license. <u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">We have posted the text of the license (in plain text, PDF, and HTML), our rationale document, and an FAQ, as support for our submission. <span style="color:#1f497d"><a href="http://www.osetfoundation.org/public-license/" target="_blank">http://www.osetfoundation.org/public-license/</a>.</span><u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">Thank you for your consideration and we look forward to the discussion!<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">Sincerely,<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><u></u> <u></u></div> <div class="MsoNormal" style="font-size:12pt;">Heather Meeker<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;">O’Melveny & Myers<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;">Counsel to OSET<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><a href="tel:%2B1%20650.473.2635" value="+16504732635" target="_blank">+1 650.473.2635</a><u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;">&<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;">Gregory Miller<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;">Co-Executive Director, Chief Development Officer, OSET<u></u><u></u></div> <div class="MsoNormal" style="font-size:12pt;"><a href="tel:%2B1%20503.703.5150" value="+15037035150" target="_blank">+1 503.703.5150</a><u></u><u></u></div> </div> </div><br>_______________________________________________<br> CAVO mailing list<br> <a target="_blank" href="mailto:CAVO@opensource.org">CAVO@opensource.org</a><br> <a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/cavo" rel="noreferrer" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/cavo</a><br> <br></blockquote></div><br></div> <hr>_______________________________________________<br>
CAVO mailing list<br>
<a href="mailto:CAVO@opensource.org">CAVO@opensource.org</a><br>
<a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/cavo">https://lists.opensource.org/cgi-bin/mailman/listinfo/cavo</a><br>
</div>
</blockquote></span></body></html>