Record operational readiness pass
This commit is contained in:
53
README.md
53
README.md
@@ -186,3 +186,56 @@ Independent API audit completed after the write pass:
|
|||||||
- Audit failures: 0
|
- Audit failures: 0
|
||||||
|
|
||||||
One classification mismatch was repaired during verification: `evil-cardputer` now has the expected `Hardware` wiki page.
|
One classification mismatch was repaired during verification: `evil-cardputer` now has the expected `Hardware` wiki page.
|
||||||
|
|
||||||
|
## Operational Readiness Pass: 2026-05-20
|
||||||
|
|
||||||
|
Applied the next non-destructive readiness layer across all 58 Gitea repositories.
|
||||||
|
|
||||||
|
### Readiness Files
|
||||||
|
|
||||||
|
Every repo now has:
|
||||||
|
|
||||||
|
- `.editorconfig`
|
||||||
|
- `.gitattributes`
|
||||||
|
- `docs/ROADMAP.md`
|
||||||
|
- `docs/MAINTENANCE.md`
|
||||||
|
- `docs/RELEASE_PROCESS.md`
|
||||||
|
- `docs/PROVENANCE_CHECKLIST.md`
|
||||||
|
- `docs/SECURITY_REVIEW.md`
|
||||||
|
- `docs/PROJECT_HANDOFF.md`
|
||||||
|
|
||||||
|
Keeper decision: these files establish the operating surface for every repo without pretending the project-specific facts are already known. Custom existing files were preserved; the pass only created missing files or updated known stewardship-standard files.
|
||||||
|
|
||||||
|
### Milestones
|
||||||
|
|
||||||
|
Every repo now has four operational milestones:
|
||||||
|
|
||||||
|
- `Triage`
|
||||||
|
- `Provenance Review`
|
||||||
|
- `First Verified Release`
|
||||||
|
- `Maintenance`
|
||||||
|
|
||||||
|
### Issues
|
||||||
|
|
||||||
|
Every repo now has one `Stewardship Readiness Checklist` issue. The issue is the maintainer-facing queue for replacing generic stewardship notes with project-specific facts, completing security review, resolving license status, and preparing a verified release.
|
||||||
|
|
||||||
|
### Topics
|
||||||
|
|
||||||
|
Every repo now has searchable readiness topics:
|
||||||
|
|
||||||
|
- `stewarded`
|
||||||
|
- `readiness`
|
||||||
|
- one project-class topic: `hardware`, `automation`, or `software`
|
||||||
|
- `firmware` where the repo is hardware/firmware-oriented
|
||||||
|
- `private-workspace` where the repo is private
|
||||||
|
|
||||||
|
### Verification
|
||||||
|
|
||||||
|
Independent API audit completed after the readiness pass:
|
||||||
|
|
||||||
|
- Repositories audited: 58
|
||||||
|
- Readiness files: 8/8 present on every repo
|
||||||
|
- Operational milestones: 4/4 present on every repo
|
||||||
|
- Readiness issue: present on every repo
|
||||||
|
- Required topics: present on every repo
|
||||||
|
- Audit failures: 0
|
||||||
|
|||||||
Reference in New Issue
Block a user