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

Propose License Change to LGPL/MIT #118

Open
tinxx opened this issue Dec 30, 2020 · 28 comments
Open

Propose License Change to LGPL/MIT #118

tinxx opened this issue Dec 30, 2020 · 28 comments
Assignees
Milestone

Comments

@tinxx
Copy link

tinxx commented Dec 30, 2020

Hello,
First-off let me say thanks for the work you put into creating this library.

I was looking through the libraries I include in my current project and had to realize that this library would force me to release my code under GPL, too. I don't say that GPL is a bad licence, actually I believe the opposite.

Anyhow, I suggest a license change to LGPL to make it easier for people to integrate the library into projects licensed differently.

Cheers,
tinxx

@finitespace
Copy link
Owner

finitespace commented Feb 26, 2021

Hi @tinxx

I would prefer it to go to MIT, but I would need buy off from the contributors.

If you can take the time to get everyone on board, I am happy to change.

@finitespace
Copy link
Owner

@finitespace finitespace self-assigned this Feb 26, 2021
@finitespace finitespace added this to the Version_4.0.0 milestone Feb 26, 2021
@per1234
Copy link
Contributor

per1234 commented Feb 26, 2021

@finitespace you have my permission to do anything you want with my insignificant contribution.

@HappyWheels
Copy link
Contributor

@finitespace You have my permission to change the license as you see fit.

@AmedeeBulle
Copy link
Contributor

I support the change to a less restrictive license (LGPL or other).

While GPL is in general a good thing, delivering a library under GPL is quite restrictive as it is not compatible with most of the other open source licenses libraries you might want/need to include in your project.
(In fact I am not using this library for some of my projects just because of a license conflict with other libs...)

@guruathwal
Copy link
Contributor

@finitespace I do not have any objection to changing the licence to any other type.

@Amunak
Copy link
Contributor

Amunak commented Feb 26, 2021

I'm all for it, sure; feel free to license my one-word contribution under any license you wish, now and in the future. ;)

@vortigont
Copy link
Contributor

I'm OK! LGPL might be more suitable for a lib in some cases, so be it :)

@maru-sama
Copy link
Contributor

This is OK for me too.

@eykamp
Copy link
Contributor

eykamp commented Feb 26, 2021

I think the LGPL would be preferable to the GPL, but I think MIT or similar would be even better for a library.

But regardless, I consent to this change.

@jirkaptr
Copy link
Contributor

@finitespace, I don't have a problem with that.

@coelner
Copy link
Contributor

coelner commented Feb 27, 2021

So far (myself included)

  • coelner
  • jirkaptr
  • klagr
  • HappyWheels
  • chacal
  • guruathwal
  • alexshavlovsky
  • johanso-au
  • rpaskowitz
  • eykamp
  • jamesmyatt
  • vortigont
  • osos
  • per1234
  • maru-sama
  • AmedeeBulle
  • Amunak

@chacal
Copy link
Contributor

chacal commented Feb 27, 2021

Fine by me! 👍

@alexshavlovsky
Copy link
Contributor

alexshavlovsky commented Feb 28, 2021 via email

@osos
Copy link
Contributor

osos commented Mar 1, 2021

Fine with me.

@rpaskowitz
Copy link
Contributor

Either LGPL or MIT are good with me.

@tinxx
Copy link
Author

tinxx commented Mar 29, 2021

Hey folks,
Let me summarize the current state of the license change proposal:

I initially proposed LGPL as the new license because the original license was GPL.
@finitespace, however, is the main author and proposed MIT as the new license.
MIT would be even more permissive and would enable the library to be used more easily and extensively.

Now there are some unclear and missing statements from contributors that I would like to get cleared up.

Unclear Contributors

I would like to ask the following contributors to clarify their decisions:

Do you support either MIT, LGPL, both or basically any license?

  • vortigont, you signalled you are OK with LGPL. Are you OK with MIT license, too?

OK Contributors (LGPL + MIT)

The following contributors gave their OK for both LGPL and MIT licenses (or any license):

  • alexshavlovsky
  • AmedeeBulle
  • Amunak
  • chacal
  • coelner
  • eykamp
  • guruathwal
  • HappyWheels
  • jirkaptr
  • osos
  • per1234
  • rpaskowitz
  • vortigont

Other Contributors

  • @johanso-au has so far not been heard from.
  • @yanbec has not been mentioned here so far. However I found his name on: BME280.h (165-168, 253-255, 315); BME280.cpp (154-161)

@johanso-au, @yanbec, please tell us if you are OK with a license change to MIT and/or LGPL license?


Sorry for the inconvenience!
--Tinxx

@chacal
Copy link
Contributor

chacal commented Mar 29, 2021

All licenses are fine for me!

@osos
Copy link
Contributor

osos commented Mar 29, 2021

I am OK with any license.

@vortigont
Copy link
Contributor

I'm also OK with any license.
Cheers!

@coelner
Copy link
Contributor

coelner commented Mar 30, 2021

LGPL or MIT are fine.

@jirkaptr
Copy link
Contributor

All licenses are fine for me.

@finitespace
Copy link
Owner

finitespace commented Apr 17, 2021

Alright, it looks like we have a quorum! I am going to assume anyone who has not already spoke up has abandoned their account - so speak up now or forever hold your silence.

For the remaining unspoken - I will take your silence as consent

Would someone volunteer to create a new merge request @coelner @tinxx? I would personally like to change it to MIT.

@tinxx tinxx changed the title Propose License Change to LGPL Propose License Change to LGPL/MIT Apr 23, 2021
tinxx added a commit to tinxx/BME280 that referenced this issue Apr 23, 2021
tinxx added a commit to tinxx/BME280 that referenced this issue Apr 23, 2021
tinxx added a commit to tinxx/BME280 that referenced this issue Apr 23, 2021
@tinxx
Copy link
Author

tinxx commented Apr 23, 2021

Hi @finitespace,

I have created a PR changing all license annotations to Copyright (c) 2015-2021 Tyler Glenn, et al..
Where there were explicit mentions of other contributors (Forked by Alex Shavlovsky), I have also added the person to the Copyright notice.

Cheers!
Tinxx

@tinxx
Copy link
Author

tinxx commented Jun 4, 2021

Hey @finitespace, any news?

@finitespace
Copy link
Owner

finitespace commented Jul 26, 2021

Thank you, @tinxx. That was an excellent pull request, are you looking for work? ;) A few minor comments, let me know your thoughts,

Kind regards, and sorry for the delay,
@finitespace

tinxx added a commit to tinxx/BME280 that referenced this issue Aug 18, 2021
@tinxx
Copy link
Author

tinxx commented Aug 18, 2021

Hey @finitespace,

Thank you for the warm response.

I have pushed the amendments according to your comments. I hope this is to your satisfaction ;)

You can always contact me privately with a job offer ;)

Cheers!
@tinxx

@tinxx
Copy link
Author

tinxx commented Feb 5, 2022

Bump! Please re-visit the Merge Request! Thanks!

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

No branches or pull requests