Comments (48)
@ahoarau I am reading into the licenses. I don't see why the LGPL-V2 prevents any larger work (open or closed) to link against this library.
My objection to change to MIT or Apache 2.0 license is that it allows for closed source modifications of this library. This library is open source and I think any modified version should be kept open.
from orocos_kinematics_dynamics.
I was just lead to believe that you agreed on that in the last issue.
I am sorry I gave you the impression I did. I just wanted to know the opinion of Smits first.
I will come back to you about whether I agree or not.
from orocos_kinematics_dynamics.
from orocos_kinematics_dynamics.
@ahoarau you still want to migrate to lgpl 3.0 with the linking exception?
As mentioned before, I agree with it.
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
@MatthijsBurgh LGPL-v2 prevents from static linking - at least makes it extremely difficult. "you must provide a way to relink against the library".
Moreover, modifications that are need in some cases when integrating the lib could be difficult to put public for private companies. That could include more minor modifications as simple as building with different flags, fixing some warnings.. all of those are not necessarily useful for the bigger audience + again difficult to put public.
Apache2 solves point 1, MIT both.
Many useful libraries like this one have permissive licenses, and still get contributions from people.
That being said, as a contributor and maintainer, the choice is up to you of course ! I was just lead to believe that you agreed on that in the last issue.
from orocos_kinematics_dynamics.
from orocos_kinematics_dynamics.
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
from orocos_kinematics_dynamics.
from orocos_kinematics_dynamics.
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
from orocos_kinematics_dynamics.
I agree!
from orocos_kinematics_dynamics.
I agree.
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
@MatthijsBurgh any news on this ?
from orocos_kinematics_dynamics.
@ahoarau I am sorry, but I can not agree with a change to MIT or apache 2.0.
As statically linking is your biggest issue, I suggest the Mozilla Public License. I would agree with a change to that one. It still requires the user to disclose the source code, when distributing, but it doesn't require compatibility to the original version of the library, So it allows for static linking.
Comparison: https://softwareengineering.stackexchange.com/questions/221365/mozilla-public-license-mpl-2-0-vs-lesser-gnu-general-public-license-lgpl-3-0
from orocos_kinematics_dynamics.
@MatthijsBurgh thanks for your feedback. I understand your point of view.
I'm ok with this compromise as well. Probably a simple "patch" on the LGPL could be enough. Something like "LGPL + authorize static linking exception". That might simplify this (long) process.
What do you think ?
from orocos_kinematics_dynamics.
Yes, such a simple patch would also be an option. The question is how we do this correctly?
from orocos_kinematics_dynamics.
Yes, such a simple patch would also be an option. The question is how we do this correctly?
https://spdx.org/licenses/LGPL-3.0-linking-exception.html
Some like this would be enough I believe. Added to the repo.
from orocos_kinematics_dynamics.
I agree.
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
@ahoarau you still want to migrate to lgpl 3.0 with the linking exception?
As mentioned before, I agree with it.
Absolutely. Linking exception, MIT or BSD. Everything that makes life easier, I believe everyone is up for it.
Can you do the commit to upload the linking exception ?
from orocos_kinematics_dynamics.
@ahoarau I can do the commit, can you do the bookkeeping, whether everyone agrees? The list above is not complete yet.
from orocos_kinematics_dynamics.
@ahoarau I can do the commit, can you do the bookkeeping, whether everyone agrees? The list above is not complete yet.
Thanks. I believe some accounts are not used anymore, so it's gonna be difficult to keep track of everyone outside Github, but let's give it a last try:
@DjoleMNE @tdelaet @francisco-miguel-almeida @morxa @aballier @jbohren-hbr @martiniil @spencerjackson @rethink-kmaroney @mcopejans @gborghesan @seanyen
Please note that linking exception won't affect fundamentally the meaning of the license, it's a simple made-for-people-building-code extension.
from orocos_kinematics_dynamics.
I agree
from orocos_kinematics_dynamics.
from orocos_kinematics_dynamics.
from orocos_kinematics_dynamics.
Related Issues (20)
- AddressSanitizer throws errors HOT 3
- Compile issue of python bindings HOT 10
- Question about the computational performance of KDL on redundant kinematic chains HOT 4
- Joint Limits on Inverse Kinematic solver HOT 1
- Python Version Error HOT 6
- Website Documentation Wrong
- Installing KDL with python bindings on macos when building from source HOT 1
- Scaling of RigidBodyInertia values HOT 3
- ImportError: dynamic module does not define module export function (PyInit_PyKDL) HOT 14
- compiling eigen not found HOT 2
- CMake error of SET(KDL_CFLAGS "${KDL_CFLAGS} -I${EIGEN3_INCLUDE_DIR}") HOT 2
- Cmake Build Error HOT 2
- Path_RoundedComposite::Clone() doesn't copy F_base_start and F_base_via HOT 2
- compilation error HOT 2
- Bump version in master branch after release
- Frame composition does nothing. HOT 1
- Gravity Compensation with PyKDL always gives Zero HOT 2
- Problem with path_line trajectory, C code, bad quaternions in trajectory
- Build error on OpenBSD HOT 3
- Question about the JntToCoriolis function
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from orocos_kinematics_dynamics.