<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Someone can start <a moz-do-not-send="true"
href="https://wiki.opensource.org/bin/Working%20Groups%20%26%20Incubator%20Projects/License%20De-Listing%20Process%20Proposal%20Draft/">here</a>
if they're interested in pursuing this topic.<br>
<br>
Pam<br>
<br>
<div class="moz-signature">Pamela S. Chestek<br>
Chestek Legal<br>
PO Box 2492<br>
Raleigh, NC 27602<br>
<a class="moz-txt-link-abbreviated" href="mailto:pamela@chesteklegal.com">pamela@chesteklegal.com</a><br>
(919) 800-8033<br>
<a class="moz-txt-link-abbreviated" href="http://www.chesteklegal.com">www.chesteklegal.com</a><br>
<br>
</div>
<div class="moz-cite-prefix">On 12/14/2022 1:34 PM, Chris DiBona
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAEq5uwkd4msA8N=_Ayi9-nVE_44xVzWFz=ksPb4+YcprR+7Tmg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">Without betraying my feelings on recently approved
licenses. I've always thought the osi could move licenses into a
deprecated or 'legacy' state , so that programs under those
licenses until date x could be considered open source, but after
that... I mean, there's already a break down of superseded, etc
on the Osi site....
<div dir="auto"><br>
</div>
<div dir="auto">But maybe that's too nuanced a view of things
:-) Goodness knows the number of projects adding on nonsense
extra clauses continue to proliferate, mostly in the
JavaScript community....but I digress.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Chris</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Dec 14, 2022, 9:08 PM
McCoy Smith <a class="moz-txt-link-rfc2396E" href="mailto:mccoy@lexpan.law"><mccoy@lexpan.law></a> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
> -----Original Message-----<br>
> From: License-discuss <<a
href="mailto:license-discuss-bounces@lists.opensource.org"
target="_blank" rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">license-discuss-bounces@lists.opensource.org</a>>
On<br>
> Behalf Of Pamela Chestek<br>
> Sent: Wednesday, December 14, 2022 11:47 AM<br>
> To: <a
href="mailto:license-discuss@lists.opensource.org"
target="_blank" rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">license-discuss@lists.opensource.org</a><br>
> Subject: Re: [License-discuss] Retroactively disapproving
licenses<br>
> <br>
> To do some foreshadowing, the Working Group that was
formed to make<br>
> recommendations for improving the license review process
will soon be<br>
> publishing its recommendation. This was originally within
their remit, but the<br>
> group agreed that it was complex enough (and frankly I
think we were all a<br>
> little tired at this point) that it should be a separate
undertaking. Personally, I<br>
> think the OSI has to tread carefully to avoid unintended
consequences and<br>
> therefore needs to have a lot more information before
deciding whether and<br>
> how to delist a license, such as:<br>
> <br>
> How many projects are using the licenses How significant
they are How many<br>
> downstream users there are, and whether they have relied
on the status as<br>
> "open source" in some way, e.g., suddenly a component
will have to be<br>
> removed because it no longer has an "open source" license
Whether anyone<br>
> is doing marketing around the term "open source" for a
license considered<br>
> for delisting<br>
> <br>
> I'm sure with more thought there is other information
that would be<br>
> relevant.<br>
> <br>
> So McCoy, are you volunteering to head up a working group
to work on this<br>
> question? 😁<br>
> <br>
Hey, not like I haven't volunteered for OSI in a related area
before:<br>
<a
href="https://opensource.org/proliferation-report#:~:text=The%20purpose%20of%20this%20document%20is%20to%20report,lessen%20or%20remove%20issues%20caused%20by%20license%20proliferation.%22"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://opensource.org/proliferation-report#:~:text=The%20purpose%20of%20this%20document%20is%20to%20report,lessen%20or%20remove%20issues%20caused%20by%20license%20proliferation.%22</a><br>
😉<br>
<br>
<br>
_______________________________________________<br>
The opinions expressed in this email are those of the sender
and not necessarily those of the Open Source Initiative.
Official statements by the Open Source Initiative will be sent
from an <a href="http://opensource.org" rel="noreferrer
noreferrer" target="_blank" moz-do-not-send="true">opensource.org</a>
email address.<br>
<br>
License-discuss mailing list<br>
<a href="mailto:License-discuss@lists.opensource.org"
target="_blank" rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">License-discuss@lists.opensource.org</a><br>
<a
href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><br>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Official statements by the Open Source Initiative will be sent from an opensource.org email address.
License-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:License-discuss@lists.opensource.org">License-discuss@lists.opensource.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a>
</pre>
</blockquote>
<br>
</body>
</html>