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 13 Next »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

  • Review outstanding action items from previous meetings

  • Review RFC Process

    • Approve any outstanding RFCs

  • Review Competition Deadlines and schedules

  • Review Risk Assessment

  • Review Report Progress

  • Plans for scheduled flight test next weekend

\uD83D\uDDE3 Discussion topics

Time

Item

Presenter

Notes

3:10

Outstanding Action items

Aidan

Still to do:

  • Connectors for electronic in architecture

  • risk assessment

  • zp3

  • Aaron to check in about registration for phoenix

3:20

IMAC updates

Aidan

  • see in thread on mechanical space discord (to be made into confluence thread)

  • Deadlines need to be revised and be communicated what is actually done

3:23

RFC

Aidan

  • Submitter should ping in sysint and start a thread for conversation (link and ping sysint in RFC channel)

  • Sysint votes and 2/3 majority is needed to approve it

  • Lead who signs off on it to update thread in discord and lock thread

  • Status updated within 3 days, more info call within 7 days (decision), 10 days max for final decision

3:40

Competition deadlines

Aidan

3:49

Booking grounds

Aaron

  • Book sundays up until May 5th CC: uw.warg@gmail.com

  • Next weekend, long weekends. make sure it’s okay if we don’t show up every time.

3:53

Report Status

Hamza

  • Working on format and content

  • Will publish to github as a public repo

4:20

Risk Assessment

Aaron

  • Leads have not done anything yet

  • All of it should be put in the same document

4:22

Flight Plan

Aidan

✅ Action items

⤴ Decisions

  • No labels