Skip to content

Commit 935dca0

Browse files
RealOrangeOneRealOrangeOne
authored
Merge pull request #45 from srobo/upstream-sr2019-tasks
Upstream SR2019 tasks
2 parents 9b38096 + 2e3a25a commit 935dca0

19 files changed

+151
-19
lines changed

‎comp/flyers.yaml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,7 @@ description: >-
1515
- descriptions of both SR and the game
1616
- a summary of the teams competing (a list of TLAs and names is fine)
1717
- the overall schedule of the competition weekend
18+
- sponsors
1819
1920
Note: much of the content of these flyers does not need to actually be new --
2021
the website already contains plenty of summaries of SR and the game, which can

‎comp/game/robot-flag-mounts.yaml

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
summary: Purchase spare robot flag mounting hardware
2+
3+
priority: major
4+
5+
component: Competition
6+
7+
milestone: $SRYYYY Competition
8+
9+
description: >-
10+
During matches robots are given coloured flags so that the audience know which
11+
robot is from which scoring zone.
12+
13+
We expect that not all teams will have suitable mounts for flags. To
14+
allow for this we should therefore obtain some mounting components they can
15+
use. We already own a hot glue gun, though we may need to get some more glue
16+
sticks. The mounting component has historically been
17+
https://www.screwfix.com/p/jg-speedfit-pem0215w-l-equal-tee-white-15-x-15-x-15mm-5-pack/74470.
18+
19+
dependencies:
20+
- comp/pre-comp-storage-trip

‎comp/game/robot-flags.yaml

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,11 +13,6 @@ description: >-
1313
At least two complete sets of each badge are needed: one for the robots
1414
currently playing and another for the robots currently staging.
1515
16-
We also expect that not all teams will have suitable mounts for flags. To
17-
allow for this we should therefore obtain some mounting components they can
18-
use. We already own a hot glue gun, though we may need to get some more glue
19-
sticks. The mounting component has historically been
20-
https://www.screwfix.com/p/jg-speedfit-pem0215w-l-equal-tee-white-15-x-15-x-15mm-5-pack/74470.
21-
2216
dependencies:
2317
- comp/pre-comp-storage-trip
18+
- comp/game/robot-flag-mounts

‎comp/livestream/configure-scenes.yaml

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
summary: Organise livestream scenes
2+
3+
priority: major
4+
5+
component: Competition
6+
7+
milestone: $SRYYYY Competition Prep
8+
9+
description: >-
10+
The livestream requires a number of different scenes and views, made up of
11+
static images, video feeds, overlays etc.
12+
13+
Most of the assets have already been created, but some may require updating
14+
or new ones created
15+
16+
See https://studentrobotics.org/runbook/competition/livestream/scenes/.
17+
18+
dependencies:
19+
- comp/livestream/plan-video-feeds

‎comp/livestream/hardware.yaml

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
summary: Organise hardware to run livestream
2+
3+
priority: major
4+
5+
component: Competition
6+
7+
milestone: $SRYYYY Competition Prep
8+
9+
description: >-
10+
This ticket relates to providing the actual machine that will be
11+
used for the livestream.
12+
13+
Requirements:
14+
- Video mixer PC (With dedicated GPU, capable of running OBS)
15+
- 2× HDMI capture card
16+
- 2× preview monitors
17+
- 2× cameras (depending on feed plan)
18+
- Audio mixers
19+
20+
dependencies:
21+
- comp/livestream/plan-video-feeds

‎comp/livestream/main.yaml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,3 +16,6 @@ description: >-
1616
1717
dependencies:
1818
- comp/venue/network
19+
- comp/livestream/training
20+
- comp/livestream/hardware
21+
- comp/livestream/configure-scenes

‎comp/livestream/plan-video-feeds.yaml

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
summary: Plan video feeds
2+
3+
priority: major
4+
5+
component: Competition
6+
7+
milestone: $SRYYYY Competition Prep
8+
9+
description: >-
10+
The livestream will need to have a few different camera feeds to show different parts of the venue
11+
12+
- Arena (likely multiple)
13+
- Hosts (who may be different to commentators)
14+
- Stage (only needed for prize giving)

‎comp/livestream/training.yaml

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
summary: Have livestream training sessions
2+
3+
priority: major
4+
5+
component: Competition
6+
7+
milestone: $SRYYYY Competition
8+
9+
description: >-
10+
Volunteers who are assigned to run the livestream should be
11+
trained how the system works, and how the event will be run.

‎comp/main.yaml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,6 @@ dependencies:
3939
- comp/prizes/main
4040
- comp/photos/main
4141
- comp/uprate-server
42-
- comp/spare-kit
4342
- comp/kit-testing-equipment
4443
- comp/kit-handback
4544
- comp/media-consent/main

‎comp/pits/helpdesk/expert-list.yaml

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
summary: Create domain expert list
2+
3+
priority: major
4+
5+
component: Competition
6+
7+
milestone: $SRYYYY Competition
8+
9+
description: >-
10+
If there is a problem at helpdesk, that those on helpdesk cannot solve, they need to know who to escalate to.
11+
12+
There will be different experts depending on the domain.
13+
14+
Example domains:
15+
16+
- Rules
17+
- Kit
18+
- Python API
19+
- Hardware
20+
- Competition operations
21+
- Event
22+
- Tech
23+
24+
Note that this list of people should also take into account who is likely to be available.

0 commit comments

Comments
 (0)