845d6b8dcd
## Summary - Introduce a standalone Python roadmap validator with a CLI entry point, modular validation pipeline, and GitHub Actions wiring so roadmap content can be linted locally and in CI. - Provide reusable validation primitives for path resolution, front-matter parsing, identity checks, task parsing, catalog enforcement, and template adherence. - Document usage, configuration, and workflow behaviour to make the validator approachable for contributors. ## Validator Details - **Core tooling** - Added the `tools/roadmap_validator/` package with `validate.py` (CLI), `validator.py` (orchestration), and helper modules (`tasks.py`, `identity.py`, `paths.py`, `constants.py`, `issues.py`). - CLI supports directory/file targets, skips default filenames, emits GitHub annotations, and integrates optional substring filtering - README explains features, environment variables, and development guidance. - **Catalog and template enforcement** - `catalog.py` verifies each allowed content unit has `index.md` and `preview.md`, confirms roadmap entries appear under the proper quarter/area, and flags stale or missing links. - `templates.py` enforces template basics: front matter completeness, `## Description` ordering/content, template placeholder cleanup, and task section detection. - **Task validation** - `tasks.py` checks required metadata (`owner`, `status`, `start-date`, `end-date`), date formats, populated descriptions/deliverables, TODO markers, tangible deliverable heuristics, and `fully-qualified-name` prefixes. - **Workflow integration** - `.github/workflows/roadmap-validator.yml` runs the validator on pushes and manual dispatch, installs dependencies, scopes validation to changed Markdown, and surfaces findings via GitHub annotations. ## Existing Roadmap Updates - Normalised 2025q4 commitments across Web, DST, QA, SC, and other units by filling in missing descriptions, deliverables, schedule notes, recurring task statuses, and maintenance tasks. - Added tasks where absent, removed remaining template placeholders, aligned fully qualified names, and ensured roadmap files conform to the new validator checks. ## Testing ```bash python tools/roadmap_validator/validate.py *2025q4* ``` CI: `Roadmap Validator` workflow runs automatically on pushes/dispatch. --------- Co-authored-by: kaiserd <1684595+kaiserd@users.noreply.github.com>
2.1 KiB
title, tags, draft, description
| title | tags | draft | description | |||
|---|---|---|---|---|---|---|
| nim-libp2p IPv6 support |
|
false | add first-class IPv6 support across transports |
vac:p2p:ift:2025q4-nimlibp2p-ipv6
Enable IPv6 support
Description
Enable IPv6 in nim-libp2p end-to-end so users of the library can run dual-stack when needed. Scope covers transports (tcp/quic), address handling (multiaddr, identify), and ci/test infra.
Task List
Core transports (tcp/quic)
- fully qualified name:
vac:p2p:ift:2025q4-nimlibp2p-ipv6:transport - owner: rramos
- status: not started
- start-date: 2025/10/01
- end-date: 2025/12/31
Description
Add IPv6 listen/dial for tcp and quic. Might require changes in chronos
Schedule note: Dates reflect quarter bounds; update when actual timing is known.
Deliverables
- nodes can listen on /ip6 and accept inbound requests
- dialer can dial /ip6 addresses
addresses & identity
- fully qualified name:
vac:p2p:ift:2025q4-nimlibp2p-ipv6:addresses - owner: rramos
- status: not started
- start-date: 2025/10/01
- end-date: 2025/12/31
Description
Add IPv6 support in the switch when specifying listening multiaddresses containing ip6 component. Ensure ip6 addresses are advertised in identify. Implement measures to handle duplicated IPs in peerstore/addresses being listened to (i.e 192.0.2.42 vs 2001:db8::1234).
Schedule note: Dates reflect quarter bounds; update when actual timing is known.
Deliverables
- Identify advertises correct /ip6 addrs; observed addrs tracked per transport
Testing, Interop & CI
- fully qualified name:
vac:p2p:ift:2025q4-nimlibp2p-ipv6:testing - owner: rramos
- status: not started
- start-date: 2025/10/01
- end-date: 2025/12/31
Description
Ensure IPv6 support and ensure there are no regressions in IPv4 support. Add test units demonstrating the support, and check that interop against other implementations is achieved
Schedule note: Dates reflect quarter bounds; update when actual timing is known.
Deliverables
- Test units focusing on IPv6
- Interop tests against other implementations that support IPv6