<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I suspect these conversations will get very interesting when we
release Prime III as open source under GPLv3. We are planning a
release on September 28th. Once we have proven release that has been
and will be used in binding elections, I suspect these debates will
intensify. Keep in mind, Prime III runs local, i.e. no network
connection required, through your web broswer and doesn't store any
information about voters. Hence, no one has hacked it or claimed
they can hack it because it prints a paper ballot that is actually
the ballot of record, not a digital ballot. <br>
<br>
Stay tuned...<br>
<br>
<br>
<div class="moz-cite-prefix">On 9/6/15 1:01 PM, Brent Turner wrote:<br>
</div>
<blockquote
cite="mid:CAB1+w6K7-V36TooDJ1FOagcEDCisjTXPJtByctVrnrz8FE+XwA@mail.gmail.com"
type="cite">
<div dir="ltr">One concern is this newly licensed code becoming
corporate owned code, and that possible " back-door" issue may
diminish the enthusiasm of the coders work toward best election
system efforts. Though this might not be a point of irritation
for academics, the election system open source and security
community has noted this and is curious what is compelling OSET
to avoid GPLv3 .. Will the code eventually go to Kapor's
friends at Apple ?
<div><br>
</div>
<div>Kapor's noted involvement is only as relevant as his close
ties with Apple and other commercial entities that may be the
benefactors here. In the space of elections and vote counting,
we have witnessed much sleight of hand, so applications that
avoid GPLv3 for voting system use raises eyebrows, as does
OSETS previous political actions. </div>
<div><br>
</div>
<div>CAVO considers all the humans to be " stakeholders" here.
and does not anticipate "special" harm. <br>
<div><br>
</div>
<div><br>
</div>
<div> </div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, Sep 6, 2015 at 7:36 AM, Richard
Fontana <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:fontana@sharpeleven.org" target="_blank">fontana@sharpeleven.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
How would CAVO, or the open source voting systems space
generally, be<br>
harmed if this license were approved? (How is it any
different than if<br>
the OSET Foundation decided to use an existing non-GPLv3
OSI-approved<br>
license, such as MPL 2.0 ... or even "GPLv2 only"?)<br>
<br>
I think the politics lurking behind these license
submissions are<br>
worth bringing to light and examining (something which
hasn't been<br>
done enough in the past, IMO) but all I'm seeing here so far
is<br>
general concern about the OSET Foundation's close connection
to the<br>
wealthy Mr. Kapor.<br>
<br>
<br>
On Fri, Sep 04, 2015 at 07:50:14PM -0700, Brent Turner
wrote:<br>
> Maybe there are answers in the sidebar- - What compels
someone like Mitch Kapor<br>
> to create a new license for election systems ? What
compels him to be in the<br>
> space of "open source " voting systems to begin with ?
Certainly we assume<br>
> he has more than enough money but is it just greed for
more ? Is it the power<br>
> that comes with pioneering a new license so that he can
be the " kingpin " of<br>
> voting ? This is the concern of the open source voting
pioneer community. OSET<br>
> has consistently ignored. the open source community and
now this new license<br>
> issue is upon us. Why would we need a new license
rather than use GPLv3 ? . <br>
><br>
> On Fri, Sep 4, 2015 at 4:51 PM, Lawrence Rosen <<a
moz-do-not-send="true" href="mailto:lrosen@rosenlaw.com"><a class="moz-txt-link-abbreviated" href="mailto:lrosen@rosenlaw.com">lrosen@rosenlaw.com</a></a>>
wrote:<br>
><br>
><br>
> There is nobody more qualified than Heather Meeker
to shepherd the creation<br>
> of a new open source license. She's an expert.<br>
><br>
> <br>
><br>
> Intelligent and serious consideration went into the
OSET Public License<br>
> (OPL). After a detailed review by this OSI
license-review@ committee and<br>
> perhaps some slight modifications by its authors,
this license will almost<br>
> certainly be approved.<br>
><br>
> <br>
><br>
> What concerns me still, though, is how this new
license will be absorbed by<br>
> the open source community and by election officials
around the world.<br>
> Heather correctly criticized me earlier for arguing
that this new license<br>
> is addressing "a non-existent problem." Actually,
it is mostly adding to an<br>
> existing difficult problem.<br>
><br>
> <br>
><br>
> David Webber here accurately described "an open
source solution stack for a<br>
> typical voting solution today [that[ includes a
whole raft of licenses."<br>
> Any government agency that intends to acquire an
open source election<br>
> system will inevitably require components such as
an operating system,<br>
> database, printer and scanner drivers, and a main
voting software module,<br>
> presumably under a cornucopia of licenses including
Apache, MPL, ECL, GPL,<br>
> and a whole lot of BSD. We expect FOSS and
commercial add-ons that<br>
> aggregate with that election stuff.<br>
><br>
> <br>
><br>
> Add to this one more open source license.<br>
><br>
> <br>
><br>
> We'll also have to wait for all the potentially
interested developer<br>
> foundations and commercial distributors and
customers to understand if the<br>
> new license is compatible with what they are
already doing – specifically<br>
> for derivative works.<br>
><br>
> <br>
><br>
> Does anyone here believe that a new open source
license will cure the<br>
> existing confusion among government agencies that
already engage in FOSS<br>
> licensing?<br>
><br>
> <br>
><br>
> As for me, I'm personally rather bored with
evaluating (yet another) open<br>
> source license, so I leave the rest of that fun
discussion to everyone<br>
> else. :-)<br>
><br>
> <br>
><br>
> Have a great holiday weekend!<br>
><br>
> <br>
><br>
> /Larry<br>
><br>
> <br>
><br>
><br>
> _______________________________________________<br>
> CAVO mailing list<br>
> <a moz-do-not-send="true"
href="mailto:CAVO@opensource.org">CAVO@opensource.org</a><br>
> <a moz-do-not-send="true"
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>
><br>
><br>
<br>
> _______________________________________________<br>
> License-review mailing list<br>
> <a moz-do-not-send="true"
href="mailto:License-review@opensource.org">License-review@opensource.org</a><br>
> <a moz-do-not-send="true"
href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review"
rel="noreferrer" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review</a><br>
<br>
_______________________________________________<br>
CAVO mailing list<br>
<a moz-do-not-send="true" href="mailto:CAVO@opensource.org">CAVO@opensource.org</a><br>
<a moz-do-not-send="true"
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>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
CAVO mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CAVO@opensource.org">CAVO@opensource.org</a>
<a class="moz-txt-link-freetext" href="https://lists.opensource.org/cgi-bin/mailman/listinfo/cavo">https://lists.opensource.org/cgi-bin/mailman/listinfo/cavo</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Juan E. Gilbert, Ph.D.
Andrew Banks Family Preeminence Endowed Professor & Chair
Computer & Information Science & Engineering Department
University of Florida
P.O. Box 116120
Gainesville, FL 32611
352.562.0784 (V)
352.392.1220 (F)
<a class="moz-txt-link-abbreviated" href="mailto:juan@ufl.edu">juan@ufl.edu</a>
Twitter: @DrJuanGilbert
<a class="moz-txt-link-freetext" href="http://www.juangilbert.com/">http://www.juangilbert.com/</a> </pre>
</body>
</html>