If you are here, welcome to C2S2 - we're really excited to have you here! Below we've detailed some of the steps/tasks involved in onboarding, as well as next steps. If there's anything that we can do to improve your experience, don't hesitate to reach out to the team lead
Access
There's a lot of things that you'll get access to as a member of C2S2, which are detailed down below. Definitely take some time to check them out - there's nothing that's "off-limits", so feel free to explore, just maybe check with your subteam lead if you're going to make changes to anything you haven't seen before 
- Confluence: Confluence is where we store our internal documentation. If you're here, then you already have access to it , but try poking around/seeing what's on it, especially if you haven't used Confluence before
- Slack: The C2S2 Slack is the primary communication tool for the team. It is where you can message your subteam, team at large, other specific channels, and individual members. You should have received an invite to join the Slack with your onboarding - if not, definitely reach out to the team lead ASAP.
- Google Drive: C2S2 has a shared Google Drive, which is currently located here. You can also access it by going to your main Google Drive, and clicking "Shared drives" on the left-side panel. Google Drive is used for all of our non-code files, such as presentations, documents, etc. Verify that you have access to the Drive, and feel free to check out some of the things already on there.
- GitHub: C2S2 stores all of its code publicly on GitHub, so that others in the open-source community can benefit from what we're doing. You can view our organization here,but may not be able to contribute just yet; in order to get you set up, make sure to fill out the onboarding form with your GitHub username. You should receive an invitation to the account's associated username shortly after. If you don't already have a GitHub account, you can create one here! You'll likely be using GitHub as part of the team, and no worries if you haven't used it before - we'll be sure to teach you
- Server: C2S2's default development environment is a Linux RedHat server that used to be part of the ECELinux cluster. It will likely take some time to get new members added - the team lead will send out a message once you have been, at which point you can follow the instructions here to access it
- Canvas: C2S2 has a dedicated Canvas page, where formal assignments (such as those for all Project Teams) will be posted. You should be able to view this along with the Canvas pages for the rest of your courses shortly after you enroll in C2S2 as a class (see below)
- ELL Key Card Access: The ELL is the space in the basement of Upson where many Project Teams work, including C2S2. Access is provided through your Cornell ID. The team lead will submit access requests along with your onboarding email; these requests usually get pulled each Wednesday, and updated the following Friday. Long story short: Access may take time to propagate, but you should have it by the Friday following your onboarding email
- If you haven't been to the ELL before, enter Upson Hall from the Engineering Quad entrance. The ELL is the pair of doors immediately to your right. Once you enter, turn left and proceed down the hallway; you should see a small collection of tables on your left where some teams are stationed. C2S2 will be the first table you come across - you'll see our team logo above it. The central tables are shared between the teams, so feel free to work there as well.
Enrollment
Update for first-year/transfer recruits; you will not enroll for credit in the Fall. Check back in the Spring for enrollment information then!
You get credit for being on C2S2! All members should be enrolled in three credits, comprising of 1 credit of ENGRG 1400 and 2 credits of ENGRG 3400, Section 611 (class number 16998 - see here). Note: If you have already taken ENGRG 1400, or have already been on a Project Team, it isn't necessary to take again, and you should just enroll in 3 credits of ENGRG 3400.
If you have any difficulty, please reach out ASAP to the team lead. While the add deadline for Project Teams is September 22nd at 5 p.m., definitely enroll well before then!
Tutorials/Training
Your subteam lead will likely direct you to some tutorials/training to help learn more about your specific tasks, but there are no team-wide mandated trainings. That being said, all of our trainings are available here, and a strongly recommended one for everyone is the Linux Training (especially if you'll be working on the server!)
Next Steps
That covers most of the onboarding! The next steps will be to:
- Attend Your First All-Team Meeting: For Fall 2023, All-Team Meeting are usually held on Saturdays at 11:00 a.m. in Upson 222. This is where the whole team gathers weekly, and where you can hear updates for the team at large, as well as any subteams. We'll have introductions at the first meeting after your onboarding email, so definitely attend! If you are unable to attend, please reach out to the team lead ASAP
- Attend Your Subteam Meetings: You subteam lead has likely setup weekly meetings for the subteam to discuss their tasks more specifically (beyond what you would go into at an All-Team meeting), as well as to organize tasks to get done. Be sure to reach out to them to figure out when and where you're meeting
- Familiarize Yourself With Some Important Contacts
- Get Started On Your Project
- Meet New Friends
- Have Fun!
If you have any questions, concerns, or just want to chat, feel free to reach out. Feel free to also use the Acronyms and Vocabulary page as a great resource if you're ever unfamiliar with a term. Welcome again, and I hope you have a great time on the team!!!