OpenVoiceOS / OpenVoiceOS/architecture
Classify every spec as V1 or V2 before launch day
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 0
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 90
Description
Per VERSIONING.md (see the policy PR): V1 = formalization compatible with the V0 status quo (even if degraded); V2 = not backwards compatible. Every spec file and every open spec PR needs the classification added to its header. Candidate quick reads: parallel-namespace specs behind legacy_namespace gating → V1 with gated V2 sections; renames like fallback.ping/pong → V2 unless dual-emitted.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with VERSIONING.md and the referenced policy PR, then review every spec file and open spec PR for its header classification. Mark each as V1 or V2 according to the stated compatibility rules, including the parallel-namespace and fallback.ping/pong cases, and verify that all specs and open PRs are covered.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100