<p dir="ltr">Although not directly related, I started porting licenses to a machine readable format in git repo at <a href="https://github.com/OpenSourceOrg/licenses">https://github.com/OpenSourceOrg/licenses</a> </p>
<p dir="ltr">Eventually I'd like to even tag "releases", which makes stuff like pointing to licenses approved at X date more interesting.</p>
<p dir="ltr">(Patches, bugs, ideas welcome)</p>
<p dir="ltr">Paul</p>
<div class="gmail_quote">On Nov 13, 2015 3:31 PM, "Christopher Allan Webber" <<a href="mailto:cwebber@dustycloud.org">cwebber@dustycloud.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Feeling reminiscent of the good old days, when the threads of <a href="http://identi.ca" rel="noreferrer" target="_blank">identi.ca</a><br>
flowed freely with obscure licensing periphery, I have decided to try<br>
my hand at crafting where so many have dared to try (and fail) in<br>
penning an Open Source license worthy of the OSI license list.<br>
<br>
I decided to author the most open license of all time, for those who<br>
just can't decide over license minutiae. Here it is. Simply copy this<br>
into your programming headers and you are on the path to maximal<br>
freedom.<br>
<br>
# <PROGRAM NAME> -- (C) <YEAR> <AUTHOR NAME><br>
# Released under the "Any Free License 2015-11-05", whose terms<br>
# are the following:<br>
# This code is released under any of the free software licenses listed on<br>
# <a href="https://www.gnu.org/licenses/license-list.html" rel="noreferrer" target="_blank">https://www.gnu.org/licenses/license-list.html</a><br>
# which for archival purposes is<br>
# <a href="https://web.archive.org/web/20151105070140/http://www.gnu.org/licenses/license-list.html" rel="noreferrer" target="_blank">https://web.archive.org/web/20151105070140/http://www.gnu.org/licenses/license-list.html</a><br>
<br>
You may notice that this license has a convenient upgrade procedure.<br>
I suggest rolling releases of the license over time, updating to the<br>
latest link available from:<br>
<br>
<a href="https://web.archive.org/web/*/https://www.gnu.org/licenses/license-list.html" rel="noreferrer" target="_blank">https://web.archive.org/web/*/https://www.gnu.org/licenses/license-list.html</a><br>
<br>
If the OSI is not comfortable trusting the FSF license list at a<br>
particular date, one possible procedure in the rolling release system is<br>
that periodically, the OSI can review the FSF list, and make new<br>
releases based on verified and approved copies of the FSF license list.<br>
<br>
I would like to submit this license for consideration and inclusion on<br>
the OSI license review list, but am seeking feedback first. At current<br>
writing, approximately zero users include this text in their<br>
headers--however, at best estimation, this license has thousands if not<br>
tens or hundreds of thousands of users, and I believe that its mechanism<br>
provides novel benefits, and formalizing it as an acceptable choice for<br>
those who wish to promulgate Open Source principles will improve the<br>
currently unclear situation. Where others promise some freedoms, Any<br>
Free License delivers all possible freedoms, to the maximum extent<br>
permitted by law or currently recognized free licensing procedures.<br>
<br>
Any and all commentary to be derived from this email is left as an<br>
exercise to the reader. But I assure you, this is Not A Troll.<br>
<br>
- Christopher Allan Webber<br>
_______________________________________________<br>
License-discuss mailing list<br>
<a href="mailto:License-discuss@opensource.org">License-discuss@opensource.org</a><br>
<a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss" rel="noreferrer" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss</a><br>
</blockquote></div>