Difference between revisions of "Satellite Software"
(Created page with "🌲") |
|||
Line 1: | Line 1: | ||
− | + | Satellites software is responsible for writing the code to operate our satellite-related projects. Currently, the team is working on writing the flight software and payload code for Sequoia (see [[Sequoia Technical Overview]]). | |
+ | |||
+ | ==Onboarding== | ||
+ | ===Basics=== | ||
+ | 1. Join the SSI slack, and the #satellites and #satellites-software channels. Joining #satellites-systems is optional, if you want to receive info on systems level discussions. | ||
+ | |||
+ | 2. Come to meetings Thursdays at 6:30 PST. | ||
+ | |||
+ | 3. Create a github account (www.github.com) and DM @langston and @moritz (the software co-leads) your username | ||
+ | |||
+ | 4. Also message @langston and @moritz your Stanford email, so you can get added to the Google Drive. | ||
+ | |||
+ | 5. Read [[Sequoia Technical Overview]] to get a broad understanding of our systems. Don't worry if you can't understand it all. |
Revision as of 19:02, 13 September 2020
Satellites software is responsible for writing the code to operate our satellite-related projects. Currently, the team is working on writing the flight software and payload code for Sequoia (see Sequoia Technical Overview).
Onboarding
Basics
1. Join the SSI slack, and the #satellites and #satellites-software channels. Joining #satellites-systems is optional, if you want to receive info on systems level discussions.
2. Come to meetings Thursdays at 6:30 PST.
3. Create a github account (www.github.com) and DM @langston and @moritz (the software co-leads) your username
4. Also message @langston and @moritz your Stanford email, so you can get added to the Google Drive.
5. Read Sequoia Technical Overview to get a broad understanding of our systems. Don't worry if you can't understand it all.