Skip to content
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

Change license to a more permissive one #410

Open
35 of 45 tasks
ahoarau opened this issue Sep 1, 2022 · 48 comments
Open
35 of 45 tasks

Change license to a more permissive one #410

ahoarau opened this issue Sep 1, 2022 · 48 comments

Comments

@ahoarau
Copy link
Contributor

ahoarau commented Sep 1, 2022

Hello KDL contributors,

This follow the discussion that happened here: #405

As discussed with @smits and @MatthijsBurgh, they are both ok to change the license to a more permissive one. MIT seems to be the most appropriate (apache-2.0 was considered at first).

To make the change, we need the consent of every contributors to make the change from LGPL-v2 to MIT.
This will ease proprietary code development, allowing some modifications and static linking.

You can simply respond with "I agree".

Thanks !

NOTE: as a contributor myself, I agree !

@morxa
Copy link
Contributor

morxa commented Sep 1, 2022

I agree

2 similar comments
@traversaro
Copy link
Contributor

I agree

@Tobias-Fischer
Copy link
Contributor

I agree

@vbargsten
Copy link

vbargsten commented Sep 1, 2022 via email

@mag-sruehl
Copy link
Contributor

I agree

1 similar comment
@mvieth
Copy link
Contributor

mvieth commented Sep 1, 2022

I agree

@dvanthienen
Copy link

dvanthienen commented Sep 1, 2022 via email

@jspricke
Copy link
Contributor

jspricke commented Sep 1, 2022

I agree

2 similar comments
@ipa-pgt
Copy link

ipa-pgt commented Sep 1, 2022

I agree

@mvistein
Copy link
Contributor

mvistein commented Sep 1, 2022

I agree

@MatthijsBurgh
Copy link
Collaborator

@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.

@ahoarau
Copy link
Contributor Author

ahoarau commented Sep 1, 2022

@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.

@jensenb
Copy link
Contributor

jensenb commented Sep 1, 2022 via email

@MatthijsBurgh
Copy link
Collaborator

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.

@JohnSilverFarmer
Copy link
Contributor

JohnSilverFarmer commented Sep 1, 2022 via email

@meyerj
Copy link
Member

meyerj commented Sep 1, 2022

I agree

@jspricke
Copy link
Contributor

jspricke commented Sep 1, 2022 via email

@milutter
Copy link
Contributor

milutter commented Sep 1, 2022

I agree

@maverick-long
Copy link
Contributor

maverick-long commented Sep 1, 2022 via email

@snrkiwi
Copy link
Contributor

snrkiwi commented Sep 1, 2022 via email

@psoetens
Copy link

psoetens commented Sep 1, 2022 via email

@luzpaz
Copy link
Contributor

luzpaz commented Sep 1, 2022

I agree

@eaertbel
Copy link
Contributor

eaertbel commented Sep 1, 2022 via email

@ivanpauno
Copy link
Contributor

I agree

5 similar comments
@sloretz
Copy link
Contributor

sloretz commented Sep 1, 2022

I agree

@jacobperron
Copy link
Contributor

I agree

@francesco-romano
Copy link
Contributor

I agree

@wb459
Copy link

wb459 commented Sep 1, 2022

I agree

@tfoote
Copy link
Contributor

tfoote commented Sep 1, 2022

I agree

@forrest-rm
Copy link

forrest-rm commented Oct 11, 2022 via email

@jbohren
Copy link
Contributor

jbohren commented Oct 12, 2022

I agree!

@dirk-thomas
Copy link
Contributor

I agree.

@mikepurvis
Copy link
Contributor

I agree

@ahoarau
Copy link
Contributor Author

ahoarau commented Dec 19, 2022

@MatthijsBurgh any news on this ?

@MatthijsBurgh
Copy link
Collaborator

@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

@ahoarau
Copy link
Contributor Author

ahoarau commented Dec 20, 2022

@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 ?

@MatthijsBurgh
Copy link
Collaborator

Yes, such a simple patch would also be an option. The question is how we do this correctly?

@ahoarau
Copy link
Contributor Author

ahoarau commented Dec 22, 2022

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.

@zchen24
Copy link
Contributor

zchen24 commented Dec 31, 2022

I agree.

@jf---
Copy link
Contributor

jf--- commented Jan 2, 2023

I agree

1 similar comment
@mikepurvis
Copy link
Contributor

I agree

@MatthijsBurgh
Copy link
Collaborator

@ahoarau you still want to migrate to lgpl 3.0 with the linking exception?

As mentioned before, I agree with it.

@ahoarau
Copy link
Contributor Author

ahoarau commented Feb 28, 2024

@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 ?

@MatthijsBurgh
Copy link
Collaborator

MatthijsBurgh commented Feb 28, 2024

@ahoarau I can do the commit, can you do the bookkeeping, whether everyone agrees? The list above is not complete yet.

@ahoarau
Copy link
Contributor Author

ahoarau commented Feb 28, 2024

@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.

@ahoarau ahoarau changed the title Change license to MIT Change license to a more permissive one Feb 28, 2024
@morxa
Copy link
Contributor

morxa commented Feb 28, 2024

I agree

@dvanthienen
Copy link

dvanthienen commented Feb 28, 2024 via email

@gborghesan
Copy link

gborghesan commented Feb 29, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests