-
Notifications
You must be signed in to change notification settings - Fork 986
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add BSD license option #220
Comments
Actually its not so much about PX4 compatibility (we don't link against mavros anyway) then about ROS compatibility. ROS is BSD licensed and a lot of ROS users depend on this licensing for their usage. For them having a GPL licensed communication layer as part of their setup is problematic and and has led to some of them using their own MAVLink to ROS bridges for licensing reasons only. I therefore would also suggest to ask the other contributors to MAVROS and MAVROS_EXTRAS if they would be willing to re-license under the same model. |
List of contributors for
List of contributors for |
FYI: i just released mavros 0.10.2 for Indigo and Jade (new). Really it's small release for new distro. |
@vooon Sounds good to me. |
Ok, I'm not really into to this licenses thing, so do I just say "OK"? :D |
Generally in the BSD I do not like that my code can be closed. But on the other hand mavros does not have any complex code... |
I would be finde with BSD Licence, because I thinkt the advantage of every ROS user beeing able to use mavros without limitations outweighs the "limitations" to the code |
@vooon sorry about not giving a response earlier. Agree BSD for ROS compatibility is good. |
Well, I got the agreement of all the authors of the code. |
sry for the late response. |
Ok, thanks! |
All done, next release (0.11) will be dual licensed GPL/BSD. |
@vooon This is really great news! I think it will greatly help the continuing adoption of mavros. The current situation with a top-level license file and LGPL in the headers is quite confusing. I would propose to remove the license text, and change it to a short paragraph along the lines below.
Then in the top level license file:
I would also suggest to add a CONTRIBUTIONS.md file similar to what other projects have, e.g. the PX4 one is here, which again restates the contributions requirements. |
Ok, i will do it later. |
Corrected XML for new MAV_DISTANCE_SENSOR message
@LorenzMeier wants more permissive BSD license, so mavros can be deeply integrated with PX4 codebase.
In that case i prefer not to change license, but add a second license.
The text was updated successfully, but these errors were encountered: