...
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 13th from 7-8pm (with buffer / bay time after) | |
First General Meeting | Delaney | N/A | |||
Model Rocket! | full weekend, you know the deal | Kyle/Nahvid | September 24th / 25th | E5 2004 / Texas | |
GitHub Tutorial | 1 in-person session | Kavin | |||
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 | ???? | ||||
Intro to rocket integration? | |||||
Plumbing Tutorial | |||||
Timeline
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.
...