chore: switch to GPLv3 license #178
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Yes, I am fine with moving to GPLv3. Thank you! |
Contributor
|
Yes fine for me! I support 😄 |
Contributor
|
Fine by me!On 19 Jan 2026, at 09:47, Toon (Anton) ***@***.***> wrote:toonvank left a comment (markbeep/AudioBookRequest#178)
Yes fine for me! I support 😄
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the project having gained in traction, I want to move from the MIT license to the GPLv3 license. The main idea is that any forks of ABR will then also need to be open-sourced (if it's being distributed), which I find is important, especially for selfhosted tools.
Nice summary of what the GPLv3 license is: https://gist.github.com/kn9ts/cbe95340d29fc1aaeaa5dd5c059d2e60
For that I need a clear "Yes" or "No" from all contributors whether they're okay with changing the license.
@leandrocoding @toonvank @mtthidoteu @vicegold