1

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

What's this mean? Suppose package X contains an algorithm that

  1. I applied to a task then published a paper. Am I not allowed to say "we applied package X on this task", or, when referring to the paper (not within the paper), "the paper used algorithm part of package X, developed by A and B"?
  2. I forked into my own package, Y, under MIT license, and built significantly upon. Eventually I might say, "Y is great!", while also mentioning somewhere (or in same sentence) that it has built upon X. Am I to either never mention X, or never praise my own work?

1 Answer 1

4

This clause clarifies that the names of contributors cannot be used to promote versions of the software that they didn't author.

For example, consider an imaginary Xunil operating system authored by a well-known Tinus Lorvalds and published under BSD-3-clause. I can now freely go around and give (or even sell) to other people copies of Xunil and tell them that they can trust it because Lorvalds wrote it.

But under that license I cannot add my own modifications and then advertise my modified version as Lorvalds' work. For example, I might introduce bugs or backdoors into the operating system. Lorvalds is not responsible for them, I am. As far as the license is concerned I'm totally allowed to create and distribute my buggy insecure version, as long as I leave other contributors like Lorvalds out of my promotional efforts.

This does not modify the attribution requirements, that the copyright and license notice (including Lorvalds' copyright statement!) must be preserved in the source code and in documentation.

Neither of your scenarios is affected by this license term, because your “X” is the name of the software, not the name of the contributors. Of course you are allowed to mention that you used a certain software. Of course you are allowed to state that your modified version is based on X. Of course you can advertise your modified version.

Personally, I think this clause of the BSD license is usually superfluous because the aspects it prohibits may already be prohibited by personality rights. However, issues such as personality rights and trademarks differ substantially between jurisdictions, so that clarifying this issue in the license can have value.

In contrast to BSD-3-clause, the Apache-2 license only touches on trademarks, not on contributor names:

This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

For example, if Xunil were Apache-2 licensed, and if there were a trademark on that name, then I wouldn't be allowed to advertise my buggy insecure version as “based on Xunil™”. But I would be allowed (and required!) to disclose this in the NOTICE file.

1
  • Thank you. Regarding "in the source code": 1) does it suffice to say like so in NOTICE, then like so in docstring? 2) how about same NOTICE, but like so in docstring? If 2) is a "yes", is it also "yes" if only the function's docstring changed? May 28 at 16:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.