New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SPDX matching guidelines and common variant of BSD-3-Clause #399
Comments
I agree that these two variations are not legally different and should be accommodated in our matching markup. Text of clause 3 we have for comparison:
But would need help with someone from the technical side as to how to implement such markup |
marking as later, as need to make sure other lawyers agree |
discussed on legal call today; we agree that these two wordings are identical and they should be marked up to both match BSD-3 clause. one thing to note is that we need to be careful not to do a simple match for both "may" and "may not" as their meanings are inverted in the two versions by language earlier in the sentence. Would @wking or @goneall be able to write and test some <alt> tags that will match both, but not the hybrids "neither ... may not" or "The name of the author may be used..."? |
…issue #399 Signed-off-by: Gary O'Neall <gary@sourceauditor.com>
I created a pull request #650 which has been unit tested with the 2 variants for clause 3 mentioned above. |
closing this issue as #650 has now been merged. |
As per [0] at the upstream and the source itself in [1], the license is BSD-3-Clause, not GPL. Interestingly, it is one of the alternative variants discussed in [2]. [0] https://metadata.ftp-master.debian.org/changelogs/main/n/netcat-openbsd/netcat-openbsd_1.217-2_copyright [1] http://cdn-fastly.deb.debian.org/debian/pool/main/n/netcat-openbsd/netcat-openbsd_1.130.orig.tar.gz [2] spdx/license-list-XML#399
From Richard:
I've noticed that a very common variant of what I think of as the 3-clause BSD license has this as its third clause:
products derived from this software without specific prior
written permission.
Am I right that such a license, otherwise matching[1] what SPDX calls 'BSD-3-Clause', would not be considered a match to 'BSD-3-Clause' because clause 3 does not say 'Neither the name of the author nor the name of its contributors...'?
Asking because this seems to be the case from a strict reading of the SPDX matching guidelines, yet the result also seems to violate its spirit.
Richard
[1]The non-use of 'contributors' results in changes to the stock disclaimer language too. I don't think it is clear whether this too would result in a non-match under the SPDX guidelines.
The text was updated successfully, but these errors were encountered: