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

License Change Consent (from MIT to LGPL-3.0 or later) #601

Closed
EliteAsian123 opened this issue Nov 21, 2023 · 32 comments
Closed

License Change Consent (from MIT to LGPL-3.0 or later) #601

EliteAsian123 opened this issue Nov 21, 2023 · 32 comments

Comments

@EliteAsian123
Copy link
Member

EliteAsian123 commented Nov 21, 2023

YARG will soon be changing it's license from MIT to LGPL-3.0 (or any version later)

LGPL is a more restrictive license compared to MIT, however it's fully compatible. See details here.

Before proceeding with this license update, we want to ensure that we have your consent. If you are in agreement with the proposed change, please reply to this message with your approval. If you have any concerns or objections, we value your feedback and would be happy to discuss further.

Your understanding and cooperation are highly appreciated as we work towards the continued growth of YARG. Thank you for your ongoing support!

Why?

Some of the reasons are: LGPL requires that any modified version of the software (in this case, YARG), must also have their source code published as LGPL. LGPL also has provisions related to patents, which prevents (to an extent) the use of patents to restrict the use of the software (please read the LGPL license for more details regarding these things if interested), among other things.

Will this affect any plans with the project, or any libraries?

Nope. LGPL will still allow us to do things such as close-sourcing certain parts of the project (such as anti-cheat), and will still allow use to use libraries with proprietary licenses (such as BASS).

Who?

95% (which in this case is 33/34 listed) of everyone who has made code and art contributions to YARG must give consent. Grammatical changes in various markdown files have been excluded. Those people are as follows:

Any objections from these people will be worked out before this change is made. Thanks for your contributions and understanding.

TL;DR

Please give approval below of whether you not you consent of YARG changing licenses from MIT to LGPL-3.0 (or any version later) if you have been mentioned above.

@Pantotone
Copy link
Member

LGTM! 👍

@EscapeNumber001
Copy link
Contributor

I consent to this change.

@santorfo
Copy link
Contributor

All good from me 👌

@TheNathannator
Copy link
Collaborator

I fully endorse this change 👍

@jnackmclain
Copy link
Contributor

You have my approval

@NarrikSynthfox
Copy link
Contributor

Sounds good to me

@vcinventerman
Copy link
Contributor

All good with me 👍

@raphaelgoulart
Copy link
Contributor

I consent to this change.

@pul53gh
Copy link
Contributor

pul53gh commented Nov 21, 2023 via email

@PixelatedPope
Copy link
Contributor

PixelatedPope commented Nov 21, 2023 via email

@RileyTheFox
Copy link
Collaborator

I consent to this change!

@SamuelPalma
Copy link
Contributor

SamuelPalma commented Nov 21, 2023 via email

@grishhung
Copy link
Contributor

grishhung commented Nov 21, 2023 via email

@exoticri
Copy link
Contributor

I consent to this change

@PikminGuts92
Copy link
Contributor

I consent to the license change 👍

@eckerj
Copy link
Contributor

eckerj commented Nov 21, 2023

Good for me :-)

@TheFatBastid
Copy link
Contributor

I consent to this change. Rock on!

@muskit
Copy link
Contributor

muskit commented Nov 21, 2023

I consent to the license change.

2 similar comments
@kaduwaengertner
Copy link
Member

I consent to the license change.

@nevespt
Copy link
Contributor

nevespt commented Nov 21, 2023

I consent to the license change.

@sonicfind
Copy link
Collaborator

Cracks knuckles
image

@LlysiX
Copy link
Contributor

LlysiX commented Nov 21, 2023

sounds good to me bossman

@NicolasPL64
Copy link
Contributor

Sure thing! I consent

@LocalH
Copy link
Contributor

LocalH commented Nov 21, 2023

Fine with me

@Roystermeat
Copy link
Contributor

Roystermeat commented Nov 21, 2023 via email

@zigguy
Copy link
Contributor

zigguy commented Nov 21, 2023

I consent

@ieee802dot11ac
Copy link
Contributor

ieee802dot11ac commented Nov 23, 2023 via email

@NyxTheShield
Copy link
Contributor

I consent!

@rjkiv
Copy link
Contributor

rjkiv commented Nov 24, 2023

👍🏻

@InvoxiPlayGames
Copy link
Contributor

awesome change, i consent

@JayDiddyThaGOAT
Copy link
Contributor

I consent to this change!

@thoudankeykang
Copy link
Contributor

although permission isn't required from me, i still do consent

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