-
We need a public-facing machine which hosts at least the API so the website can have the live scores etc. (setting up that portion is #112).
Separately, see #118 for the in-venue box.
-
The score-input UI should match the score-sheets as much as possible to reduce the chance of errors when inputting the data. The _design_ of both should therefore happen at the same time (see #109), s…
-
Related to #109, though underlying it, and #119 we need an automated scorer which reads the input match states and scores them.
See https://github.com/PeterJCLaw/srcomp/wiki/Competition-Preparation#i…
-
- prep the image
- flash the SDs (for the borrowed ones, we need to review what's already on them and possibly re-flash them back that afterwards)
- generate list of MAC addresses and desired DNS en…
-
In concert with #65, this will go in https://github.com/srobo/comp-floorplans and would ideally use a similar build mechanism (see the 2017 folder) for integration with SRComp.
The crux of this tas…
-
Depends on #102 and #103
-
-
We need to work out what we need in the competition network, what services we want to run, etc.
Includes:
- SRComp
- Display Screens
- ~Telephony (probably)~
- NOT Competitor WiFi (see #68)
…
-
Make sure we know what will be running on display screens at the competition, ensure these are up to date and functioning.
-