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

💡 Change license to AGPL #38

Closed
MarcusOtter opened this issue Jan 22, 2022 · 3 comments · Fixed by #34
Closed

💡 Change license to AGPL #38

MarcusOtter opened this issue Jan 22, 2022 · 3 comments · Fixed by #34
Assignees
Labels
improvement 💡 Improvement suggestion

Comments

@MarcusOtter
Copy link
Owner

Is your request for improvement related to a problem? Please describe.
From nchristopher#1079 on Discord:

Wouldn't it be more appropriate for Needle to be licensed under the AGPL rather than the GPL? The AGPL is identical to the GPL, with the added clause that it applies over networks (eg. Discord bots).

Currently, someone could fork Needle and host it, keeping their source private. Unless that was your intention, I think the AGPL would be a better choice.

I prefer that people keep the source code for Needle open when they make their own modifications, and in this case AGPL supports this better than GPL.

Describe the solution you'd like
Change to AGPL-3.0

Describe alternatives you've considered
N/A

Additional context
https://www.gnu.org/licenses/why-affero-gpl.html

This change will probably happen with v2.0.

@MarcusOtter MarcusOtter added the improvement 💡 Improvement suggestion label Jan 22, 2022
@MarcusOtter MarcusOtter self-assigned this Jan 22, 2022
@MarcusOtter MarcusOtter pinned this issue Jan 22, 2022
@MarcusOtter MarcusOtter moved this to Todo-soon in Needle v2.0 Jan 22, 2022
@n1ckoates
Copy link
Contributor

This is a great change to make as soon as possible, as license changes require approval from past contributors. At the moment, that's just @jasikpark.

@jasikpark
Copy link
Contributor

an ok from me 👍 agpl sounds like an improvement 😁

@n1ckoates
Copy link
Contributor

Another important decision to make is whether to have the "or later" clause in the license. The "or later" clause is recommended by the FSF (creators of the GPL). If a newer version of the GPL was released, users could (optionally) use it instead. There are pros and cons to both approaches.

Repository owner moved this from Todo-soon to Done in Needle v2.0 Feb 3, 2022
@MarcusOtter MarcusOtter unpinned this issue Feb 3, 2022
@MarcusOtter MarcusOtter changed the title 💡 Improvement: Change license to AGPL 💡 Change license to AGPL May 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement 💡 Improvement suggestion
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants