Team setup: install and configure for any team
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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, environmentspypi/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(thepypienvironment asks for approval),pipx install flashpointon 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 flashpointworks (ADR-0009 finally holds). Bundled defaults ship in the package; Ignite's robots and units stay in the repo'sconfig/, out of the wheel. - Config home: per-user folder (
~/.config/flashpoint,%APPDATA%\flashpoint).flashpoint initcreates it with the team number and lake folder and never overwrites. Breaking: no more fallback to a checkout'sconfig/. 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.
doctoruses 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.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 18h 37m
- Merged PRs (30d)
- 15
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from IgniteRobotics/flashpoint
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
IgniteRobotics/flashpoint#45 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
IgniteRobotics/flashpoint#44 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
IgniteRobotics/flashpoint#43 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
IgniteRobotics/flashpoint#12 ·
Maintainers usually reply within 1 day
-
tools/update-owlet-manifest.py ignores --help and starts downloadingMay be free again @yoveneim claimed this 11 days ago, and no pull request is open. Openbug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
IgniteRobotics/flashpoint#11 · 1 comment ·
Maintainers usually reply within 1 day
All issues in IgniteRobotics/flashpoint
Similar issues
-
bug ready-for-dev
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
OpenHands/extensions#897 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tensorflow/datasets#11253 ·
Maintainers usually reply within 1 day
-
fix(core): a config section with all keys commented out crashes startupPossibly taken @Aryanbhargava18 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
kubeflow/mcp-server#512 ·
Maintainers usually reply within 1 day
-
Stop trusting the compromised eMudhra CA certificatesPossibly taken @anth-volk claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
PolicyEngine/uk-triple-lock#54 ·
Maintainers usually reply within 1 day
-
DBFS append mode silently overwrites existing filesPossibly taken @IlyaKhalafi claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
fsspec/filesystem_spec#2429 ·
Maintainers usually reply within 1 day