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

relicense from AGPL to MIT #172

Open
17 of 19 tasks
daroczig opened this issue Aug 4, 2024 · 18 comments
Open
17 of 19 tasks

relicense from AGPL to MIT #172

daroczig opened this issue Aug 4, 2024 · 18 comments

Comments

@daroczig
Copy link
Owner

daroczig commented Aug 4, 2024

Although I thought (10+ years ago) that AGPL-3 effectively addressed the potential issue of SaaS companies taking advantage of open-source software without contributing back, the licensing terms seem to be confusing and interpreted differently by orgs and lawyers. Given the multiple requests from the past years I've received to relicense to a more permissive license, and my current belief that logger does not benefit from the restrictions of AGPL -- I am hereby starting the relicensing process to MIT.

To do so, I need approval from all copyright holders (past contributors):

I know this is painful and boring, but the relicensing can only happen if I get acceptance from everyone, so please kindly reply below stating:

I accept the change of logger's license to MIT.

Otherwise, please feel free to let me know your concerns, questions etc.

Thanks for your past contributions and your help in this process as well!

@MichaelChirico
Copy link
Contributor

I accept the change of logger's license to MIT.

Thank you for this, I can attest that google has a by-strict-exception-only policy for AGPL third party code: https://opensource.google/documentation/reference/using/agpl-policy

@burgikukac
Copy link
Contributor

I accept the change of logger's license to MIT.

1 similar comment
@tdeenes
Copy link
Contributor

tdeenes commented Aug 4, 2024

I accept the change of logger's license to MIT.

@aaelony
Copy link
Contributor

aaelony commented Aug 4, 2024 via email

@atheriel
Copy link
Contributor

atheriel commented Aug 5, 2024

I accept the change of logger's license to MIT.

In the past I've cited the AGPL as a reason to avoid this package for corporate Shiny apps, so happy to see it change. R community norms are strongly in favour of folks contributing back regardless of license, too.

@hadley
Copy link
Collaborator

hadley commented Aug 5, 2024

Approved!

@DanChaltiel
Copy link
Contributor

I accept the change of logger's license to MIT.

3 similar comments
@pawelru
Copy link
Contributor

pawelru commented Aug 5, 2024

I accept the change of logger's license to MIT.

@philaris
Copy link
Contributor

philaris commented Aug 5, 2024

I accept the change of logger's license to MIT.

@stPhena
Copy link
Contributor

stPhena commented Aug 5, 2024

I accept the change of logger's license to MIT.

@Polkas
Copy link
Contributor

Polkas commented Aug 5, 2024

@daroczig thank you for your contributions, and I am happy to see you more in open source world now:)

I accept the change of logger's license to MIT.

@kpagacz
Copy link
Contributor

kpagacz commented Aug 5, 2024

Nicely done :)

I accept the change of logger's license to MIT.

@jozefhajnala
Copy link
Contributor

jozefhajnala commented Aug 5, 2024 via email

@artemklevtsov
Copy link
Contributor

I accept the change of logger's license to MIT.

@deeenes
Copy link
Contributor

deeenes commented Aug 5, 2024

Fine by me! :)

@averissimo
Copy link
Contributor

I accept the change of logger's license to MIT.

@daroczig
Copy link
Owner Author

@amy17519 @earino @terashim could you please provide feedback on the above-mentioned license change?

@earino
Copy link
Contributor

earino commented Aug 18, 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