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

Teams section update / cleanup #76

Open
wants to merge 20 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 5 commits
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
4c2d60d
Relocate tech days section to programme
RealOrangeOne Jan 25, 2020
6b8904a
Remove section for LTCs
RealOrangeOne Jan 25, 2020
eed8b96
Remove section about kickstart from teams section
RealOrangeOne Jan 25, 2020
0fddc6f
Modernise team allocation process
RealOrangeOne Jan 25, 2020
dadd665
Note that confirming places sooner is better
RealOrangeOne Jan 25, 2020
b3639f5
Modernise tasks for team coordinator
RealOrangeOne Jan 25, 2020
85cd0b3
Rewrite documentation for kit allocation, and note about re-allocatin…
RealOrangeOne Jan 25, 2020
803ac90
Update dropout and reallocation process
RealOrangeOne Jan 25, 2020
98894fd
Collapse section about dropouts when there's not enough time to alloc…
RealOrangeOne Jan 25, 2020
5bd8f9a
Remove existing generic competiton prep page and replace with dedicat…
RealOrangeOne Jan 25, 2020
c653faf
Note about the email lists, and how to send emails
RealOrangeOne Jan 25, 2020
3455198
Fix typo spelling of "incentive"
RealOrangeOne Feb 23, 2020
7b222da
Restore thinned out competition preparation page, as the content didn…
RealOrangeOne Feb 23, 2020
67b6845
Merge remote-tracking branch 'origin/master' into teams-section-cleanup
RealOrangeOne Feb 23, 2020
8c5aea1
Restore original page name
RealOrangeOne Feb 23, 2020
c5b4b90
Cleanup after competition page
RealOrangeOne Feb 23, 2020
5388d56
Remove references to LTCs
RealOrangeOne Feb 23, 2020
de6d1c6
Clarify this
PeterJCLaw Nov 22, 2020
b9c3667
Fix pronoun
PeterJCLaw Nov 22, 2020
80acda9
Merge branch 'master' into teams-section-cleanup
PeterJCLaw Nov 22, 2020
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/programme/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,6 @@ Ancillary Software Coordinator |
## Things

* Kickstart
* [Review process](/programme/kickstart/review)
* [Review process](./kickstart/review.md)
* Competition
* Tech Days
* [Tech Days](./tech-days.md)
File renamed without changes.
2 changes: 1 addition & 1 deletion docs/teams/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,5 +6,5 @@ them.

Generally a single person (the Team Coordinator) takes on the overall
responsibility for teams, though during the competition year it is often
advantageous to delegate geographical areas to other volunteers to ensure prompt
advantageous to delegate to other volunteers to ensure prompt
responses to enquiries and avoid overloading a single person.
74 changes: 19 additions & 55 deletions docs/teams/allocating-teams.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,69 +3,33 @@ original:
authors: Fiona Gillan
url: https://github.com/fgillan/sr-team-coord/wiki/Allocating-teams
---
## Allocating Teams

* Transfer data from the Google Form of Team Applications into spreadsheet, and populate new spreadsheet ‘SR Year Teams’ with following info, in chronological order:
* Team Leader Name
* Email address
* Phone number
* Organisation
* Organisation address
* Organisation postcode
* TLA
* Rookie
* LTC
* LTC Area
* LTC Email address
# Allocating Teams

### Required information

* Remove duplicate applications, keeping a record of the duplicate applications in case it is possible to allocate more than one team to an organisation.
* Consult Team Archive to establish whether the team is (i) a rookie, (ii) obtain previous TLA.
* If rookie team, need to allocate a new TLA, taking care to ensure that it has not been used previously.
When collecting information from teams, the following information must be collected:

* Team Leader Name
* Team Leader Email address
* Team Leader Phone number
* Organisation
* Organisation address
* Organisation postcode
* Desired kickstart location
* Whether the organisation would benefit from a second kit / team

* Plot geographical location of allocated teams using postcode.
* Plot geographical location of LTCs.
* Divide teams up aiming for geographical areas with equal numbers of teams in each LTC area.
* Enter the LTC information on to ‘SRYear Teams’ spreadsheet.
Once teams have been registered, allocate them a TLA. This TLA must be unique for all teams this competition year, be based roughly on their organisation name, and not be construed for rude language. If a team has competed before, re-use their previously allocated TLA. If a TLA was previously given to a different organisation, calculate a new one.

If this is the first year a given institution is competing, they are considered a rookie. This should also be noted with the rest of their team information.

* Produce spreadsheets for relevant people:
* ‘User account info’ including: Team Leader Name, Team Leader Email address, Organisation, TLA. Share with person in charge of user account info.
* A spreadsheet for each LTC containing the info for the teams for whom they are responsible: Team Leader Name, Email address, Phone number, Organisation, Organisation Address, Postcode, TLA, Rookie.
* ‘Kickstart Teams’ for Kickstart Coordinator: TLA, Organisation, Postcode, LTC Area, LTC, LTC Email address.
## Confirming places

* Send ‘Team Leader Intro’ email via MailChimp to successful Team Leaders including following information:
* Kickstart info
* User account info
* Inform re. TLA (using info from ‘SRYear Teams’ spreadsheet)
* Inform re. allocated LTC
* Advice re. seeking help – i.e website, forum, LTC, Mentor, Team Coordinator
* Explain re. SR being a volunteer-run organisation.
Once signup has closed, teams need to be informed they have a place in the year's competition.

## Example of email sent in 2017
If possible, confirm places in batches before the deadline, rather than all at once after the deadline. This provides an insentive for signing up sooner, as it confirms places quicker, enabling team leaders to organise kickstart trips with more notice.

> Congratulations – your team has been allocated a place for Student Robotics 2017! (I am aware that you may have applied for more than one place as you were hoping to have more than one team, however, due to demand for this year’s competition we have only been able to allocate one team per organisation.)
>
> So, what happens next?
> Our volunteers are busy planning this year’s Kickstart event where you will be introduced to the SR Programme and receive your SR kit. It will be held on 15th October, 2016 at various locations around the UK. You will be notified which Kickstart event you have been assigned to attend over the next few days.
> Throughout the SR Programme your team members will require access to SR services. Therefore, you, as Team Leader, will shortly receive an email containing your SR username and password which will enable you to create user accounts for your team members.
>
> Each team has been assigned a Three Letter Abbreviation (TLA) for ease of communication.
>
> Your TLA is:
>
> Each team has been allocated a Local Team Co-ordinator (LTC) based roughly on your geographical location. Your LTC will be your main point of contact guiding you through the SR Programme. (If you’ve competed before, you may notice that we have reorganised the way in which we provide support/communication.)
>
> Your LTC is:
>
> We are aware that you are all extremely busy people and there is often a great deal of work involved in the logistics of organising a team to enter. Therefore we will endeavour to notify you of information as soon as it is feasibly possible. However, please do bear in mind that Student Robotics is a volunteer-run organisation and, as such, the work is done in people’s spare time leading to some delays occasionally, during which we would appreciate your patience.
>
> If you have any queries from now on, please do the following:
> 1. Look on the website.
> 2. Post on the forum (once you’ve received your SR user account information) NB. Please do not post sensitive personal information on the forum as this is publically accessible. The forum is a great way to share information and get answers to your questions - if you’re wondering about something, chances are someone else is too or has done and posted on the forum – you’ll hear more about this resource at Kickstart.
> 3. Email your Local Team Coordinator.
> 4. Ask your Mentor – this is something your LTC can help with organising. (Ideally all teams would have a Mentor to help with the technical aspects of the Programme. We have a limited number of volunteers who are available to mentor teams, but if there’s not one near to you, we can help support you to find your own from local industry etc.)
> 5. If after all that your query still has not been answered email me, Fiona at [email protected].
### Example emails

> We’re very excited to have your team participating in this year’s competition and look forward to hopefully seeing you and your team at Kickstart in October!
* [SR2020](https://github.com/srobo/team-emails/blob/master/SR2020/2019-09-25-confirm-competition-place.md)
* [SR2019](https://github.com/srobo/team-emails/blob/master/SR2019/2018-10-10-place-confirmation.md)
9 changes: 0 additions & 9 deletions docs/teams/kickstart.md

This file was deleted.

52 changes: 0 additions & 52 deletions docs/teams/managing-ltcs.md

This file was deleted.