Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Organise the helpdesk for the competition #1407

Open
4 tasks
Tracked by #1409 ...
github-actions bot opened this issue Aug 13, 2024 · 2 comments · May be fixed by srobo/runbook#213
Open
4 tasks
Tracked by #1409 ...

Organise the helpdesk for the competition #1407

github-actions bot opened this issue Aug 13, 2024 · 2 comments · May be fixed by srobo/runbook#213
Assignees
Labels
AO: Mentoring I: Should Have This task is relatively high priority, but we can survive without

Comments

@github-actions
Copy link

Helpdesk is the single-point-of-contact for teams to get help with their robots. We need to plan who will run this on the day as well as the various things it needs to be able to help the teams.

If kit breaks at the competition for teams, we should be prepared to replace it quickly. For that we will need spares readily available. This should be coordinated with the Kit team.

If there is a problem at helpdesk, that those on helpdesk cannot solve, they need to know who to escalate to. There will be different experts depending on the domain of the problem.

An example set of domains are:

  • Rules
  • Event
  • Kit
    • Python API
    • Hardware
    • Competition operations

Note that this list of people should also take into account who is likely to be available.

Required actions:

  • Decide who will run helpdesk
  • Create a list of available subject matter experts
  • Have spare kit available at the competition
  • Train volunteers to run helpdesk

Original

comp/helpdesk

@github-actions github-actions bot added AO: Mentoring I: Should Have This task is relatively high priority, but we can survive without labels Aug 13, 2024
@github-actions github-actions bot added this to the SR2025 Competition milestone Aug 13, 2024
@sedders123
Copy link
Member

Ensure there is a plan for separating used vs charged batteries #1187

@PeterJCLaw
Copy link
Member

@raccube are you able to take this task?

@raccube raccube self-assigned this Jan 8, 2025
@RealOrangeOne RealOrangeOne linked a pull request Jan 8, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AO: Mentoring I: Should Have This task is relatively high priority, but we can survive without
Projects
Status: Todo
Development

Successfully merging a pull request may close this issue.

3 participants