<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I agree with Luis. How does this additional requirement change compliance with the OSD? It seems quite vague and could raise concerns in the community.<b><o:p></o:p></b></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> License-discuss <license-discuss-bounces@lists.opensource.org>
<b>On Behalf Of </b>Luis Villa<br>
<b>Sent:</b> Sunday, December 09, 2018 3:42 PM<br>
<b>To:</b> license-discuss@lists.opensource.org<br>
<b>Subject:</b> Re: [License-discuss] Proposed license decision process<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">[EXTERNAL]</span></strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="100%" align="center">
</div>
</div>
<div>
<div>
<p class="MsoNormal">(1) what is the proposed test for "guarantees software freedom"?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">(2) if the answer to #1 is something like "the same tests as the FSF would apply" (either explicitly or implicitly), does the board plan to talk with FSF about merging license lists and review processes? If not, why not?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Thu, Dec 6, 2018 at 10:38 PM Richard Fontana <<a href="mailto:richard.fontana@opensource.org">richard.fontana@opensource.org</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">At a recent meeting, the OSI Board discussed requests to clarify the<br>
license approval process (documented at<br>
<a href="https://opensource.org/approval" target="_blank">https://opensource.org/approval</a>). We've drafted the guidelines below,<br>
which we aim to follow when reviewing licenses, to ensure that a<br>
license will be approved only if it conforms to the Open Source<br>
Definition and provides software freedom.<br>
<br>
"Decision Date" for a license normally means (a) 60 days after a<br>
license is initially submitted for review, and (b) 30 days after<br>
submission of a revised version of a license that was previously<br>
submitted for review. A license is considered to be submitted for<br>
review if it follows the process set forth at<br>
<a href="https://opensource.org/approval" target="_blank">https://opensource.org/approval</a>. While we will try our best to adhere<br>
strictly to this 60/30 day Decision Date definition, circumstances may<br>
require us to extend the Decision Date further.<br>
<br>
On the Decision Date, the OSI will announce one of four possible decisions:<br>
<br>
1. Defer for another 30-day discussion cycle, if community discussion<br>
of conformance of the license to the OSD remains active<br>
<br>
2. Approve, if (a) there is sufficient consensus emerging from<br>
community discussion that approval is justified, and (b) the OSI<br>
determines that the license conforms to the Open Source Definition and<br>
guarantees software freedom<br>
<br>
3. Reject if (a) the OSI determines that the license cannot<br>
practically be remedied to adequately guarantee software freedom, or<br>
(b) there is sufficient consensus emerging from community discussion<br>
that the license should be rejected for substantive reasons, or (c)<br>
the license is problematic for nonsubstantive reasons (for example, it<br>
is poorly drafted or significantly duplicative of one or more existing<br>
OSI-approved licenses)<br>
<br>
4. Withhold approval, if (a) the OSI determines that approval would<br>
require reworking the license and (b) the license submitter appears<br>
willing and able to revise the license constructively<br>
<br>
We would appreciate your comments.<br>
<br>
- Richard<br>
<br>
_______________________________________________<br>
License-discuss mailing list<br>
<a href="mailto:License-discuss@lists.opensource.org" target="_blank">License-discuss@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" target="_blank">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><o:p></o:p></p>
</blockquote>
</div>
</div>
<span style="font-size: 11px;"><font style="font-size: 11px;" color="#008000">Please consider the environment before printing this email.</font></span><font style="font-size: 11px;" color="#008000">
<br>
<br>
<font color="#808080" size="1" face="Verdana">
The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. To contact us directly, send to postmaster@dlapiper.com. Thank you.
<br>
</font></font></body>
</html>