[License-discuss] Proposed license decision process

Radcliffe, Mark Mark.Radcliffe at dlapiper.com
Mon Dec 10 13:16:11 UTC 2018

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.

From: License-discuss <license-discuss-bounces at lists.opensource.org> On Behalf Of Luis Villa
Sent: Sunday, December 09, 2018 3:42 PM
To: license-discuss at lists.opensource.org
Subject: Re: [License-discuss] Proposed license decision process

(1) what is the proposed test for "guarantees software freedom"?
(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?

On Thu, Dec 6, 2018 at 10:38 PM Richard Fontana <richard.fontana at opensource.org<mailto:richard.fontana at opensource.org>> wrote:
At a recent meeting, the OSI Board discussed requests to clarify the
license approval process (documented at
https://opensource.org/approval). We've drafted the guidelines below,
which we aim to follow when reviewing licenses, to ensure that a
license will be approved only if it conforms to the Open Source
Definition and provides software freedom.

"Decision Date" for a license normally means (a) 60 days after a
license is initially submitted for review, and (b) 30 days after
submission of a revised version of a license that was previously
submitted for review. A license is considered to be submitted for
review if it follows the process set forth at
https://opensource.org/approval. While we will try our best to adhere
strictly to this 60/30 day Decision Date definition, circumstances may
require us to extend the Decision Date further.

On the Decision Date, the OSI will announce one of four possible decisions:

1. Defer for another 30-day discussion cycle, if community discussion
of conformance of the license to the OSD remains active

2. Approve, if (a) there is sufficient consensus emerging from
community discussion that approval is justified, and (b) the OSI
determines that the license conforms to the Open Source Definition and
guarantees software freedom

3. Reject if (a) the OSI determines that the license cannot
practically be remedied to adequately guarantee software freedom, or
(b) there is sufficient consensus emerging from community discussion
that the license should be rejected for substantive reasons, or (c)
the license is problematic for nonsubstantive reasons (for example, it
is poorly drafted or significantly duplicative of one or more existing
OSI-approved licenses)

4. Withhold approval, if (a) the OSI determines that approval would
require reworking the license and (b) the license submitter appears
willing and able to revise the license constructively

We would appreciate your comments.

- Richard

License-discuss mailing list
License-discuss at lists.opensource.org<mailto:License-discuss at lists.opensource.org>
Please consider the environment before printing this email.

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 at dlapiper.com. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20181210/8965677b/attachment.html>

More information about the License-discuss mailing list