Q-10: Decide how data gets from the lane to the scoring desk #5
Labels
No labels
area/broadcast
area/core
area/docs
area/operator
area/ops
area/rules
phase/analysis
phase/build
phase/design
phase/harden
prio/blocker
prio/high
prio/normal
type/bug
type/chore
type/decision
type/feature
type/question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
robert/divetiming#5
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Today a judge writes a paper protocol and a runner carries it to the scoring desk
(
Vorlagen/mail von mike.md). Removing that step is a large part of why this project exists.Do we get an input device at each lane, or does the app only replace the desk end?
Working assumption: one device per lane judge (web app on a tablet or phone) plus a desk
operator, with paper retained as the fallback.
Depends on hardware availability and on how many volunteers we can train.
Owner: Robert / host. See
docs/04-open-questions.mdQ-10.