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.

Sign up for GitHub

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

Jump to bottom

Should we move to the MIT license? #100

Open
MerlinEgalite opened this issue Apr 23, 2023 · 5 comments
Open

Should we move to the MIT license? #100

MerlinEgalite opened this issue Apr 23, 2023 · 5 comments
Labels
🧐 question Further information is requested

Comments

@MerlinEgalite
Copy link
Contributor

No description provided.

@MerlinEgalite MerlinEgalite added the 🧐 question Further information is requested label Apr 23, 2023
@MerlinEgalite MerlinEgalite changed the title Should we move to the MIT license Should we move to the MIT license? Apr 23, 2023
@MathisGD
Copy link
Contributor

MathisGD commented Apr 28, 2023 •
edited
Loading

I don't see any big deal with the current licence (AGPL 3), but neither with MIT.

For reference solmate is under AGPL 3 and OZ contracts is under MIT.

@MerlinEgalite
Copy link
Contributor Author

MerlinEgalite commented Apr 28, 2023 •
edited
Loading

what's dommage?

AGPL v3 prevents companies that distribute proprietary code to use it because it would require to open source their code. So AGPL v3 is a limiting the usage of the code we ship which can be a good or a bad thing.

@MathisGD
Copy link
Contributor

edited lol

@MerlinEgalite
Copy link
Contributor Author

So on my side I think that MIT is better

@MathisGD
Copy link
Contributor

Ok for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🧐 question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MerlinEgalite @MathisGD