<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 1, 2020 at 8:33 PM McCoy Smith <mccoy@lexpan.law> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">4. Licenses that are redundant with more popular licenses [Several licenses<br>
in this group are excellent licenses and have their own followings, however<br>
these licenses were perceived by the License Proliferation Committee as<br>
completely or partially redundant with existing licenses.]<br>
<br>
6. Superseded licenses [Licenses in this category have been superseded by<br>
newer versions.]<br>
<br>
7. Licenses that have been voluntarily retired [Self-defining category. No<br>
one should use these licenses going forward, although we assume that<br>
licensors may or may not choose to continue to use them.]<br>
<br>I suppose one could create a supraset called "Deprecated Licenses"<br>
comprising subsets consisting of 4, 6 and 7 above, although you'd get some<br>
controversy about adding category 4 to that supraset, as some of the authors<br>
of licenses in category 4 do not believe that their licenses ought to be<br>
considered redundant and would likely object even more if their license were<br>
categorized as deprecated.<br>
<br></blockquote><div><br></div>For the purposes of this discussion, I think it's really important to distinguish between "this license is perfectly open source but we generally recommend sticking with a small set of well known licenses" and "this license is not open source after all".</div><div class="gmail_quote"><br></div><div class="gmail_quote">henrik<br></div>-- <br><div dir="ltr" class="gmail_signature"><a href="mailto:henrik.ingo@avoinelama.fi" target="_blank">henrik.ingo@avoinelama.fi</a><br>+358-40-5697354 skype: henrik.ingo irc: hingo<br><a href="http://www.openlife.cc" target="_blank">www.openlife.cc</a><br><br>My LinkedIn profile: <a href="http://fi.linkedin.com/pub/henrik-ingo/3/232/8a7" target="_blank">http://fi.linkedin.com/pub/henrik-ingo/3/232/8a7</a></div></div>