Git Product home page Git Product logo

Comments (28)

finitespace avatar finitespace commented on August 22, 2024 3

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.

from bme280.

Amunak avatar Amunak commented on August 22, 2024 1

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

from bme280.

finitespace avatar finitespace commented on August 22, 2024

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

How would you feel about a license change?

from bme280.

per1234 avatar per1234 commented on August 22, 2024

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

from bme280.

HappyWheels avatar HappyWheels commented on August 22, 2024

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

from bme280.

AmedeeBulle avatar AmedeeBulle commented on August 22, 2024

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

from bme280.

guruathwal avatar guruathwal commented on August 22, 2024

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

from bme280.

vortigont avatar vortigont commented on August 22, 2024

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

from bme280.

maru-sama avatar maru-sama commented on August 22, 2024

This is OK for me too.

from bme280.

eykamp avatar eykamp commented on August 22, 2024

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.

from bme280.

jirkaptr avatar jirkaptr commented on August 22, 2024

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

from bme280.

coelner avatar coelner commented on August 22, 2024

So far (myself included)

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

from bme280.

chacal avatar chacal commented on August 22, 2024

Fine by me! 👍

from bme280.

alexshavlovsky avatar alexshavlovsky commented on August 22, 2024

from bme280.

osos avatar osos commented on August 22, 2024

Fine with me.

from bme280.

rpaskowitz avatar rpaskowitz commented on August 22, 2024

Either LGPL or MIT are good with me.

from bme280.

tinxx avatar tinxx commented on August 22, 2024

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

from bme280.

chacal avatar chacal commented on August 22, 2024

All licenses are fine for me!

from bme280.

osos avatar osos commented on August 22, 2024

I am OK with any license.

from bme280.

vortigont avatar vortigont commented on August 22, 2024

I'm also OK with any license.
Cheers!

from bme280.

coelner avatar coelner commented on August 22, 2024

LGPL or MIT are fine.

from bme280.

jirkaptr avatar jirkaptr commented on August 22, 2024

All licenses are fine for me.

from bme280.

finitespace avatar finitespace commented on August 22, 2024

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.

from bme280.

tinxx avatar tinxx commented on August 22, 2024

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

from bme280.

tinxx avatar tinxx commented on August 22, 2024

Hey @finitespace, any news?

from bme280.

finitespace avatar finitespace commented on August 22, 2024

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

from bme280.

tinxx avatar tinxx commented on August 22, 2024

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

from bme280.

tinxx avatar tinxx commented on August 22, 2024

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

from bme280.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.