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

Add SPDX identifiers to the licenses. #315

Merged
merged 2 commits into from
Jun 18, 2021
Merged

Conversation

clalancette
Copy link
Contributor

This is so we can use them at a higher layer. Note that the
SPDX identifier for "BSD License 2.0" is made up, since that
license is also made up. We eventually need to remove it,
but some of the core packages still depend on it (and really
should be switched over to BSD-3-Clause).

Signed-off-by: Chris Lalancette clalancette@openrobotics.org

This is so we can use them at a higher layer.  Note that the
SPDX identifier for "BSD License 2.0" is made up, since that
license is also made up.  We eventually need to remove it,
but some of the core packages still depend on it (and really
should be switched over to BSD-3-Clause).

Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
@gbalke
Copy link

gbalke commented Jun 17, 2021

Could be worth adding a comment mentioning these should be SPDX identifiers? Would be useful to be explicit in case people want to add new licenses!

Copy link
Contributor

@audrow audrow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@clalancette
Copy link
Contributor Author

Could be worth adding a comment mentioning these should be SPDX identifiers? Would be useful to be explicit in case people want to add new licenses!

The variable it gets put into is named 'spdx', which seems pretty clear to me. But maybe it is worthwhile to point to the URL where I got these; I'll add that.

Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
@clalancette
Copy link
Contributor Author

Full CI (since basically everything depends on this package):

  • Linux Build Status
  • Linux-aarch64 Build Status
  • macOS Build Status
  • Windows Build Status

@clalancette
Copy link
Contributor Author

clalancette commented Jun 18, 2021

The only failures are in mypy, which is a known issue right now.

@clalancette
Copy link
Contributor Author

Approved, and no new test failures. Going ahead and merging.

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

Successfully merging this pull request may close these issues.

None yet

3 participants