<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>Josh,</div><div><br></div><div>I would contend that the review would fail on this criteria:<br></div><div><br></div><div>b) does it contain unique and valid provisions, such that no existing<br>
license is sufficient?<br>
</div><div><br></div><div>The existing GPL3 "as is" is sufficient for the stated purpose of elections software.</div><div><br></div><div>In fact you could argue the reverse - that granting OSET license would diminish and conflict the elections community by inferring that GPL3 is NOT adequate as it stands.</div><div><br></div><div>OSET provided a link to their web site and their stated objectives - it appears the real purpose of the OSET license is to provide the criteria for inclusion in their own repository.</div><div><br></div><div>>>><br></div><div>The idea is that a jurisdiction will utilize a web service to determine
what it will take to implement an OSS based system using <b><u>software available from the OSET Foundation Repository.</u></b>
The repository ideally will contain a broad range of apps and solutions
(not only TrustTheVote Project components). Of course they'll be
limited to software which is federally certified to comprise a complete
voting system's minimal configuration "BOM."</div><div><br></div><div>All OSET-supported software development work results in open-source
software. The software is available via an open-source license, the <strong>OSET Public License</strong> (or OPL), and is distributed via our<a id="yui_3_17_2_1_1441918784375_357" target="_blank" href="https://github.com/trustthevote"> public-access source code repository.</a></div><div><<<</div><div><br></div><div>As you note - that is their prerogative - but not something that OSI needs to get involved in.</div><div><br></div><div>Thanks, </div><div><br></div><div>David<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] [License-review] OSET Foundation<br>
From: Josh Berkus <<a href="mailto:josh@postgresql.org">josh@postgresql.org</a>><br>
Date: Thu, September 10, 2015 12:45 pm<br>
To: <a href="mailto:lrosen@rosenlaw.com">lrosen@rosenlaw.com</a>, License submissions for OSI review<br>
<<a href="mailto:license-review@opensource.org">license-review@opensource.org</a>>, "'Tzeng, Nigel H.'"<br>
<<a href="mailto:Nigel.Tzeng@jhuapl.edu">Nigel.Tzeng@jhuapl.edu</a>>, "'Gregory Miller'"<br>
<<a href="mailto:gmiller@osetfoundation.org">gmiller@osetfoundation.org</a>><br>
Cc: 'Meegan Gregg' <<a href="mailto:meegan@osetfoundation.org">meegan@osetfoundation.org</a>>, 'CAVO'<br>
<<a href="mailto:cavo@opensource.org">cavo@opensource.org</a>>, 'Christine Santoro'<br>
<<a href="mailto:csantoro@osetfoundation.org">csantoro@osetfoundation.org</a>>, <a href="mailto:legal@osetfoundation.org">legal@osetfoundation.org</a><br>
<br>
On 09/09/2015 03:31 PM, Lawrence Rosen wrote:<br>
> Nigel, please don't put me in the false position of claiming that GPLv3<br>
> is good for everything. You know it has never been my favorite license.<br>
> :-) But in this case, considering the essential element of public trust<br>
> in public election software, I want the (psychologically) strongest<br>
> license in our arsenal. I DO want the public to be comforted by<br>
> attorneys at the ready to defend software freedom for this GPL<br>
> application. That will be reassuring around the world.<br>
<br>
*shrug* I agree with you, but that is not our job.<br>
<br>
Our job is to decide:<br>
<br>
a) does the OSET license meet the letter and spirit of the OSD?<br>
<br>
b) does it contain unique and valid provisions, such that no existing<br>
license is sufficient?<br>
<br>
c) is it legally sound?<br>
<br>
d) is it going to be used by a significant and sustained project?<br>
<br>
Any discussion about which license OSET should adopt and whether they<br>
really need their provisions or not should take place in other forums.<br>
You can do what you want, but I am not going to try to tell someone<br>
else what license they should pick for their project, and in my opinion<br>
such posts have no place in license-review.<br>
<br>
--Josh Berkus<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">https://lists.opensource.org/cgi-bin/mailman/listinfo/cavo</a><br>
</div>
</blockquote></span></body></html>