srobo / competition-team-minutes Goto Github PK

Ideally not long after competition is announced, website needs to have the normal splash page back and a news article or two repeating the competition announcement and containing details for kickstart.

From https://github.com/srobo/core-team-minutes/blob/master/2018/2019-02-06.md#specific

From https://github.com/srobo/core-team-minutes/blob/master/2018/2018-07-24.md#general

blocking on: #47

We need to ship the team kits to the London venue

From https://github.com/srobo/core-team-minutes/blob/master/2018/2019-02-06.md#specific

We have (or are just about to) tell teams where to go, we need to confirm they're going there.

We should also get the team leader phone numbers when they confirm! so we can chase them up if they no-show

The usual risk assessments need to be produced before the event.

From https://github.com/srobo/core-team-minutes/blob/master/2018/2018-08-14.md#action-points

Assumption list: https://docs.google.com/document/d/1TUWtD6siLcqFc1XXdW9nq0dqFxa7L39hwakIA28F1PM/edit

From https://github.com/srobo/core-team-minutes/blob/master/2018/2018-08-14.md#action-points

From an SR email address, letting them know what our plans are for SR2019.

From: https://github.com/srobo/core-team-minutes/blob/master/2018/2018-08-14.md#action-points

Announce competition date and venue, and kickstart details to volunteers.

From: https://github.com/srobo/core-team-minutes/blob/master/2018/2018-08-08.md#action-points

Normally we give team leaders a legally worded form which teams have to sign to receive a kit. This is because the kits aren't CE marked, so we need them to sign a form saying they won't sue us if they get hurt.

The only modifications really needed are the year and the logo, everything else should be fine.

I can't find a link to the SR2017 forms sadly, so that will need doing.

From https://github.com/srobo/core-team-minutes/blob/master/2018/2019-02-06.md#specific

We need signage to lead teams to parking, the intro talk, and possibly the micro-games.

We have 3 metal signs which I think fit A1 paper.

Load it up with working code, so we can actually have a working demo at kickstart for the first time ever.

We need one of these in each venue

From https://github.com/srobo/core-team-minutes/blob/master/2018/2019-02-06.md#specific

We need to announce what the awards will be for the competition, so the teams know what they're working towards.

IIRC we usually have:

• 1st place
• 2nd place
• 3rd place
• Trustees award (Core Team award?)
• Robot and Team Image
• Online presence
• Rookie award
• First Robot Movement (rookies only)

With competition and kickstart dates.

Blocks on #10

Once competition is announced we'll invite trustees to a core team meeting to clarify fundraising expectations from both trustee and core team point of view - particularly as SR2019 funding is tight this is rather important for the longer term.

Discussed in https://github.com/srobo/core-team-minutes/blob/master/2018/2018-08-22.md

General mailshot announcing that cogs are in motion for SR2019, and where to go to see what's going on (and help out).
Need to think carefully about what goes into this as the announcement channel should be used sparingly.

• Do we ask feedback (in a Google Form) for who is interested in mentoring, events, development, organisation etc.?
• Do we rekindle the googlegroup (or suitable alternative) separately before this goes out?

We should retrospect on the first major phase of the Core Team's duties to see what worked well and what we can improve on. This includes:

• our pre-year planning
• the competition announcement
• the kickstart event

From https://github.com/srobo/core-team-minutes/blob/b86168193989a762a3b1c2d502bfb80783e2e41b/2018/2018-11-13.md#specific

Need to contact @jimmythompson to get the credentials to our social media accounts so that we can start using them.

From: https://github.com/srobo/core-team-minutes/blob/master/2018/2018-08-08.md#action-points

We need to announce the game in a super flashy way.

Also please note this presentation will be given by 2 different people, so the creator needs to brief the other venue.

A few similar presentations to look at:

• SourceBots 2018
• SR2017 southampton (scroll to game section)

See group email thread "Notes on venue requirements".

From https://github.com/srobo/core-team-minutes/blob/master/2018/2018-08-14.md#action-points

Lots of teams miss out on the intro presentation, most teams really should be able to see it, and we're able to livestream competitions now, so surely we should be able to livestream/record Kickstart.

It's worth noting we don't have media consent at kickstart, so camera angles need to avoid seeing students.

We absolutely must have enough working kits for the number of teams we intend to invite to participate.

We therefore need to know how many kit pieces we have in working order, ideally before we confirm places to teams.

Will probably look like:

• Gathering teams
• Intro talk
• Game talk
• Lunch & speak to blueshirts about robot designs (this went well in SourceBots)
• Pick up kits (This has to be done VERY carefully to avoid crowding, just take the team leaders up, teams should stay still)
• Microgames
• Go Home

This task is to flesh out the above, and give them times.

Previous years:

• SR2016 Kickstart schedule

We need to decide whether we want to host a forum for teams for the SR2019 cycle.

If we do, then we need to decide whether we self-host or not.
If the latter we need to work out how (and if) we want to identify competitors vs team leaders and who is in which team.

See also #34 (Python 3) and #35 (Odroid OS).

Presently this is London and Southampton, provisionally 10th November. Needs to be confirmed

There is no cake :(

• We need to bring new teams up to speed with our kits
• The most important tasks should be first (i.e. safely charging a battery)
• Have advanced tasks at the end for the advanced teams.

Previous years:

• SourceBots 2018 (can't find the link :( )
• SR2017
• SR2016
• SR2015

We should find some good Saturdays for tech days, aim for 1 per month, so 4 in total.

Space them out nicely, bearing in mind that teams don't do much at the start of the competition, and that teams are less likely to turn up in the middle of school breaks.

We're unfortunately not able to offer these this year, however it appears that we may have overlooked some mentions on the website. While @prophile will be getting in touch with the teams who have enquired about them, we should remove the mentions as soon as we can.

https://github.com/srobo/core-team-minutes/blob/b86168193989a762a3b1c2d502bfb80783e2e41b/2018/2018-11-13.md#specific

From https://github.com/srobo/core-team-minutes/blob/master/2018/2019-02-06.md#specific

Looking through past years here's the points which are usually covered:

1. What student robotics is
2. Who the volunteers are
3. Schedule for the year
   • How long the competition is
   • Tech days date, time, etc..
   • Competition date, time, etc..
4. General robot design tips
5. Health and safety
   • How to charge your batteries
6. What the awards are

Don't forget to put a slide at the end including the schedule for the day!

Also please note this presentation will be given by 2 different people, so the creator needs to brief the other venue.

Here are some previous presentations to copy ideas from:

• SourceBots 2018
• SR2017

From https://github.com/srobo/core-team-minutes/blob/master/2018/2018-07-24.md#specific

This is something that we should do, however it needs investigation into whether it is possible to achieve. If it looks unlikely then in the interests of delivering a stable kit we should not rush this.

From https://github.com/srobo/core-team-minutes/blob/master/2018/2019-02-06.md#specific

This is something that we should do, however it needs investigation into whether it is possible to achieve. If it looks unlikely then in the interests of delivering a stable kit we should not rush this.