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

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

\uD83D\uDDE3 Discussion topics

Item

Notes

Action

Architecture meeting

2023 System Architecture

  • Talked to Graeme and Brian about our design and more action item is added

  • Conall may talk about it briefly?

  • Mech timeline concerns, Dec is probably not realistic. Jan deliverable.

  • Carbon filter is in progress. pushed into Dec.

Weekly General

I think we had weekly general meeting before (long time ago I think) and we switched to biweekly

pros:

  • People on subteams are not updated asap.

  • New process on updates on architecture doc

  • flight test debriefs

  • synced everyweek

  • chances to meet new people

  • creating engagement

  • project/update based

  • Deadlines

cons:

  • attendance might suffer.

  • less specific on subteam specific

(Anonymous voting)

interactive feedbacks

Asking questions to the audience.

request to us/leadership

Pick some active member and let them do in depth update.

Project spotlight because multiple subteams are involved.

acknowledge people for member accomplishment.

Flight test videos playing

Social

  • Movie night on Nov 19th, 6-8 PM

  • Snacks?

  • 2 socials one next week, 1 at Dec 3 or 4

Jinghao Lei book room

Next saturday

Second firmware COOP

Follow up next Tuesday.

  • Hiren has submitted petition for shortened work term (he needs to work until mid Jan for this to count - neither Chris nor Anni can support this).

COOP

EFS(for sure) mech CV, sysint. 2 positions

Joint mech EE coop. (mech side low attendance in person, manufacturing)

CV integration, testing.

Sysint: Onstream people very low, having someone in charge of managing deadlines/timelines. Organize flight tests, do actual work for subteams. PM role but also have technical work. Managing deadlines for all the team, lack of sysint team members. Hours are flexible (heavy on Evening/weekends)

2 week frame

→ flight test results?

moter not enough thrust

number of people going to the comp

prioritize drivers, as many g drivers as we can

3 cars? 10-12 people

Safety Things

  • safety data sheets

  • user/operator manuals

  • power tools/ mech tools

  • Chemicals

  • Team lead data

Sysint lead

have role responsibility defined and have an onboarding document for being Sysint Lead.

✅ Action items

⤴ Decisions

  • No labels