Implement MIL-006: project license in config.env; AGPL-3.0 default only for a public GitHub project #52

Open
Tirsvad wants to merge 2 commits from mil-006-license into mil-006-plan
Owner

Implements MIL-006. Based on mil-006-plan (PR #43), so the base is that branch; retarget to main once #43 is merged.

  • PROJECT_LICENSE in config.env: a Gitea license key or none; checked before any request, never asked.
  • Without it, AGPL-3.0 applies only when GitHub is chosen and the project is public; a private project with GitHub gets none.
  • The license is applied on Gitea with or without GitHub, and the server must offer it before anything is created.
  • Plan and summary name the license and where it came from.
  • README and config.env.example document the key.
  • Tests: new tests/test-license.sh; existing tests that expected AGPL-3.0 on a private project now use a public one. Full suite: 985 checks, 0 failed.

Closes #44
Closes #45
Closes #46
Closes #50

Implements MIL-006. Based on `mil-006-plan` (PR #43), so the base is that branch; retarget to `main` once #43 is merged. - `PROJECT_LICENSE` in config.env: a Gitea license key or `none`; checked before any request, never asked. - Without it, AGPL-3.0 applies only when GitHub is chosen and the project is public; a private project with GitHub gets none. - The license is applied on Gitea with or without GitHub, and the server must offer it before anything is created. - Plan and summary name the license and where it came from. - README and config.env.example document the key. - Tests: new tests/test-license.sh; existing tests that expected AGPL-3.0 on a private project now use a public one. Full suite: 985 checks, 0 failed. Closes #44 Closes #45 Closes #46 Closes #50
Tirsvad added 2 commits 2026-10-07 07:28:50 +02:00
- PROJECT_LICENSE (a Gitea license key, or none) is read, checked and never asked
- Without it AGPL-3.0 applies only when GitHub is chosen and the project is public
- The license is applied on Gitea with or without GitHub, and checked against the server first
- Plan and summary name the license and where it came from
- MIL-006 accepted; README and config.env.example document the key
- Tests: new test-license.sh; existing tests use a public project where they expect AGPL-3.0

Task: MIL-006#1
Task: MIL-006#2
Task: MIL-006#3
Task: MIL-006#4
Refs #44
Refs #45
Refs #46
Refs #50
A private project with GitHub no longer gets a license, so only a public one expects it.

Task: MIL-006#4
Refs #50
You are not authorized to merge this pull request.
This pull request can be merged automatically.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin mil-006-license:mil-006-license
git checkout mil-006-license
Sign in to join this conversation.