Reason for going from Apache 2 license to Unlicense?

inexorabletash / text-encoding

Polyfill for the Encoding Living Standard's API

Other

720 stars 267 forks source link

Reason for going from Apache 2 license to Unlicense? #57

Closed paazmaya closed 7 years ago

paazmaya commented 7 years ago

I am just curious, what was the reason to make https://github.com/inexorabletash/text-encoding/commit/630eed16d5a89958f9ab279059d0c8b0960d5a51 happen?

I was about to request changing to MIT license from Unlicense, but instead opened this question...

inexorabletash commented 7 years ago

Since my main goal for the polyfill is to be a reference implementation for the Encoding standard (i.e. helps find bugs in the specified algoritihms), I wanted it to have as unrestrictive a license as possible, like the spec. (Someone also wanted to pull it into a CDN and the license tags was slightly off which prompted me to revisit which license was used, but I was planning to pick a new software license as close to CC0 as possible.)

paazmaya commented 7 years ago

Thank you for the clarification.

ilatypov commented 7 years ago

The no-warranty clause of Unlicense contradicts its no-ownership clause, according to Rick Moen. https://lists.opensource.org/pipermail/license-review/2012-January/001386.html

I wonder if this may get enterprise lawyers defensive when their employer adopts this package directly and via requisite dependencies?