ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Making a module proprietary

asked 2013-07-29 09:26:35 -0500

RP gravatar image

updated 2013-07-29 11:38:35 -0500


The paper on ROS (ROS: an open-source Robot Operating System) mentions the following:

"As such, systems built around ROS can use fine-grain licensing of their various components: individual modules can incorporate software protected by various licenses ranging from GPL to BSD to proprietary, but license “contamination” ends at the module boundary"

Can I have more information on this?


edit retag flag offensive close merge delete


I too would be interested in finding more information on this. Thank you for posting!

eacousineau gravatar image eacousineau  ( 2013-09-06 20:51:25 -0500 )edit

1 Answer

Sort by » oldest newest most voted

answered 2013-10-11 07:47:54 -0500

tfoote gravatar image

If you are writing a module you can keep it proprietary by not releasing its source. Note you do need to comply with any licenses of code with which you integrate.

Much of the ROS ecosystem is released under BSD or Apache 2 both of which are very permissive licenses.

edit flag offensive delete link more

Question Tools


Asked: 2013-07-29 09:26:35 -0500

Seen: 342 times

Last updated: Oct 11 '13