This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
Update license text to proper BSD-3-Clause #31
Comments
|
Sounds good. I don't know when I'll be able to get to this, but PRs welcome. |
jeffcarp
pushed a commit
that referenced
this issue
Oct 25, 2019
So far, `LICENSE.md` contained the W3C variant of the BSD-3-Clause license. Replacing the license text should be ok because this is still basically the same license with just some wording differences. Furthermore, the project where the original code was taken from also did this change in web-platform-tests/wpt@402c8a6 (web-platform-tests/wpt#11191). This makes `LICENSE.md` consistent with the license declaration from `package.json` (which already did not refer to the W3C variant anymore) and fixes #31.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The https://github.com/jsdom/abab/blob/master/LICENSE.md file contains the "W3C 3-clause BSD License", but https://github.com/jsdom/abab/blob/master/package.json mentions the regular
BSD-3-clause. This is especially confusing becauseLICENSE.mdalso contains a link to https://github.com/w3c/web-platform-tests/blob/master/LICENSE.md#w3c-3-clause-bsd-license, claiming that the link points to the W3C variant, but the link target shows only the unmodified license (the W3C variant got removed in web-platform-tests/wpt@402c8a6#diff-37854d19817c792316d481f5beb93cc7).So I suggest to update
LICENSE.mdto also use the regular BSD-3-clause license (it only differs in wording) and remove all references to the W3C variant and the link to that other repo. This makes it easier for users of the package to confirm the license status.The text was updated successfully, but these errors were encountered: