Simplify license terms in README

[diegorodriguezv]

Removed additional restrictions on commercial use, redistribution, and competing services according to the AGPL:

All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.

[greptile-apps]

Greptile Summary

This PR modifies the License section of README.md to remove three additional restrictions the project owner had placed on top of the AGPL v3 license: a commercial use prohibition, a no-public-redistribution clause, and a competing-services prohibition. The stated rationale is that AGPL section 10 classifies these as "further restrictions" that any recipient may remove from their copy.

• The LICENSE file contains only the stock AGPL v3 text and was not changed; the additional restrictions existed only in the README, so there was already a gap between the two.
• Removing these lines from the project's README is a policy decision that affects how future contributors and users interpret the project's intent — it should be approved by the copyright holder, not made unilaterally by a contributor.

Confidence Score: 3/5

The change touches only the README License section, but it removes explicit restrictions the maintainer placed there; merging without maintainer approval risks misrepresenting the project's intended licensing terms.

The only file changed is README.md, and there are no code correctness issues. However, the change removes restrictions that appear to reflect the copyright holder's intent, and that decision should not be made by a third-party contributor without explicit maintainer consent.

README.md — the License section is the sole change and warrants direct review by the project owner before merging.

Important Files Changed

Filename	Overview
README.md	Removes three additional license restrictions from the License section, making the README consistent with the bare AGPL v3 text in LICENSE; this is a significant policy change that should be approved by the copyright holder.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[README.md — License section] -->|Before PR| B["AGPL v3\n+ Commercial use prohibited\n+ No public redistribution\n+ Competing services prohibited"]
    A -->|After PR| C["AGPL v3 only"]
    D[LICENSE file] --> E["Standard AGPL v3 text\n(no additional restrictions)"]
    C -.->|Now consistent| E
    B -.->|Was inconsistent with| E

Loading

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
README.md:281-286
**Policy change requires maintainer sign-off**

This PR removes three additional restrictions (commercial use, redistribution, competing services) that the project owner explicitly added to the README. While the PR author cites AGPL section 10 to argue these restrictions are "further restrictions" that recipients may remove for their own copies, _removing them from the canonical README_ is a different act — it changes the stated policy of the project itself, not a downstream recipient's copy. That decision belongs solely to the copyright holder(s). The `LICENSE` file contains only the standard AGPL v3 text and has not been changed, so this PR creates a new inconsistency: the README no longer reflects the restrictions the maintainer intended to communicate, even if those restrictions were of questionable legal enforceability under AGPL.

_{Reviews (1): Last reviewed commit: "Simplify license terms in README" | Re-trigger Greptile}

[greptile-apps]

Policy change requires maintainer sign-off

This PR removes three additional restrictions (commercial use, redistribution, competing services) that the project owner explicitly added to the README. While the PR author cites AGPL section 10 to argue these restrictions are "further restrictions" that recipients may remove for their own copies, removing them from the canonical README is a different act — it changes the stated policy of the project itself, not a downstream recipient's copy. That decision belongs solely to the copyright holder(s). The LICENSE file contains only the standard AGPL v3 text and has not been changed, so this PR creates a new inconsistency: the README no longer reflects the restrictions the maintainer intended to communicate, even if those restrictions were of questionable legal enforceability under AGPL.

Prompt To Fix With AI

This is a comment left during a code review.
Path: README.md
Line: 281-286

Comment:
**Policy change requires maintainer sign-off**

This PR removes three additional restrictions (commercial use, redistribution, competing services) that the project owner explicitly added to the README. While the PR author cites AGPL section 10 to argue these restrictions are "further restrictions" that recipients may remove for their own copies, _removing them from the canonical README_ is a different act — it changes the stated policy of the project itself, not a downstream recipient's copy. That decision belongs solely to the copyright holder(s). The `LICENSE` file contains only the standard AGPL v3 text and has not been changed, so this PR creates a new inconsistency: the README no longer reflects the restrictions the maintainer intended to communicate, even if those restrictions were of questionable legal enforceability under AGPL.

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!