This Page is for planning out our most unified, informative, and engaging fall recruitment / onboarding process ever!
Recruitment
Sessions We Will Run
Session / Tutorial | Format | Lead | Assisted By | Date(s) | Location |
|---|---|---|---|---|---|
Student Design Team Showcase | Chill at the bay and talk to students | Zach (Not that there is much to lead) | As many people as possible | September 7th from 3-5pm | The Bay / SDC |
Info Session | 1 1h? meeting | Delaney | Technical leads, others free to come hang out. | September 14th from 7-8pm (with buffer / bay time after) | E7 4417 |
First General Meeting | usual 1h meeting, go to bay afterwards | Delaney | N/A | 2004 PLZ | |
Model Rocket! | full weekend, you know the deal | Nahvid with advisory/help from kyle | Anyone who can | September 24th / 25th | E5 2004 / Texas |
GitHub Tutorial | 1 in-person session | Kavin | Anyone who knows Git | ||
KiCAD Tutorial | 2? in-person sessions, follow along at home guide | Chamath | Zach, Jared officially, anyone else who knows KiCAD appreciated | ||
Electronics 101 tutorial | ??? about ours, or electronics in general? | Jared | Zach, Chamath? | ||
RocketCAN tutorial | 1 1-2h presentation | Zach | |||
SolidWorks tutorial | ???? | Francis? | |||
Rockets for Dummies | After a general meeting | Roman | |||
Plumbing Tutorial | hands on but mostly ??????? | Michel | |||
Composites tutorial | material prep the day before, a few hours? day of | Gavin | Sept 23rd | ||
Events for 1st years to help with
Event | When | |
|---|---|---|
Cold flow? | ||
Async 1 on 1 learning to do
Thing | Main Person | Others who can run |
|---|---|---|
Soldering | Zach | |
Firmware | ||
Sewing | ||
Timeline
Week | Events |
|---|---|
Sept 5-11 | Showcase |
Sept 12-18 | Info Session |
Sept 19-25 | Composites tutorial, Model Rocket |
Sept 26 - Oct 2 | Git, Electronics 101 |
Oct 3-9 | |
Oct 10-16 | Reading Week |
Oct 17-23 | Midterms ( for Zach) |
Oct 24-30 | 1st year Midterms? |
Documentation
Currently the team manual is quite long and dense, I want to split it up into a series of shorter pages that make the info more approachable. This stuff also isn’t for some government contract, it’s for new members who are here to have fun and learn, so we should write it that way. As long as it’s generally respectful and easy to follow, it’s ok if you have jokes or write in the first person, documentation is often much more interesting if it reads somewhat like a novel.
Potential New structure: starts from a big link on the home page
Welcome to waterloo rocketry! (a bit about the team, what we do)