2024-09-03 Director Sync

Attendance

• @Georgia Vachon Westerlund

• @Nathan Green

• @Daniel Puratich

• Anyone is welcome, particularly director advisors, we’ll see who can make it.

Frontloaded Topics

• Onboarding Georgia

  • Director Onboarding

  • adding to all the accounts

• Role of directors alignment

  • Director Expectations

  • Do u feel like some stuff currently listed in Operations - Responsibilities is and/or should be exec stuff?

    • update eventually

• How we intend on splitting the workload

  • Georgia remaining as Ops lead - can handle most admin/logistics

    • Georgia on leads meeting.

  • Who is running flight tests?

    • Nathan carry continue.

  • Who is running arch syncs? (tech director?)

    • continue Nathan.

• What project management tools we want to use

  • Need to push the use of Asana

  • need to ask people to do stuff more directly

  • use asana for arch syncs

• Biggest Risks:

  • no onsite directors for winter term, ggggg

    • can’t grab Yuchen, he’s offsiters

  • Trailer trainning for competition

• Laying out a flight test timeline and key milestones to ensure proper ramp up to competition.

  • We need clear objectives for this fall term bc we will all be offsite in winter which will result in delayed progress imo

  • Objectives for the term wrt:

    • competition

    • fixed wing

      • Directors align on possibility of usage at comp, see discussion here.

      • Flight be EOT? prolly not, see below

    • Pegasus

      • Pushing autonomy

    • ZeroPilot

      • EFS seems ready to run M2 early this term.

        • get them to set deadlines

      • more foam planes this term

      • focus on comp stuff toooooo

• Do we wanna try to split things based on project?

  • Anni tried this in the past, it didnt work great imo

  • Could be like:

    • Nathan: Ground Station, Tracking Antenna, O-Week thing

    • Georgia: Pegasus 2

    • Daniel: Fixed Wing, E7 Atrium thing

    • Other members are handling other programs adequately without much guidance: houston, foam planes, etc.

    • there are a lot of TODOs that aren’t rlly encompassed by this type of breakdown

notes:

• roster

  • not many yet → 15 so far

  • Worth reaching out to people that fill it out falsely?]

• avoid flying peggy 1

• timeline

  • Peggy 2 flight before end of month, flight test on 20th weekend seems best

    • need to order rangefinders

    • no pi, no lighting initially

  • need payload when conops comes out

    • should have conops end of september

  • October 12th, all autonomy hardware done and run some software, hopefully comp related

    • integration test mostly, doesn't need to be special

  • Aim for fixed wing first flights just after comp

    • gives us time to focus on comp

    • focus on fixed wing right after comp, before we get conops

  • After comp 2025 conops release

    • decide VTOL or run Peggy again

  • SUAS

    • limited for 8 people

    • challenge with 2025 is that we dont have a lot of people onsite

    • 2026 tho we could enter in Peggy

      • there will be a ton of us here right after we graduate

      • gives us time to get our money up too

  • no other comps r rlly viable

    • ran through some not rlly worth it

• leads meeting

  • what is purpose

  • alternate weeks, ask leads what they think

• we setup asana a bit, will wait for more stuff to come out

  • arc syncs in 2103

• named fixed wing eclipse.

• mech timeline to push

  • comp payload top priority

  • no fixed wing deadlines this term, will discuss more later. maybe winter term mech will be less bogged down so push deadlines then

• socials

  • 2 general socials, do the rest by subteam

  • fire pit was chill, low attendance

• ee team

  • two leads unless someone is stepping down in which three is fine

  • one hour per day average, set expectation

• autonomy

  • push comp stuff early

  • push testing

  • important this comp

• ops recruitment

  • setting up the books

  • getting members and keeping them engaged

  • learn blast

• nitpicky

  • team being very nitpicky on design stuff

  • delegating stuff better

  • culture is important

• force all subteams to have a weekly work session

• force one subteam specific social per term