2023-05-25 Leads Meeting Minutes

Daniel Puratich 3 mins

By next leads meeting having Confluence and Asana pages fully up to date and digestible is a huge priority! To be clear: Asana for Tasks and Confluence for Documentation.

All leads play a role in this, please help each other out by giving good feedback. Directors can help out as well here, please ping us for assistance! The Admin Confluence space has been cleaned up. Please check it out and raise any concerns.

Any team who had not already moved their meeting minutes (Electrical, Operations, & Autonomy) I have moved them for you to the meetings space on confluence. Please put future meeting minutes here and ask questions if you are unsure.

With regards to leads meeting minutes we are publishing them in advance and requesting folks to add topics for discussion or announcement. We would like there to be more detail added to items. Specifically which questions do you have that need to be discussed or what information do you want announced to all subteam leads. Further a rough time you anticipate the conversation will take will be very useful in planning our time! Very vague items make it tough for us to plan things out optimally.

Anthony Luo Megan Spee Daniel Puratich Hamza Ali 10 minutes

Following Operations 2023-2024 Goals we will be opening up for nominating people to become ops lead. Process will somewhat follow Promotion Process but we want to get people going here!

Hamza responsible purely for recruitment, onboarding, and finances & internal sponsorship.

Other inquiries (social media, branding, merch, logistics, budget planning etc) defer to anni or megan.

Aidan Bowers (Deactivated) 5 minutes

Follow up from last leads meeting on the progress we’ve made if any.

Daniel Puratich Updated New Member Onboarding recently. Please review!

Megan Spee Daniel Puratich 3 mins

Leads please refer to Team Roster Information asynchronously. Directors are expecting subteam leads to assist in maintaining the team roster. Please ping directors with questions!

Self-hosted Gitlab.

• Moved back into the bay
• Documentation: GitLab Version Control
• Multiple Maintainers

Flight tests should be well documented if using warg equipment. We should follow the flight test request template and we should take good notes during flight debrief so that we are able to accurately look back at flight tests in the past and gain valuable insight (issue from last term).

Megan Spee Is documenting this iirc, please write out an update ?

https://app.asana.com/0/1201848093086346/1203876194646488

^ this asana link is for pilot training program, not for flight testing process.

• Follow through from comp debrief. What is listed are my (Conall) opinions, these are open to discussion.

• Select a number (15?) when necessary for logistics

• Select “core group” (Pilot, GS operator, etc.)

• Fill in other members later

• If you can’t make it the month and week before competition…

Megan Spee May be documenting this as well ? Is there a Confluence page on this ?

https://app.asana.com/0/1201848093086346/1203822536596988

External communications on uwwarg.business

Internal communications on uw.warg.

Which projects need weekly syncs? Who should be present at these syncs and what is the purpose of them?

• Comp drone

  • Design reviews, integration questions, etc could be brought up. Sets a scheduled time where people will be available.

• Antenna tracker (bi-weekly maybe?)

  • sync to make sure that project is on-track and will converge at the same time.

• Test airframes & Flight test planning (bi-weekly opposite antenna tracker?)

  • sync to check what we need to test over the next few weeks and what needs to be done for them. Gets people on-board with knowing when we’ll be setting what up.

Large aircraft follow some convention.

Quadcopters follow some other convention.

What about fixed wings?

https://docs.google.com/spreadsheets/d/15v-RY9S_4Y7X-nNQ2MvUycmwu6jzMIE1FoKBCHgZFA8/edit#gid=0