P0: Stabilize & decide

未关闭
  • 哪里不对？
#16 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
github-actions, python
领域
backend, devops

调研方向

Start with openspec/changes/p0-stabilize-foundation/tasks.md and the linked architecture sections in docs/rewrite/05-target-architecture.md and docs/rewrite/99-ctre-device-serial-numbers.md. The issue says most repository work is done; remaining tasks require live robot checks and team review, with robot checks tracked in #13. Done means the ADR review is complete and the corpus, CI skeleton, and CAN inventory requirements in the stated exit criteria are satisfied.

由索引模型根据 Issue 内容生成。

描述

roadmap

Size: S · Depends on: nothing · OpenSpec: p0-stabilize-foundation

Status

Update 2026-10-23: what's left is [HUMAN] 6.3 (check the CAN device fields on a live robot), 6.4 (confirm /Flashpoint/CANInventory in a fresh log from each robot) and 7.2 (unit registry walk with Tuner X), tracked in #13. Team review of the ADRs is still open. Repo work is done: legacy-2025 and archive/* tags, main protected (ci-ok required), rewrite merged into main 2026-10-22, repo public with the owlet binaries purged from history.

Update 2026-10-19: what's left is [HUMAN] 6.3, 6.4 and 7.2, tracked in #13. Team review of the ADRs is still open.

Status: in progress (started 2026-10-04). Done: CI skeleton, tags, ADRs (D1–D10 Proposed, D11 Accepted), corpus-v1, Pro/compliancy findings, robot inventory logger PRs (IgniteRobotics/Robot-2026#107, IgniteRobotics/Phoenix-2026#12), retire-legacy-code stage 1. Open: [HUMAN] verify getdevices field names on a live robot, confirm /Flashpoint/CANInventory in fresh logs, Tuner X unit walk, team review of the ADRs. Tracked in openspec/changes/p0-stabilize-foundation/tasks.md.

Scope

  • Repo:
    • Tag the current main as legacy-2025.
    • Archive the branches under archive/*: development, power-tracking, static-site, dataviz, docker.
    • Delete hoot-support.
    • Protect main and require PRs plus CI.
  • Decisions: make the calls D1–D11 in 05 §6. Record each as a short ADR in docs/adr/.
  • Golden corpus: pick about 6 real logs and commit them through LFS or a fetch script.
    • one qual wpilog, plus its rio and CANivore hoots
    • one practice log
    • one non-FMS log
    • one log with a corrupt tail
    • one 2025 log and one 2026 log (owlet versions)
  • Robot-side CAN inventory logger (all robots): implement the contract in 05 §4a and 99.
    • First open http://<rio>:1250/?action=getdevices against the current Phoenix 6 robot to confirm the field names. The only documented example is from Phoenix 5 (CTR Electronics, n.d.-h).
    • Ship it before the next practice session, because every log recorded without it becomes a legacy-identity log.
    • Back-fill a units seed: walk each robot and spare shelf with Tuner X, record each serial against its slot, and label the motors physically.
  • Pro check: run owlet --check-pro (Mechanical Advantage, 2026) on the corpus. ✅ Done 2026-10-04: all hoots are Pro-licensed (ADR-0005). --compliancy was also found to be the owlet selection key (ADR-0004).
  • Exit: ADRs merged, corpus available, CI skeleton green, /Flashpoint/CANInventory present in a fresh log from every robot.

Moved from the rewrite roadmap on 2026-10-19. That doc keeps the dependency graph, migration, quality gates and risks. Status lives here. Author-year citations are in references.md. pitfall N refers to 03-pitfalls-and-performance.md.

主要语言
Python
星标
0
派生
1
平均合并
19 小时 40 分钟
30 天内合并 PR
14

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

IgniteRobotics/flashpoint 的其他 Issue

查看 IgniteRobotics/flashpoint 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。