<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.6.6">
</HEAD>
<BODY>
On Sun, 2015-09-06 at 13:51 -0400, Richard Fontana wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
On Sun, Sep 06, 2015 at 09:34:15AM -0700, Lawrence Rosen wrote:<BR>
<FONT COLOR="#737373">> I'm concentrating instead on OSET's argument that government agencies need this license in order to properly acquire FOSS election software. If that's a valid fear, our community has some work to do to fix it -- and not necessarily introduce another license to gloss it over.</FONT><BR>
<BR>
I will say that I'm rather skeptical of this argument.<BR>
</BLOCKQUOTE>
<BR>
I too do not understand the argument around procurement (this is an honest statement of ignorance, not a set up for a counter argument). <BR>
<BR>
As a former CIO and CTO within public higher education, I worked with both state and public university procurement offices. In that time we acquired open source software distributed under a variety of licenses (e.g. Moodle via the GPL <<A HREF="https://docs.moodle.org/dev/License">https://docs.moodle.org/dev/License</A>>; Sakai via Apache and Educational Community License <<A HREF="https://www.apereo.org/licensing/">https://www.apereo.org/licensing/</A>>, etc.). We also procured systems and services from commercial vendors that included open source licensed software bundled with proprietary software (e.g. Apple computers <<A HREF="http://www.apple.com/opensource/">http://www.apple.com/opensource/</A>>, Instructure Canvas via an open core model with AGPL <<A HREF="https://github.com/instructure/canvas-lms/wiki">https://github.com/instructure/canvas-lms/wiki</A>>).<BR>
<BR>
Never once while working within the University of California, State University of New York nor University of Massachusetts, did I hear procurement officers or contract managers raise issues around open source licensing. Again, I and my colleagues may be ignorant of the issues OSET has identified, but I would very much like to learn more. Especially as I still provide consultation to UMass. I will also follow up with my colleagues within UMass' procurement and legal offices. In the mean time, can someone point me to the relevant discussions, information around this?<BR>
<BR>
Thank you,<BR>
Patrick<BR>
<BR>
<BR>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
|| | | |||| || || | |||| ||| | ||| <BR>
Patrick Masson<BR>
General Manager & Director<BR>
Open Source Initiative<BR>
855 El Camino Real, Ste 13A, #270<BR>
Palo Alto, CA 94301<BR>
United States<BR>
OSI Phone: <A HREF="tel:%28415%29%20857-5398">(415) 857-5398</A><BR>
Direct Phone: (970) 4MASSON<BR>
Skype: massonpj<BR>
Em: <A HREF="mailto:masson@opensource.org">masson@opensource.org</A><BR>
Ws: <A HREF="http://www.opensource.org/">www.opensource.org</A>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>