ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | Q&A
Ask Your Question

Manifest's license tag for proprietary ROS packages

asked 2016-02-17 13:08:34 -0600

spmaniato gravatar image

The license tag of package manifests (package.xml) seems to be mandatory. What should I set it to for a proprietary package that won't be open-sourced? (Assuming I'm not including or linking against "infectious" open-source licenses of course.)

I've been writing the following and then adding copyright headers to the actual source code.

edit retag flag offensive close merge delete



I use Proprietary for the license on my private packages as well.

ahendrix gravatar image ahendrix  ( 2016-02-17 13:16:23 -0600 )edit

1 Answer

Sort by » oldest newest most voted

answered 2016-02-18 04:59:35 -0600

gvdhoorn gravatar image

updated 2016-02-18 04:59:54 -0600

Same here. REP-140 gives examples of OSS licenses (here), anything else is up to you.

What you shouldn't do though, is paste your license text in the license tag. I've seen ppl do that, and it's not what the tag is for.

edit flag offensive delete link more



Related, now license text file can be specified in package.xml format=3 after this PR.

130s gravatar image 130s  ( 2018-06-22 14:54:51 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2016-02-17 13:08:34 -0600

Seen: 904 times

Last updated: Feb 17 '16