[FOSS pivot] Adopt a single, consistent license #41

Closed
opened 2026-08-16 15:09:55 +02:00 by myrmidex · 0 comments
Owner

Context

The project currently states three different licenses:

  • LICENSE.md = GPL-3.0
  • README.md = "MIT"
  • site landing page = "AGPL-3.0"

This must be resolved to one choice before we position as a FOSS project.

Options

  • AGPL-3.0 — recommended for a self-hosted web app; keeps the FOSS guarantee even when hosted publicly (closes the GPL network loophole)
  • GPL-3.0 — copyleft for distributed binaries, but a hosted instance can withhold modifications
  • MIT — maximum adoption, no copyleft

Scope

  • Decide the license (decision needed here)
  • Update LICENSE.md, README.md, and the site landing page to state the same license

Acceptance criteria

  • LICENSE.md + README + site all agree on one license
## Context The project currently states three different licenses: - `LICENSE.md` = GPL-3.0 - `README.md` = "MIT" - site landing page = "AGPL-3.0" This must be resolved to one choice before we position as a FOSS project. ## Options - **AGPL-3.0** — recommended for a self-hosted web app; keeps the FOSS guarantee even when hosted publicly (closes the GPL network loophole) - **GPL-3.0** — copyleft for distributed binaries, but a hosted instance can withhold modifications - **MIT** — maximum adoption, no copyleft ## Scope - Decide the license (decision needed here) - Update `LICENSE.md`, `README.md`, and the site landing page to state the same license ## Acceptance criteria - `LICENSE.md` + `README` + site all agree on one license
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lvl0/dishplanner#41
No description provided.