chore: relicense Ordo from GPL-2.0-or-later to AGPL-3.0-or-later #94

New issue

Closed

opened 2026-07-02 05:09:25 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-02 05:09:25 +00:00

(Migrated from github.com)

Problem

Ordo is licensed GPL-2.0-or-later while the rest of the Introibo platform (Core, Api, Site) is AGPL-3.0-or-later. Standardise Ordo on AGPL-3.0-or-later. The repo has never been published or used externally, so this is a clean relicense with no third-party rights to consider.

Acceptance criteria

LICENSE contains the AGPL-3.0 text
composer.json license = AGPL-3.0-or-later
README licence line updated
No remaining GPL-2.0 references

## Problem Ordo is licensed GPL-2.0-or-later while the rest of the Introibo platform (Core, Api, Site) is AGPL-3.0-or-later. Standardise Ordo on **AGPL-3.0-or-later**. The repo has never been published or used externally, so this is a clean relicense with no third-party rights to consider. ## Acceptance criteria - [ ] `LICENSE` contains the AGPL-3.0 text - [ ] `composer.json` `license` = `AGPL-3.0-or-later` - [ ] README licence line updated - [ ] No remaining GPL-2.0 references

manlycucumber referenced this issue from a commit

2026-08-05 19:02:32 +00:00

chore: relicense Ordo to AGPL-3.0-or-later (#94) (#95)

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

Directorium/Ordo#94

No description provided.

Rows
Columns