Link to the choose-a-license thread posts at the end of the "why" section.

This commit is contained in:
Rob Landley 2024-12-22 11:17:14 -06:00
parent 69ef8463ff
commit 027a3c459c

View File

@ -51,7 +51,14 @@ by sticking the two licenses at
<a href=http://git.busybox.net/busybox/tree/networking/ping.c?id=887a1ad57fe978cd320be358effbe66df8a068bf>opposite ends of the file</a> and hoping nobody
noticed.</a>
<p>Note: I asked <a href=https://www.oreilly.com/openbook/opensources/book/kirkmck.html>Kirk McKusick</a> for permission to call this a BSD license at
<p>I asked <a href=https://www.oreilly.com/openbook/opensources/book/kirkmck.html>Kirk McKusick</a> for permission to call this a BSD license at
a conference shortly before I started using the name,
and <a href=0bsd-mckusick.txt>again in 2018</a>.</p>
<p>In 2017 while walking 0BSD through the github choose-a-license approval
process, I copied to my blog two very long posts in the thread
(<a href=https://landley.net/notes-2017.html#26-03-2017>part one</a>,
<a href=https://landley.net/notes-2017.html#27-03-2017>part two</a>)
explaining why the license is like that and what it was trying to
accomplish. It seems to have <a href=https://github.com/search?q=license%3A0bsd&type=Repositories>been convincing</a>.</p>
<!--#include file="footer.html" -->