This repo is focussed on meeting notes, high-level design documents, etc. Only add issues in this repo related to meeting notes and docs. No code issues. Our main repo & issue tracker is at https://git.fediversity.eu/fediversity/fediversity
- PostScript 100%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
cinereal
eabb994eb8
`architecture-docs/architecture.md`'s `## Actors` and `## Glossary` become a pointer to <https://core.pages.git.fediversity.eu/concepts.html>, so exactly one copy of that vocabulary survives. The page is new in the `fediversity` monorepo (`core/docs/md/concepts.md`), and is the union of the two copies that existed: it carries the root `README.md` text plus this document's `Maintainers`/`Developers` split under Actors and its `Provider`, `Provider configuration` and `Resource` glossary entries. Nothing is dropped. It lives there because that is where the terms are used -- the option reference and the flake-attribute pages on the same site refer to them without redefining them. The two in-document links that pointed at the removed anchors (`- Circle: [actor](#actors)` and the components note) are repointed at the same page's anchors. Separate note, not touched here: `### Proxmox` under `## Technologies used` still describes Proxmox as the hypervisor. The `fediversity` repo no longer uses it -- it deploys through Incus. Flagging rather than rewriting, since the rest of that section is a planning document rather than a description of the code, and deciding what replaces it is a call for the project team. Assisted-by: Claude:claude-opus-5 Reviewed-on: #41 |
||
| agreement | ||
| architecture-docs | ||
| Documentation | ||
| investment_analysis | ||
| KickOff | ||
| MarCom | ||
| meeting-notes | ||
| planning | ||
| target_software | ||
| .gitignore | ||
| default.nix | ||
| Fediversity_software_stack.md | ||
| Fediversity_target_audience.md | ||
| LICENSE | ||
| notes.md | ||
| Outreach ideeen fediversity.md | ||
| README.md | ||
| secrets-management.md | ||
| shell.nix | ||
meta
Meeting notes, high-level design documents, etc.