License public repos and create Allod landing docs #11
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
allod/strategy#11
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
User story: So that I can publish Allod as a usable public framework, I need every public repo to carry clear licensing and landing documentation that explains what the project is and where to start.
Part of the "Public release & private-first migration" arc.
Decision
Use
GPL-3.0-or-laterfor the public Allod repositories.Why: GPLv3-or-later gives strong copyleft that matches Allod's self-sovereign infrastructure goals, while avoiding AGPL's extra ambiguity/friction around reusable Nix flakes and NixOS modules.
Scope
Starting Point
Use strategy/brainstorm/org-profile.md as the starting draft for the landing page / org profile.
Licensing sweep for the public repos is done (GPL-3.0-or-later, per the decision above). Each LICENSE opens with a short copyright + SPDX notice (
SPDX-License-Identifier: GPL-3.0-or-later) over the verbatim GNU GPL v3 text.One PR per repo:
allod/deploywas empty (no commits) so it could not take a PR; the LICENSE was committed directly tomasteras the root commit, and allod/deploy#1 tracks importing the deploy-flake content from the private repo.Still open under this issue and intentionally not closed here: the public landing page / org profile (
brainstorm/org-profile.mdis the draft), and READMEs for the repos that still lack them (memory,strategy, anddeployonce it has content).done