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

Which variantof the BSD license does this project use? #30

Open
jiaxshi opened this issue Nov 11, 2024 · 3 comments
Open

Which variantof the BSD license does this project use? #30

jiaxshi opened this issue Nov 11, 2024 · 3 comments

Comments

@jiaxshi
Copy link

jiaxshi commented Nov 11, 2024

We get "BSD" in package.xml. There are multiple variants of the BSD license. Which specific one applies to our project? BSD-3-Clause?

@mikeferguson
Copy link
Contributor

I can't speak to map_msgs - because I'm not really sure where that came from. The move_base_msgs came from the ros-planning/navigation repo originally, which was released by Willow Garage under a 3-clause BSD license (you can see that in nearly every header file in that repo - except for AMCL, which was released under LGPL since it predates the navigation stack)

@jiaxshi
Copy link
Author

jiaxshi commented Nov 12, 2024

@mikeferguson Thanks for your info. We are using the msg package in meta-ros with yocto project. In latest yocto, it checks that the project uses a clear LICENSE rather than an ambiguours one.
Actually many ROS packages are in the same situation.

@mintar
Copy link

mintar commented Nov 12, 2024

Adding a LICENSE file would help. Also, it's good practice to use a string from the SPDX License List in the package.xml, so instead of BSD use BSD-3-Clause. There's also more support for SPDX licenses in the package.xml specification (see this discussion).

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

3 participants