Skip to content

Change licence to AGPLv3#1216

Open
f-PLT wants to merge 1 commit intomainfrom
change-licence
Open

Change licence to AGPLv3#1216
f-PLT wants to merge 1 commit intomainfrom
change-licence

Conversation

@f-PLT
Copy link
Copy Markdown
Contributor

@f-PLT f-PLT commented Apr 8, 2026

Summary

This PR updates the project's license from the GNU General Public License v3.0 (GPLv3) to the GNU Affero General Public License v3.0 (AGPLv3).

Why are we making this change?

Under the standard GPLv3, the copyleft provisions are only triggered upon distribution of the software. This creates a known loophole (often called the "SaaS loophole" or "ASP loophole"): a company can take our code, modify it extensively, and offer it to users as a web service without ever actually "distributing" the binaries. Consequently, they are not obligated to share their improvements back with the community.

The AGPLv3 was specifically designed to close this loophole. It contains the same robust copyleft conditions as the GPLv3, but adds a crucial provision (Section 13: Remote Network Interaction). This section requires that if you modify the program and let others interact with it remotely through a computer network, you must make the source code of your modifications available to those users.

By moving to the AGPLv3, we are:

  • Protecting the open-source ecosystem: Ensuring that any entity benefiting from hosting our software and modifying it gives those modifications back to the community.

  • Securing project sustainability: Preventing bad actors or large cloud providers from silently forking our project, wrapping it in a proprietary service, and starving the core project of contributions.

Impact and what this means for our users:

For individual users & internal company use: If you are using or modifying the software strictly for internal use and not exposing it externally as a service, nothing changes for you.

  • For contributors: No change. Your contributions will simply be licensed under AGPLv3 going forward.

  • For SaaS providers & Commercial hosts: If you modify our software and allow users to interact with it over a network, you must now provide a way for those users to access the modified source code under the AGPLv3.

Summary by CodeRabbit

  • Chores
    • Updated project license from GNU General Public License (GPL) v3 to GNU Affero General Public License (AGPL) v3. All license terms, preamble, definitions, and boilerplate notices have been updated accordingly.

@f-PLT f-PLT self-assigned this Apr 8, 2026
@netlify
Copy link
Copy Markdown

netlify bot commented Apr 8, 2026

Deploy Preview for antenna-ssec canceled.

Name Link
🔨 Latest commit c09a917
🔍 Latest deploy log https://app.netlify.com/projects/antenna-ssec/deploys/69d6a0040684db0008356f72

@netlify
Copy link
Copy Markdown

netlify bot commented Apr 8, 2026

Deploy Preview for antenna-preview ready!

Name Link
🔨 Latest commit c09a917
🔍 Latest deploy log https://app.netlify.com/projects/antenna-preview/deploys/69d6a004d5704600083fb569
😎 Deploy Preview https://deploy-preview-1216--antenna-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 74 (🔴 down 6 from production)
Accessibility: 97 (no change from production)
Best Practices: 92 (no change from production)
SEO: 100 (no change from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 8, 2026

📝 Walkthrough

Walkthrough

The LICENSE file has been updated from GNU General Public License v3 (dated June 2007) to GNU Affero General Public License v3 (dated November 2007). This replaces all references, preamble text, definitions, and boilerplate notices to reflect AGPL's network-server-focused requirements instead of GPL's traditional copyleft model.

Changes

Cohort / File(s) Summary
License Update
LICENSE
Replaced GPL v3 with AGPL v3, updating preamble, definitions, section 13 (network interaction obligations), boilerplate notices, and all references from "GNU General Public License" to "GNU Affero General Public License".

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A carrot of freedom, now networked and shared,
From GPL's promise to AGPL's care,
Where servers must open what modifications declare,
The license hops forward with copyleft flair! 🌐✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Change licence to AGPLv3' directly and clearly summarizes the main change: updating the project license from GPLv3 to AGPLv3.
Description check ✅ Passed The PR description provides a comprehensive summary, detailed rationale for the license change, and impact analysis, but lacks several template sections including list of changes, related issues, testing instructions, and a deployment checklist.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch change-licence

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@f-PLT f-PLT marked this pull request as ready for review April 8, 2026 18:42
@f-PLT f-PLT requested a review from mihow April 8, 2026 18:42
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
LICENSE (1)

1-661: ⚠️ Potential issue | 🟡 Minor

Align boilerplate notice with official AGPLv3 text in the "How to Apply These Terms to Your New Programs" section.

The LICENSE file differs from the official AGPLv3 published by the Free Software Foundation in the boilerplate notice (lines 633–637). The phrase "as published by the Free Software Foundation" is split across lines differently than the official version. Update line 636 to match the official formatting:

Formatting correction needed
-    it under the terms of the GNU Affero General Public License as published
-    by the Free Software Foundation, either version 3 of the License, or
+    it under the terms of the GNU Affero General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or

Additionally, ensure that:

  • Contributors are notified of the GPLv3→AGPLv3 relicensing, as this change affects all existing contributions (AGPLv3's network interaction clause in Section 13 is more restrictive).
  • Other project documentation (README, CONTRIBUTING, package metadata) reflects the AGPLv3 license.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@LICENSE` around lines 1 - 661, Update the "How to Apply These Terms to Your
New Programs" boilerplate in LICENSE so the one-line copyright/permission block
exactly matches the official AGPLv3 wording (the paragraph beginning "This
program is free software: you can redistribute it and/or modify it under the
terms of the GNU Affero General Public License as published by the Free Software
Foundation, either version 3 of the License, or (at your option) any later
version.")—replace the current split/incorrect lines with the exact official
sentence; then add an explicit contributor notification about relicensing from
GPLv3→AGPLv3 (call out Section 13/network interaction) and update project docs
(README, CONTRIBUTING, package metadata like package.json) to state the AGPLv3
license and link to the official text.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@LICENSE`:
- Around line 1-661: Update the "How to Apply These Terms to Your New Programs"
boilerplate in LICENSE so the one-line copyright/permission block exactly
matches the official AGPLv3 wording (the paragraph beginning "This program is
free software: you can redistribute it and/or modify it under the terms of the
GNU Affero General Public License as published by the Free Software Foundation,
either version 3 of the License, or (at your option) any later
version.")—replace the current split/incorrect lines with the exact official
sentence; then add an explicit contributor notification about relicensing from
GPLv3→AGPLv3 (call out Section 13/network interaction) and update project docs
(README, CONTRIBUTING, package metadata like package.json) to state the AGPLv3
license and link to the official text.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 99e45d9e-0f05-4e9d-9200-11c782ed1c77

📥 Commits

Reviewing files that changed from the base of the PR and between 83a970c and c09a917.

📒 Files selected for processing (1)
  • LICENSE

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.

1 participant