Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Making a module proprietary

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

RP
11 ●1 ●1 ●3

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

Hi,

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

"As such, systems built around ROS can use ﬁne-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?

Thanks

edit retag flag offensive close merge delete

Comments

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

eacousineau ( 2013-09-06 20:51:25 -0600 )edit

add a comment

1 Answer

Sort by » oldest newest most voted

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

tfoote

58457 ●128 ●550 ●526 http://www.ros.org/

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

add a comment

Question Tools

Stats

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

Seen: 562 times

Last updated: Oct 11 '13

ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.

Making a module proprietary edit

Comments

1 Answer

Question Tools

Stats

Making a module proprietary