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

License clarification #26

Open
ariel11 opened this issue Aug 24, 2019 · 3 comments
Open

License clarification #26

ariel11 opened this issue Aug 24, 2019 · 3 comments

Comments

@ariel11
Copy link

ariel11 commented Aug 24, 2019

Hi, does license "BSD" mean the BSD-3-clause (https://opensource.org/licenses/BSD-3-Clause), or one of the other BSD licenses? Thanks!

@bartvanandel
Copy link

Good point. We're currently building an app and are working on proper attribution. So far, the only (indirect) dependency that we have that doesn't have an SPDX-compatible license id is readline. It would really help if your package were using one of the identifiers from the SPDX licenses list.

@fbeaudoincoveo
Copy link

I second that.

We have automatic validations to ensure that all of our project dependencies have a license that matches one of those allowed by our legal department. Unfortunately, "BSD" is considered too vague to be added to that list, which means that unless it is clarified, we'll have to either switch to another similar library that has a clear license, or implement the features we need on our own.

Would it be possible to use one of the SPDX identifiers instead?

https://spdx.org/licenses/

Thanks!

@lnqs
Copy link

lnqs commented Apr 8, 2024

Same for us. We're totally willing to live with not having a valid SPDX identifier, but knowing what BSD flavor this package is meant to be published as would be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants