Packaging ROS2 build as pip package allowed?

Hi I have a question regarding the ROS2 license. It is my understanding that the components that make up ROS2 are all under the Apache 2.0 license.

What I would like to do is to package a built version of ROS2 (Dashing) as a Python (pip) package to allow for simple installation. This package would then be publicly available through a URL (obviously for free).
Is this allowed under the current license, and are there any caveats?

Best regards,
Josef

Thanks for your question. However we ask that you not double post questions following our support guidelines: http://wiki.ros.org/Support

For others reference there’s already a thread at: https://answers.ros.org/question/341661/is-redistributing-ros2-allowed/

ROS Discourse is for news and general interest discussions. ROS Answers provides a Q&A site which can be filtered by tags to make sure the relevant people can find and/or answer the question, and not overload everyone with hundreds of posts.

1 Like

To answer the specific question about pip:

You already use pip to install pure Python ROS packages by simply passing the git url.

If you are referring to release the Python packages to PyPI then I would say this is not a license question but if it is desired. The maintainers have intentionally not released ROS package to PyPI. So I don’t think you should do that without an explicit “ok” of each packages maintainer.