Team setup: install and configure for any team

オープン
  • 何か問題がありますか？
#24 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
python
領域
cli, release

調査の方向性

Read the team-setup OpenSpec change linked in the issue and inspect release.yml plus its pypi and testpypi environments. The remaining work includes PyPI trusted publisher setup, a TestPyPI dry run, a first tagged release, and a clean-laptop walkthrough; start with the PyPI organization dependency and follow the listed steps. Done means the install works from PyPI and a new team can complete setup.

索引モデルが issue の本文から書いたものです。

説明

roadmap

Size: L · Depends on: IgniteRobotics/flashpoint#17, IgniteRobotics/flashpoint-private#71 · OpenSpec: team-setup (archived 2026-11-01)

Status

Update 2026-11-01: archived (PR #41), 26/28 tasks. Specs synced to openspec/specs/team-setup and openspec/specs/config-editor. Open, tracked in #13: 4.3 first release (tag v0.2.0, clean pipx install) and 9.4 [HUMAN] new-team walkthrough. Close this once both pass.

Update 2026-10-23: in progress, 24/28 tasks. Implemented and merged: packaging, config home, init and setup checks (IgniteRobotics/flashpoint-private#88), then the Setup view, editor, fix actions and robot draft (IgniteRobotics/flashpoint-private#89, ADR-0017). PyPI metadata, BSD-3-Clause license and release workflow merged (#2); new-season setup docs (#1). The repo went public 2026-10-22 with a rewritten history (owlet binaries and personal emails removed); 1.1, 1.3 and 1.4 ticked (#29).

Left:

  • 1.2 [HUMAN] Claim the PyPI name and add the trusted publisher (release.yml, environments pypi / testpypi). Waiting on the PyPI organization setup.
  • 2.2 Dry run to TestPyPI and pipx install --index-url https://test.pypi.org/simple/ flashpoint (after 1.2).
  • 4.3 First release: tag v0.2.0 (the pypi environment asks for approval), pipx install flashpoint on a clean machine.
  • 9.4 [HUMAN] New-team walkthrough on a clean laptop.

Scope

Make Flashpoint usable by any FRC team with an easy install.

  • Public install: repo public, published to PyPI with trusted publishing, so pipx install flashpoint works (ADR-0009 finally holds). Bundled defaults ship in the package; Ignite's robots and units stay in the repo's config/, out of the wheel.
  • Config home: per-user folder (~/.config/flashpoint, %APPDATA%\flashpoint). flashpoint init creates it with the team number and lake folder and never overwrites. Breaking: no more fallback to a checkout's config/. Fixes IgniteRobotics/flashpoint-private#54.
  • Team number drives robot addresses (10.TE.AM.2, roborio-TEAM-frc.local, USB) instead of 6829's.
  • Setup view: shows the whole configuration (team and connection, robots and slots, thresholds, units) and every setup check. doctor uses the same checks and exits non-zero on a problem.
  • Edit configuration in the UI: validated with the loading rules, comments kept, conflict check, last 20 versions backed up. Read-only when shared on the network.
  • Draft a robot from a log: devices from the hoots, serials from the CAN inventory, bus names from bus status. The fast path for a new team.
  • Fix actions: guarded (ADR-0015 style, new ADR-0017) buttons for create config, download/verify owlet, AdvantageScope path, install/start the acquire service. Anything else shows the exact command.
  • Non-goals: a no-Python installer, hosting or accounts, editing lake data from the UI, a robot-side vendordep (samples only), macOS acquire service.
主要言語
Python
スター
0
フォーク
1
平均マージ
18時間 37分
マージ済み PR（30日）
15

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

IgniteRobotics/flashpoint のほかの issue

IgniteRobotics/flashpoint の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。