<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>
<p class="MsoNormal">1 September 2015<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Members of the OSI License Review Community
<u></u><u></u></p>
<p class="MsoNormal">VIA EMAIL to <a href="mailto:license-review@opensource.org" target="_blank">license-review@opensource.org</a><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">CC: Christine M. Santoro, Esq., OSET Foundation General Counsel<u></u><u></u></p>
<p class="MsoNormal"> John Sebes, CTO, OSET Foundation / TrustTheVote Project<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">RE: Application for Consideration of the OSET Foundation OPL for OSD Compliance Approval<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Greetings, Members of the OSI License Review Community:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal">1. Governing Law<u></u><u></u></p>
<p class="MsoNormal">2. Venue<u></u><u></u></p>
<p class="MsoNormal">3. Government Rights<u></u><u></u></p>
<p class="MsoNormal">4. March-in Rights<u></u><u></u></p>
<p class="MsoNormal">5. Sovereign immunity <u></u><u></u></p>
<p class="MsoNormal">6. Deployment<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thank you for your consideration and we look forward to the discussion!<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Sincerely,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Heather Meeker<u></u><u></u></p>
<p class="MsoNormal">O’Melveny & Myers<u></u><u></u></p>
<p class="MsoNormal">Counsel to OSET<u></u><u></u></p>
<p class="MsoNormal"><a href="tel:%2B1%20650.473.2635" value="+16504732635" target="_blank">+1 650.473.2635</a><u></u><u></u></p>
<p class="MsoNormal">&<u></u><u></u></p>
<p class="MsoNormal">Gregory Miller<u></u><u></u></p>
<p class="MsoNormal">Co-Executive Director, Chief Development Officer, OSET<u></u><u></u></p>
<p class="MsoNormal"><a href="tel:%2B1%20503.703.5150" value="+15037035150" target="_blank">+1 503.703.5150</a><u></u><u></u></p>
</div>
</div><br>_______________________________________________<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" rel="noreferrer" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/cavo</a><br>
<br></blockquote></div><br></div>