-
In order to sync up the screens (#70), lighting (#65) and audio (#66) we'll need a network and likely a deploy of [SRComp](https://github.com/PeterJCLaw/srcomp/wiki). These will be driven by a compsta…
-
-
We need to know how the knockout matches will work - which teams will face which other teams along with timings.
This may be able to be similar to previous years, however with the increase in teams…
-
Under Python 2 we got away with having the `./update` script be a locally callable script. Under Python 3 this hits issues due to the inclusion of the script's own directory on the `sys.path` which is…
-
We're going to need a copy of the score-entry UI running somewhere. In the past this has been on the machine which is also used for score-entry, though that's not especially ideal as it places additio…
-
* [x] per https://github.com/srobo/tasks/issues/102#issuecomment-471192406 we would like to have an extra gap between the two semi-finals
* [x] per a discussion with @prophile which I now can't find …
-
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…
-
This needs to embed the livestream form youtube and somehow exist on the compbox. This could either be a page in the srcomp-puppet repo, or in the srcomp-screens repo.
-
This is for the SRComp related machines:
- the compbox (#118)
- the display screens (#96)
- the score-entry laptop
Task as I keep forgetting this!
-
We need a machine at the venue which hosts the various screens and the local SRComp for match timings etc.
Separately, see #233 for the public facing box.