Add area owners to kickstart and pre

prophile · prophile · commit 38bfb7b14d65 · 2023-02-07T23:18:13.000Z
diff --git a/kickstart/advertise-volunteers.yaml b/kickstart/advertise-volunteers.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: volunteer-coordination
+
 description: >-
     We need to advertise the existence of the kickstart to people who might want
     to help run it.
diff --git a/kickstart/allocate-tlas.yaml b/kickstart/allocate-tlas.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: teams
+
 description: >-
     Once we've decided which teams are getting places we need to assign them
     their TLAs.
diff --git a/kickstart/appoint-safeguarding-officers.yaml b/kickstart/appoint-safeguarding-officers.yaml
@@ -6,5 +6,7 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: health-safety
+
 description: >-
     Safeguarding officers need to be appointed, by the Safeguarding Lead, as per the safeguarding policy.
diff --git a/kickstart/confirm-teams.yaml b/kickstart/confirm-teams.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: teams
+
 description: >-
     We need to inform the teams who have places and invite them to the Kickstart
     venue most suitable for them.
diff --git a/kickstart/decide-presenters.yaml b/kickstart/decide-presenters.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: production
+
 description: >-
     The presentation needs to be given at each venue, so will be presented by
     multiple people. It's recommended the person who creates the presentation be one of the people to
diff --git a/kickstart/kit/allocate.yaml b/kickstart/kit/allocate.yaml
@@ -6,6 +6,8 @@ component: Kit
 
 milestone: $SRYYYY Kickstart
 
+area-owner: kit
+
 description: >-
     Teams will want kits at Kickstart so we need to know which kits to
     give to each team.
diff --git a/kickstart/kit/fix.yaml b/kickstart/kit/fix.yaml
@@ -6,6 +6,8 @@ component: Kit
 
 milestone: $SRYYYY Kickstart
 
+area-owner: kit
+
 description: >-
     We need to have confidence that the kits we'll hand out at the $SRYYYY
     Kickstart are going to work for the teams. Once tested they may need
diff --git a/kickstart/kit/main.yaml b/kickstart/kit/main.yaml
@@ -6,6 +6,8 @@ component: Kit
 
 milestone: $SRYYYY Kickstart
 
+area-owner: kit
+
 description: >-
     We need to have kits to hand out at the $SRYYYY Kickstart.
 
diff --git a/kickstart/kit/ship-courier.yaml b/kickstart/kit/ship-courier.yaml
@@ -6,6 +6,8 @@ component: Kit
 
 milestone: $SRYYYY Kickstart
 
+area-owner: kit
+
 description: >-
     Teams unable to make it to a Kickstart need their kits couriering to
     them.
diff --git a/kickstart/kit/ship-kickstarts.yaml b/kickstart/kit/ship-kickstarts.yaml
@@ -6,6 +6,8 @@ component: Kit
 
 milestone: $SRYYYY Kickstart
 
+area-owner: kit
+
 description: >-
     Teams will want kits at Kickstart so we need to ship the relevant kits
     to each of the Kickstart venues.
diff --git a/kickstart/kit/ship-overseas.yaml b/kickstart/kit/ship-overseas.yaml
@@ -6,6 +6,8 @@ component: Kit
 
 milestone: $SRYYYY Kickstart
 
+area-owner: kit
+
 description: >-
     Teams overseas need their kits shipped to them. This has mostly been
     the German teams in the past few years, which have been shipped together
diff --git a/kickstart/kit/test.yaml b/kickstart/kit/test.yaml
@@ -6,6 +6,8 @@ component: Kit
 
 milestone: $SRYYYY Kickstart
 
+area-owner: kit
+
 description: >-
     We need to have confidence that the kits we'll hand out at the $SRYYYY
     Kickstart are going to work for the teams.
diff --git a/kickstart/kit/update-disclaimer-forms.yaml b/kickstart/kit/update-disclaimer-forms.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: kit
+
 description: >-
     As the kits contain valuable and potentially dangerous components, many of
     which are not CE marked, we normally ask the team leaders to sign a form
diff --git a/kickstart/main.yaml b/kickstart/main.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: committee
+
 description: >-
     We need to have the $SRYYYY Kickstarts.
 
diff --git a/kickstart/markers.yaml b/kickstart/markers.yaml
@@ -6,6 +6,8 @@ component: Rules
 
 milestone: $SRYYYY Kickstart
 
+area-owner: game
+
 description: >-
     We need to generate the fiducial markers used for the $SRYYYY game
     and add them to https://github.com/srobo/game-markers.
diff --git a/kickstart/microgames.yaml b/kickstart/microgames.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: mentoring
+
 description: >-
     At Kickstart we usually have the teams perform some introductory tasks to
     get them familiar with the kit and to establish that they can safely charge
diff --git a/kickstart/prepare-news-afterwards.yaml b/kickstart/prepare-news-afterwards.yaml
@@ -6,6 +6,8 @@ component: Website
 
 milestone: $SRYYYY Kickstart
 
+area-owner: media-press
+
 description: >-
     After the kickstart we want to have a news article which describes how the
     event went and continues to build up the excitement around the comptition.
diff --git a/kickstart/print-disclaimer-forms.yaml b/kickstart/print-disclaimer-forms.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: kit
+
 description: >-
     As the kits contain valuable and potentially dangerous components, many of
     which are not CE marked, we normally ask the team leaders to sign a form
diff --git a/kickstart/publish-news-afterwards.yaml b/kickstart/publish-news-afterwards.yaml
@@ -6,6 +6,8 @@ component: Website
 
 milestone: $SRYYYY Kickstart
 
+area-owner: media-press
+
 description: >-
     After the kickstart we want to have a news article which describes how the
     event went and continues to build up the excitement around the comptition.
diff --git a/kickstart/remind-teams.yaml b/kickstart/remind-teams.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: teams
+
 description: |
     We need to remind team leaders that the kickstart is happening, communicate
     the final details and encourage them to prepare for it on their end.
diff --git a/kickstart/remind-volunteers.yaml b/kickstart/remind-volunteers.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: volunteer-coordination
+
 description: >-
     We need to remind volunteers that the kickstart is happening and communicate
     the final details: who is doing what, at what venue, what time to arrive, etc.
diff --git a/kickstart/rules/decide-game.yaml b/kickstart/rules/decide-game.yaml
@@ -6,6 +6,8 @@ component: Rules
 
 milestone: $SRYYYY Kickstart
 
+area-owner: game
+
 description: >-
     The $SRYYYY game will be different than the previous year's, so we
     need to decide what it will be.
diff --git a/kickstart/rules/write.yaml b/kickstart/rules/write.yaml
@@ -6,6 +6,8 @@ component: Rules
 
 milestone: $SRYYYY Kickstart
 
+area-owner: game
+
 description: >-
     We need to have a game to play in $SRYYYY. It will be different than
     the previous year's, so the rules need updating.
diff --git a/kickstart/send-disclaimer-forms.yaml b/kickstart/send-disclaimer-forms.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: kit
+
 description: >-
     As the kits contain valuable and potentially dangerous components, many of
     which are not CE marked, we normally ask the team leaders to sign a form
diff --git a/kickstart/services/forums.yaml b/kickstart/services/forums.yaml
@@ -6,6 +6,8 @@ component: sysadmin
 
 milestone: $SRYYYY Kickstart
 
+area-owner: mentoring
+
 description: >-
     In order to allow the competitors to chat to each other and request help
     from mentors, we setup forums each year. These are typically an instance
diff --git a/kickstart/services/ide.yaml b/kickstart/services/ide.yaml
@@ -6,6 +6,8 @@ component: sysadmin
 
 milestone: $SRYYYY Kickstart
 
+area-owner: mentoring
+
 description: >-
     In order to enable the competitors to program their robots, we provide a
     hosted IDE for them to work in.
diff --git a/kickstart/services/main.yaml b/kickstart/services/main.yaml
@@ -6,6 +6,8 @@ component: sysadmin
 
 milestone: $SRYYYY Kickstart
 
+area-owner: mentoring
+
 description: >-
     We provide a hosted IDE and online forums to the teams to use during the
     year. Typically the microgames at Kickstart get the competitors using these,
diff --git a/kickstart/services/user-accounts/mentors.yaml b/kickstart/services/user-accounts/mentors.yaml
@@ -6,6 +6,8 @@ component: sysadmin
 
 milestone: $SRYYYY Kickstart
 
+area-owner: mentoring
+
 description: >-
     In order to allow mentors to use the various hosted services we provide, in
     order for them to help competitors, we need to give them user accounts.
diff --git a/kickstart/services/user-accounts/team-leaders.yaml b/kickstart/services/user-accounts/team-leaders.yaml
@@ -6,6 +6,8 @@ component: sysadmin
 
 milestone: $SRYYYY Kickstart
 
+area-owner: mentoring
+
 description: >-
     In order to allow the competitors to use the various hosted services we
     provide, we need to give them user accounts.
diff --git a/kickstart/signups-volunteers.yaml b/kickstart/signups-volunteers.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: volunteer-coordination
+
 description: >-
     We need to get potential volunteers to sign up to help organise the
     kickstart.
diff --git a/kickstart/update-api.yaml b/kickstart/update-api.yaml
@@ -6,6 +6,8 @@ component: pyenv
 
 milestone: $SRYYYY Kickstart
 
+area-owner: kit
+
 description: >-
      The `sr.robot3` API needs updating to contain the marker details for
      the $SRYYYY game.
diff --git a/kickstart/update-dummy-api.yaml b/kickstart/update-dummy-api.yaml
@@ -6,6 +6,8 @@ component: pyenv
 
 milestone: $SRYYYY Kickstart
 
+area-owner: kit
+
 description: >-
     The [dummy API](https://github.com/srobo/pyenv-dummy) needs
     updating to contain the marker details for the $SRYYYY game.
diff --git a/kickstart/update-simulator.yaml b/kickstart/update-simulator.yaml
@@ -6,6 +6,8 @@ component: Rules
 
 milestone: $SRYYYY Kickstart
 
+area-owner: simulator
+
 description: >-
     The $SRYYYY game will be different to that for the previous year,
     so the arena template in the simulator will need updating.
diff --git a/kickstart/venues.yaml b/kickstart/venues.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: event-logistics
+
 description: >-
     In order to have the $SRYYYY Kickstarts we need venues to have it in.
 
diff --git a/kickstart/website/archive-previous-rules.yaml b/kickstart/website/archive-previous-rules.yaml
@@ -6,6 +6,8 @@ component: Website
 
 milestone: $SRYYYY Kickstart
 
+area-owner: game
+
 description: >-
     Move the rules from the [rules](https://studentrobotics.org/docs/rules) page
     to the [game archive](https://studentrobotics.org/docs/rules/archive) in the
diff --git a/kickstart/website/docs.yaml b/kickstart/website/docs.yaml
@@ -6,6 +6,8 @@ component: Docs
 
 milestone: $SRYYYY Kickstart
 
+area-owner: kit
+
 description: >-
     The docs will need updating to match the new API for the $SRYYYY API and
     game, specifically https://studentrobotics.org/docs/programming/sr/vision/
diff --git a/kickstart/website/main.yaml b/kickstart/website/main.yaml
@@ -6,6 +6,8 @@ component: Website
 
 milestone: $SRYYYY Kickstart
 
+area-owner: media-press
+
 description: >-
     The website will need updating for $SRYYYY.
 
diff --git a/kickstart/website/publish-rules.yaml b/kickstart/website/publish-rules.yaml
@@ -6,6 +6,8 @@ component: Website
 
 milestone: $SRYYYY Kickstart
 
+area-owner: game
+
 description: >-
     These need building and the website patching.
     The [rules](https://studentrobotics.org/docs/rules) page will need updating
diff --git a/kickstart/write-presentation.yaml b/kickstart/write-presentation.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Kickstart
 
+area-owner: production
+
 description: |-
     Kickstart events require a presentation to go through what student robotics
     is, what the competition cycle looks like, and details of the game.
diff --git a/pre/advertise-teams.yaml b/pre/advertise-teams.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Preparation
 
+area-owner: teams
+
 description: >-
     We need to advertise the existence of the competition programme to people
     who might want to take part.
diff --git a/pre/advertise-volunteers.yaml b/pre/advertise-volunteers.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Preparation
 
+area-owner: volunteer-coordination
+
 description: >-
     We need to advertise the existence of the competition programme to people
     who might want to help run it.
diff --git a/pre/budget.yaml b/pre/budget.yaml
@@ -6,5 +6,7 @@ component: Competition
 
 milestone: $SRYYYY Preparation
 
+area-owner: committee
+
 description: >-
     We need to prepare a budget for the $SRYYYY Competition Programme.
diff --git a/pre/main.yaml b/pre/main.yaml
@@ -6,6 +6,8 @@ component: Competition
 
 milestone: $SRYYYY Preparation
 
+area-owner: committee
+
 description: >-
     We need to prepare for the $SRYYYY Competition Programme.
 
diff --git a/pre/signups-teams.yaml b/pre/signups-teams.yaml
@@ -6,5 +6,7 @@ component: Competition
 
 milestone: $SRYYYY Preparation
 
+area-owner: teams
+
 description: >-
     We need to get potential teams to sign up to take part in the competition.
diff --git a/pre/signups-volunteers.yaml b/pre/signups-volunteers.yaml
