Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

 Confluence & Asana Cleanup Announcement

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.

 Status of Operations Announcement

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 Ali responsible purely for recruitment, onboarding, and finances & internal sponsorship.
Other inquiries, including social media, branding, merch, logistics, budget planning, and everything else defer to Anthony Luo or Megan Spee .🔥

 Onboarding Procedures Discussion

Aidan Bowers (Deactivated) 5 minutes

Create action plan for handling this if necessary.

Anthony Luo following bootcamp process is confusing for onboarding. Discord messages get lost. More forms. Aidan has ideas. Daniel Puratich will follow up.

 Team Roster Maintennance Announcement

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!

 Mech solution for PDM Follow-up

Self-hosted Gitlab: GitLab Version Control

Conall Kingshott Nathan Green Setup with GitLab on university servers. UWFM and Formula Electric possibly got solidworks PDM. We could investigate.

 Flight Test Process Announcement

Flight tests should be well documented if using warg hardware at the flight test. 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).

Anthony Luo Tough to tell bc not proper RCAs and not following the template. Lots of info is lost when templates not run. We should get a flight test coordinator, subteam lead or PM. Flight test coordinator for booking and coordinator other people to handle admin tasks.

flight test coordinator is the go-to person for logistics + getting people to the flight test and assessing availability of pilots.

flight test lead is the person who requests the flight test. Is someone on a sub-team level who can request what content they want out of the flight test.

 Email Organization Announcement
  • External communications on uwwarg.business

    • Non leads have the business account

    • sponsorships go to uwwarg.business

    • has 2fa to Hamza Ali ‘s phone, we’d like to nominate someone to also have this

  • Internal communications on uw.warg.

    • only leads have the uw.warg one

    • Contacting competition people should go to uw.warg

 Weekly Sync Meetings Announcement

Anthony Luo In the past some were useful and some were useful.

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.

 Aircraft Naming Ideas Discussion

Anthony Luo 5 mins

  • Large aircraft follow some convention.

    • We all seem on board for mythical creatures

  • Quadcopters follow some other convention.

    • more city state pairs?

  • What about fixed wings?

    • more yogurt?

Aircraft manual writeups Andy Meng Anthony Luo

Conall Kingshott Ideas Discord Message

 Budget Discussion

Anthony Luo 5 mins

Brief budget for some things we need to spend quickly, next few days. Everyone have a look.

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

 General Meeting Feedback Discussion

Megan Spee 5 mins

People seemed engaged. nice length, about 40 minutes

Next one end of June after midterm week

 Workshop Announcement

Anthony Luo

EFS wants to fly Houston. Anthony wants to run a workshop on putting it together. Anni sends lettuce meet.

interested in running workshops?, see: Workshops!

 Competition Attendees Discussion

Megan Spee Conall Kingshott 20 mins

  • Follow through from comp debrief in an open discussion!

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

    • Conall Kingshott 15 isnt unreasonable, it’s nice to have help

    • Ethan Abraham Taking people to learn might not help people learn

    • Anthony Luo having people progress from flight tests to comp is a good way to learn incrementally + more people can observe other teams, learn from them too

      • issues come up at comp that are hard to learn from if you’re not there

      • Allows more capacity for:

        • Networking with other teams

        • Spectating teams

        • Talking to/ learning from sponsors and competition ppl

      • gets people hooked on the team potentially

  • Selection Method

    • Select “core group” (Pilot, GS operator, etc.) then fill in other members later

    • If you can’t make it the month and week before competition then you shouldn't go to comp?

      • What about people who are off-stream?

  • Megan Spee Is documenting this 🔥

  • Lettucemeet for specific meeting

    • We will try and have more discussion in this meeting to keep the rest of the team in the loop

    • Please fill this out if you’re interested!

 Next Leads Meeting Mins:

  • No labels