V-REP License compatibility with BSD-projects

Typically: "How do I... ", "How can I... " questions
Post Reply
bergercookie
Posts: 1
Joined: 26 Feb 2016, 10:39

V-REP License compatibility with BSD-projects

Post by bergercookie »

I'm trying to utilise V-REP to provide simulation capabilities for (some of) the currently available [MRPT](https://github.com/MRPT/mrpt) algorithms. MRPT is a project licensed under BSD. V-REP is dual-licensed (commercial and GPL) as described [here](http://www.coppeliarobotics.com/helpFil ... ensing.htm).

If we assume that the code snippets to be implemented are to abide to the GPL licensed they should be explicitly separated from the BSD-licensed MRPT code (e.g., in a different repository). However, there seems to be the [V-REP remote API](http://www.coppeliarobotics.com/helpFil ... erview.htm) which is [licensed under 3-Clause BSD](https://github.com/CoppeliaRobotics/rem ... icense.txt), i.e., different than the rest of V-REP, a license compatible with MRPT!

Is what I'm saying accurate so far?

Can we utilize the V-REP remote API in the BSD code without having to modify the license of the latter?

The question was originally published on stackoverflow.com - https://stackoverflow.com/posts/49318301

coppelia
Site Admin
Posts: 10336
Joined: 14 Dec 2012, 00:25

Re: V-REP License compatibility with BSD-projects

Post by coppelia »

Hello,

we wanted to have most items around V-REP (i.e. mainly plugins and auxiliary items such as the remote API) completely free in how they would be used. As it seems this can also be problematic for some other software packages that would require an OSI-compliant license type. For that reason those items were switched to a BSD license, the 3-clause BSD.
But as far as this concerns us, you are completely free in using the remote API in your 2-clause BSD code. The 3-clause BSD simply adds a non-endorsement clause compared to the 2-clause BSD.

Cheers

Post Reply