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

Conversation

RealOrangeOne
Copy link
Member

Go through and update the teams section for how we do things currently, along with consolidate and cleanup content.

The primary change was the removal of LTCs. I went with the option of removing things outright, although I'd be open to creating a page describing what they were, and that we don't operate things like that anymore.

@trickeydan
Copy link
Contributor

Whilst this section is being cleaned up, it might be good to try and distinguish between competitor and SR teams. It is currently ambiguous.

@RealOrangeOne
Copy link
Member Author

distinguish between competitor and SR teams

Almost everything SR do revolves around the word "teams" being the competitor variety. Besides #77, it doesn't really come up having to group the committees and their respective teams together with a collective term, and even when it does, it's generally talking about the committees, which is a non-issue, referring to them as "the committees".

@@ -0,0 +1,25 @@
# Kickstart
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe on this page also link to the general Kickstart page?

@@ -0,0 +1,25 @@
# Kickstart
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe on this page also link to the general Kickstart page?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There isn't one. There's a page on reviewing kickstarts, but no page on kickstarts themselves.

(There definitely should be one, but that's OOS)

Comment on lines -10 to -18
## Information about the competition

Liaise with Competition Coordinator about information that they would like relayed to the Team Leaders prior to the competition and send email via MailChimp Team Leaders mailist. To include information such as the following:

1. Teams should bring some laptops as we will not be providing any computers/laptops.
2. Teams should bring any tools that they require to work on their robot while at the competition as we will not be providing any tools.
3. All of the kit must be returned at the end of the competition (including the white box it comes in). If a team wishes to keep the kit for a little longer they must email [email protected] ASAP to request a loan extension. Any team that has not been granted a loan extension before the start of the competition will have to return all of the kit before they leave on Sunday.
4. Teams should have a good read of section 2.8 and Appendix B of the rules (Safety regulations). All robots will undergo a safety inspection and will not be allowed to compete until they pass this inspection.
5. Please do let us know if your team has any special requirements with regards to disability access or other matters that need to be accommodated.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Much of this information seems still relevant and useful, just to check: have we captured this somewhere else now we're dropping it from here?

@PeterJCLaw
Copy link
Member

Thanks for doing this. Overall the changes seem good, though there are some remaining references to LTCs which maybe should be dropped too? (notably on the "After competition" page)

@@ -0,0 +1,11 @@
---
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please could we keep this page at its original name? (competition-preparation.md)

Aside from making the diff easier to read, it's not especially clear what "preparation" this document currently refers to.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I had imagined this staying under teams, rather than competition/teams (I hadn't spotted it had also moved).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've not looked around for other similar information, though my gut feel is that this probably belongs in the teams section more than the competition section (I think mostly because it's not really new information about the competition?). I don't know what's best though.

I guess a comparison would be where similar information related to a tech day or kickstart would be and what the other information in this competition/teams section is.

Up to you 🤷‍♂️.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My intention is to go through the competition section after this and tidy things up a bit.

My thoughts around the competition/ section was to show things related to the competition itself, which IMO this is. I guess competition/teams is the union of teams/ and competition/.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I see the "competition" section as being mostly about the Competition event itself. I do think we perhaps need a clearer way to group things which are about the more general competition year though.

This is mostly based on the way the existing docs were structured though.

Mentoring content reads a little weird, but should be being written in the not-too-distant future
@@ -3,14 +3,6 @@ original:
authors: Fiona Gillan
url: https://github.com/fgillan/sr-team-coord/wiki/After-competition
---
## Kit Return
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe worth keeping a comment here with a brief summary of kit return? Perhaps just that it happens at the competition event and that extended loans exist, but cross linking to the relevant other section?

docs/teams/mentoring.md Outdated Show resolved Hide resolved
docs/teams/mentoring.md Outdated Show resolved Hide resolved


* Once replies obtained, make ‘Mentor Sign-Up’ spreadsheet with this info and share with LTCs so that they can review and match Mentors with their teams.
* Once replies obtained, make ‘Mentor Sign-Up’ spreadsheet with this info and match Mentors with their teams.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Once replies obtained, make ‘Mentor Sign-Up’ spreadsheet with this info and match Mentors with their teams.
Once we have the replies, make ‘Mentor Sign-Up’ spreadsheet with this info and match Mentors with their teams.
The steps are then:

Maybe also clarify whether that's replies from volunteers or from teams (or is it both?)

@@ -0,0 +1,11 @@
---
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've not looked around for other similar information, though my gut feel is that this probably belongs in the teams section more than the competition section (I think mostly because it's not really new information about the competition?). I don't know what's best though.

I guess a comparison would be where similar information related to a tech day or kickstart would be and what the other information in this competition/teams section is.

Up to you 🤷‍♂️.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants