...

Welcome to WARG

We’re happy to have you on board as our new [position]! To aid your first few days here at WARG, we have created a startup guide that you can refer to to see what your project will be, key contacts, and some steps you’ll have to take.

...

To meet these objectives, we compete annually in the AEAC student competition. For the most recent competition in [date (e.g. 2024 May)], we developed project [name], a [type (e.g. quadcopter aircraft (project Pegasus), fixed wing, VTOL)] aircraft.

[images]

The [name of subteam] subteam is responsible for [subteam responsibilities]. For the [term] term, we are focusing on [general overview]. Your project, involving [a few words], will [explain how the project will help the subteam and WARG in general].

...

•  Start the bootcamp: [link to subteam bootcamp]

...

[THIS IS AN EXAMPLE PLEASE REPLACE. Sahil is writing an old task here as an example of what to do]

Give context

Currently, the firmware bootcamp that WARG uses as a training platform for onboarding new recruits is outdated and lacks succinct documentation. We have received feedback that it is too hard to follow and believe it costs us talent. You will be implementing the firmware application for the bootcamp and writing the associated documentation that new bootcampers will use when completing it.

Specify the action from a broad point of view

Sahil Kale has given direction to make a new bootcamp for the winter 2022 recruitment season. The new bootcamp will have the following requirements

• Introduce individuals to low-level development in the form of protocol development and STM32 peripheral configuration

• Give exposure to our tooling (STM32 Cube IDE, cmake, bash, git)

• Fun to complete, and requiring less than 4 hours of work for a new first year with knowledge of C or C++ to complete

Give concrete next steps

After you are finished onboarding, here are the tasks that will occur:

•  Meet with Sahil Kale and @hardwaredesignerhere to discuss the implementation of the bootcamp from a high level standpoint - what will the bootcampers be implementing and basic electrical architecture
•  Develop the ‘solution’ firmware that other firmware team members will use as the answer key on a development board
•  Work with our EE team to bring up a PCB that members can use for the bootcamp, and validate your firmware on it
•  Write the surrounding documentation required for bootcampers to complete the bootcamp successfully

Appendix

1st week tasks

Onboarding

•  Complete the bootcamp
•  Read WARG policies:
•  Team Charter
•  On Mistakes
•  WARG Equipment for Non-WARG use
•  Bay Code
•  Bay Cleanliness
•  TODO SAFETY LINKS
•  Sleeping
•  Media Release
•  Use of Personally Identifiable Information
•  AI Usage Policy
•  Approach to Documentation
•  Read subteam documentation: [link to documentation]

Project

•  Be assigned a task from your mentor
•  Start the task

Project

[context of project in a few sentences, optional if explained already above]

This projects goals are:

• [some high level goals]

• [it doesn’t have to be complicated, you’ll explain it in detail when you meet]

[images if any]

Useful links

• What do all the acronyms mean? Check it out here: https://uwarg-docs.atlassian.net/l/cp/D2oP5Vjw

• Subteam pages: [link to subteam Confluence homepage]