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

Re-license under the MIT + Apache 2.0 license #165

Closed
29 tasks done
orhun opened this issue May 1, 2023 · 33 comments · Fixed by #303
Closed
29 tasks done

Re-license under the MIT + Apache 2.0 license #165

orhun opened this issue May 1, 2023 · 33 comments · Fixed by #303
Labels
license License-related matters

Comments

@orhun
Copy link
Owner

orhun commented May 1, 2023 •
edited
Loading

To all the contributors of git-cliff! ⛰

I hope you're doing well. I'm reaching out to discuss a potential change in licensing for the project.

Currently, the project is licensed under GPL3, which has certain restrictions on distribution and usage.

I believe that a re-licensing to MIT + Apache 2.0 license will provide several benefits to both the project and its users:

  • Greater flexibility in terms of usage, distribution, and modification of the codebase.
  • Compatibility with a wider range of software licenses, making it easier for other developers to incorporate or build upon the project.
  • Reduced legal barriers to adoption by companies and organizations that have policies against using or contributing to GPL3-licensed projects.
  • Improved accessibility to potential contributors who may be hesitant to contribute to a project with a more restrictive license.
  • The adoption of widely recognized and accepted licenses will provide greater legal certainty and protection to users and contributors alike.

This is also the license of choice for the Rust project itself and you can read more about their reasoning here.

The re-licensing can only be done if all of the below authors consent to re-licensing their work under the terms of the MIT and Apache 2.0 license or if their contributions are removed.

The authors of the project have been derived using git log --all --format='%aN <%aE>' | sort -u:

Aaron Friel <[email protected]>
alteregoart <[email protected]>
bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Cassandra McCarthy <[email protected]>
dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Eliza Weisman <[email protected]>
Florian Fromm <[email protected]>
Grachev Mikhail <[email protected]>
Herby Gillot <[email protected]>
Jan Katins <[email protected]>
Jeroen Claassens <[email protected]>
Kaushal Modi <[email protected]>
Kenji Miyake <[email protected]>
Lygon Bowen-West <[email protected]>
Mack Solomon <[email protected]>
Marcin Puc <[email protected]>
Marco Ieni <[email protected]>
Matt Foxx <[email protected]>
Ömer Faruk Şahin <[email protected]>
orhun <[email protected]>
Orhun Parmaksız <[email protected]>
Pascal Bach <[email protected]>
pataar <[email protected]>
Radu Suciu <[email protected]>
Sayafdine Said <[email protected]>
Sebastian Müller <[email protected]>
Steven L <[email protected]>
Taylan Dogan <[email protected]>
Tonye Jack <[email protected]>
Uy Ha <[email protected]>

For convenience, all users with a GitHub account have been added to the below list of checkboxes:

The list of contributors is derived using curl -s https://api.github.com/repos/orhun/git-cliff/contributors | jq -r .[].login | xargs -I {} echo "- [ ] @{}"

Please leave a comment to this issue stating that you consent to the license change or indicate your objection if you do not agree with the new license terms. For example:

  • ✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.
  • ❌ I object to the proposed license change and do not consent to my work on git-cliff being licensed under either the MIT or Apache 2.0 license.

Thank you for your contributions to the project and your attention to the matter! 🐻
@orhun orhun added the license License-related matters label May 1, 2023
@pataar
Copy link
Contributor

pataar commented May 1, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

1 similar comment
@uyha
Copy link
Contributor

uyha commented May 1, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@tranzystorekk
Copy link
Contributor

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@radusuciu
Copy link
Contributor

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

1 similar comment
@MarcoIeni
Copy link
Contributor

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@herbygillot
Copy link
Contributor

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@favna
Copy link
Contributor

favna commented May 1, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

Sidenote, I didn't even know it was possible to combine 2 licenses like that. TIL.

@hawkw
Copy link
Contributor

hawkw commented May 1, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@7596ff
Copy link
Contributor

7596ff commented May 1, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

5 similar comments
@saidsay-so
Copy link
Contributor

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@FlrnFrmm
Copy link
Contributor

FlrnFrmm commented May 1, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@Groxx
Copy link
Contributor

Groxx commented May 1, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@kaushalmodi
Copy link
Contributor

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@AaronFriel
Copy link
Contributor

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@kenji-miyake
Copy link
Contributor

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

1 similar comment
@bachp
Copy link
Contributor

bachp commented May 1, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@jankatins
Copy link
Contributor

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

(I only removed a word from the readme, so I'm irrelevant for this)

@mgrachev
Copy link
Contributor

mgrachev commented May 2, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

2 similar comments
@jackton1
Copy link
Contributor

jackton1 commented May 2, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@sbmueller
Copy link
Contributor

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@alerque
Copy link
Contributor

alerque commented May 2, 2023

I didn't make the list above, but since I have a PR pending that was submitted under the original licensing I'll pre-empt that being an issue:

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@kondanta
Copy link
Contributor

kondanta commented May 3, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

This was referenced May 3, 2023
Merged
Merged
@beeb
Copy link
Contributor

beeb commented May 3, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@FoxxMD
Copy link
Contributor

FoxxMD commented May 3, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@mackness
Copy link
Contributor

mackness commented May 6, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

1 similar comment
@ofsahof
Copy link
Contributor

ofsahof commented May 29, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@PSeitz
Copy link
Contributor

PSeitz commented Jun 1, 2023

I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@alteregoart
Copy link
Contributor

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@orhun orhun mentioned this issue Jun 27, 2023
Merged
12 tasks
@tvcsantos
Copy link
Contributor

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@orhun orhun mentioned this issue Aug 24, 2023
Merged
12 tasks
@alexfertel
Copy link
Contributor

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@orhun orhun mentioned this issue Sep 8, 2023
Merged
12 tasks
@dnaka91
Copy link
Contributor

dnaka91 commented Sep 8, 2023

✅ I consent to my work on git-cliff to be licensed under the terms of the MIT or Apache 2.0 license.

@orhun orhun mentioned this issue Sep 19, 2023
Closed
joshka added a commit to joshka/git-cliff that referenced this issue Sep 23, 2023
@joshka
revert: feat(args): update clap and clap extras to v4 (orhun#137)
a18a41c 
This reverts commit 0e710c2.

This is to ensure that there is no GPL 3.0 code contributions left to
address orhun#165
@joshka joshka mentioned this issue Sep 23, 2023
Merged
12 tasks
orhun added a commit that referenced this issue Sep 30, 2023
@joshka @orhun
revert(args): update clap and clap extras to v4 (#137) (#292)
fb4c733 
This reverts commit 0e710c2.

This is to ensure that there is no GPL 3.0 code contributions left to
address #165

Co-authored-by: Orhun Parmaksız <[email protected]>
orhun added a commit that referenced this issue Sep 30, 2023
@joshka @orhun
chore: remove GPL code (#293)
e3606ba 
* revert: feat(args): update clap and clap extras to v4 (#137)

This reverts commit 0e710c2.

This is to ensure that there is no GPL 3.0 code contributions left to
address #165

* chore: update to clap 4.4.4

---------

Co-authored-by: Orhun Parmaksız <[email protected]>
@orhun
Copy link
Owner Author

orhun commented Sep 30, 2023

I couldn't reach out to @lbowenwest so his GPL contributions are removed in #292 and we rewrote the same functionality in #293

@orhun orhun mentioned this issue Sep 30, 2023
Merged
@joshka
Copy link
Contributor

joshka commented Sep 30, 2023

I consent to the 2 PRs that revert the leftover GPL code in #292 and then update the clap version in #293 to be relicensed under the MIT and/or Apache 2 license.

@orhun orhun mentioned this issue Sep 3, 2024
Closed
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
license License-related matters
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

docs(license): re-license under the MIT + Apache 2.0 license orhun/git-cliff