Skip to content

Update LICENSE to allow closed-source apps to be made using PyPositron #8

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

itzmetanjim
Copy link
Owner

@itzmetanjim itzmetanjim commented Jul 16, 2025

Description

[Closes #7 : Change the license to something else so that closed source projects can be made using PyPositron]
The previous license, GNU AGPL v3, would not allow any projects made using this framework to be closed source.

Type of change

  • Other: License change

Solution

To allow open source projects to be made using PyPositron, the two best options are using GNU LGPLv3 , Apache License 2.0 or MIT License instead of the current AGPLv3 license. I think the MIT license is better as its more permissive and won't require any closed source project made using PyPositron to:

  • provide relinking materials , unlike LGPL
  • state changes when the library is modified, unlike Apache 2.0.

The MIT license is also more common and simpler than Apache 2.0, LGPL or AGPL.

HOWEVER, I can not commit this directly as I need to get the permission of all previous contributors ( @wyattferguson and @Bubbl33s ) to relicense their contributions.

If you contributed to PyPositron and agree to have your contributions MIT-licensed, include the following statement on a comment:

I, [Your full name or github username], hereby irrevocably agree to give permission to re-license all my past and present contributions to [PyPositron](https://github.com/itzmetanjim/py-positron/), including but not limited to code, comments, documentation, refactoring changes, and any other creative works I have contributed to the project, under the MIT License, as provided and referenced in this pull request. I affirm that I have the necessary rights to grant this re-licensing.

(This does not mean that it has to be only MIT-licensed if we later decide to use Apache 2.0)
If you don't want the project (or your contributions specifically) to be MIT-licensed (perfectly fine!), comment why and what other license to use instead (not including the above statement in your comment).

@wyattferguson , @Bubbl33s and any other contributors: Please read the PR description and agree or disagree to the re-licensing.

@itzmetanjim
Copy link
Owner Author

I also have to agree, so:
I, Tanjim Kamal (itzmetanjim) hereby irrevocably agree to re-license all my past and present contributions to PyPositron, including but not limited to code, comments, documentation, refactoring changes, and any other creative works I have contributed to the project, under the MIT License, as provided and referenced in this pull request. I affirm that I have the necessary rights to grant this re-licensing.

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

Successfully merging this pull request may close these issues.

Change the license to something else so that closed source projects can be made using PyPositron
1 participant