Q-46: Bring the incumbent scoring team into the project #1
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#1
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?
The Delcuvé family currently runs the scoring desk at the German championships and owns
the existing tooling (
fs-ergebnisse.de, LENEX3 entries, the official Protokoll PDF).We have decided to replace that system end to end (Q-01).
This is a people question before it is a technical one. Are they informed, and are they
with us, beside us, or against us? Can they be part of the project rather than displaced by it?
Working assumption: they are approached early and offered a role, and we design for a shared
desk rather than a takeover.
Owner: Robert. See
docs/04-open-questions.mdQ-46.