Re:The Unlicense is an inferior license wrapped in an atroci...
by chrismorgan on Friday March 04, 2022 @11:39PM
(#30564306)
Thanks for chipping in on this thread, you’re expressing things nice and clearly, now I have a few more links for describing this unhappy situation in open-source licensing.
Any chance you could change the slug on that first link from Rely-on-OSI to Dont-Rely-on-OSI-Approval or similar? The current URL suggests the opposite of the article’s content. Hopefully adding a redirect isn’t too onerous.
Re:The Unlicense is an inferior license wrapped in an atroci...
by kemitchell on Saturday March 05, 2022 @12:18PM
(#30569477)
Point taken on page URL. Alas, it's been up a while and I don't have a ready redirect mechanism in place.
I put energy into cofounding Blue Oak Council to publish rigorous resources, like our permissive license list, https://blueoakcouncil.org/list, in large part out of disappointment and dread, pulling back the curtain on the institutional processes for license review. As lawyers, we need functional resources like that license list, to incorporate by reference into contracts and policies. Fundamentally political artifacts, like OSI or FSF or Debian whitelists, are type errors in those contexts.
> everybody knows what MIT, BSD, Apache, and the various GPL licenses imply
I'm afraid that's not true. I would say there is broad agreement on many of the core aspects. And in many situations, practically, the specific license terms don't matter nearly as much as widely help expectations. But key concepts affecting fairly common situations remain unclear, and those details come out when there's money or strategic leverage on the line. See, e.g. the list Heather Meeker keeps at https://heathermeeker.com/open-source-faq/what-are-the-most-... See also the whole debate on permissive licenses and standards-essential patents: https://writing.kemitchell.com/2019/10/03/Open-Standards.htm....