License public repos and create Allod landing docs #11
Loading…
Add table
Add a link
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.