Hey there @mhampton, sorry for the delay, I’m subscribed to several categories, but there doesn’t seem to be a way to subscribe to “no category”. Anyway, happy to help here. All the information in the following paragraph comes from snapcraft’s catkin plugin.
The only part of ROS that the plugin definitely, certainly adds into the snap is roslib. From there, it depends on the options you’re using and your software in general. Specifically, take note of the
rosinstall-files options: both have an effect on the software put into the snap. Finally, it uses rosdep to determine the dependencies of your workspace and includes them in the snap, so you’ll need to determine those yourself.
Regarding ROS licensing specifically, quoting this page:
The core of ROS is licensed under the standard three-clause BSD license. This is a very permissive open license that allows for reuse in commercial and closed source products. You can find more about the BSD license here:
While the core parts of ROS are licensed under the BSD license, other licenses are commonly used in the community packages, such as the Apache 2.0 license, the GPL license, the MIT license, and even proprietary licenses. Each package in the ROS ecosystem is required to specify a license, so that it is easy for you to quickly identify if a package will meet your licensing needs.
In other words, while roslib and rosmaster/core are licensed under BSD, not everything coming from the ROS repo is. You’ll need to take a look at what your software is using.