Skip to content
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

Closed
bradleeedmondson opened this issue Apr 3, 2017 · 5 comments
Closed

Comments

@bradleeedmondson
Copy link
Contributor

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:

  1. The name of the author may not be used to endorse or promote
    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.

@jlovejoy jlovejoy added this to the Immediate Release milestone Jun 9, 2017
@jlovejoy
Copy link
Member

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:

  1. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

But would need help with someone from the technical side as to how to implement such markup

@jlovejoy
Copy link
Member

marking as later, as need to make sure other lawyers agree

@jlovejoy jlovejoy modified the milestones: Immediate Release - 2.7, Later Release Dec 21, 2017
@jlovejoy jlovejoy modified the milestones: Later Release, 3.2 release Mar 22, 2018
@bradleeedmondson
Copy link
Contributor Author

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..."?

@goneall
Copy link
Member

goneall commented Jun 4, 2018

I created a pull request #650 which has been unit tested with the 2 variants for clause 3 mentioned above.

@jlovejoy
Copy link
Member

closing this issue as #650 has now been merged.

algitbot pushed a commit to alpinelinux/aports that referenced this issue Sep 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants