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

Relicensing Lethe #1145

Open
blaisb opened this issue May 16, 2024 · 29 comments
Open

Relicensing Lethe #1145

blaisb opened this issue May 16, 2024 · 29 comments

Comments

@blaisb
Copy link
Contributor

blaisb commented May 16, 2024

During this week's Hackathon we discussed relicensing for Lethe in order to increase the flexibility of our license and also to remain coherent with the license that is used by deal.II.

Deal.II uses a dual license under: Apache-2.0 WITH LLVM-exception OR LGPL-2.1-or-later
I propose we use the same license.

One of the main target of this issue is to gather an OK from every past and present contributers (meaning anyone that has ever commited a file or a change to Lethe).

@AmishgaAlphonius
@shahabgol
@oguevremont
@Luckabarbeau
@voferreira
@CaroleAnneDaunais
@acdaigneault
@jeannejoachim
@OGaboriault
@hepap
@tonielgeitani
@paulapatience
@PierreLaurentinCS
@ghazalemir
@technophil98
@SGauvin
@bibeauv
@mivaia
@emilebergeron
@cenr20
@OresteMarquis
@charles-lp
@Wendi-L
@Clara-Haydar
@maxl-1
@Wieb-ke
@anicusan
@EduardsBlandin
@yashuuzi
@kronbichler
@bangerth
@Raju1231

@peterrum
Copy link
Collaborator

gather an OK from every past and present contributers.

OK from my side 👍

@paulapatience
Copy link
Collaborator

OK for me too.

@lpsaavedra
Copy link
Collaborator

OK

@bangerth
Copy link
Contributor

I don't even remember contributing, but of course it's ok with me :-)

@blaisb
Copy link
Contributor Author

blaisb commented May 16, 2024

I don't even remember contributing, but of course it's ok with me :-)

You did, you fixed a few typos in the README.md file 4 years ago. Everybody's equal, it needs to be fair :)

@voferreira
Copy link
Collaborator

Ok

@CaroleAnneDaunais
Copy link
Collaborator

Ok ✌

@shahabgol
Copy link
Contributor

shahabgol commented May 16, 2024 via email

@anicusan
Copy link
Contributor

Thanks for including me as a contributor - of course, very happy with the relicensing!

@OresteMarquis
Copy link
Collaborator

Ok :)

1 similar comment
@ghazalemir
Copy link
Collaborator

Ok :)

@oguevremont
Copy link
Collaborator

Ok!

1 similar comment
@acdaigneault
Copy link
Collaborator

Ok!

@kronbichler
Copy link
Collaborator

Ok

1 similar comment
@OGaboriault
Copy link
Collaborator

Ok

@bangerth
Copy link
Contributor

bangerth commented May 16, 2024 via email

@OGaboriault OGaboriault reopened this May 16, 2024
@Luckabarbeau
Copy link
Collaborator

Ok !

@yashuuzi
Copy link
Collaborator

Ok!

@AmishgaAlphonius
Copy link
Collaborator

Ok :)

@Wieb-ke
Copy link
Collaborator

Wieb-ke commented May 16, 2024

ok

@PierreLaurentinCS
Copy link
Collaborator

Ok for me !

@charles-lp
Copy link
Contributor

Ok for me as well!

@tonielgeitani
Copy link
Collaborator

tonielgeitani commented May 17, 2024 via email

@Clara-Haydar
Copy link
Contributor

Clara-Haydar commented May 17, 2024 via email

@Wendi-L
Copy link
Contributor

Wendi-L commented May 17, 2024

Many thanks for including me as a contributor. I fully support the relicensing.

@hepap
Copy link
Collaborator

hepap commented May 17, 2024

Ok for me :)

@jeannejoachim
Copy link
Contributor

jeannejoachim commented May 17, 2024 via email

@mivaia
Copy link
Collaborator

mivaia commented May 17, 2024

Ok for me!

@SGauvin
Copy link
Contributor

SGauvin commented May 18, 2024

Ok from my side 👋

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