\uD83D\uDDD3 Date
\uD83D\uDC65 Participants
\uD83E\uDD45 Goals
\uD83D\uDDE3 Discussion topics
Item | Notes | Action | |||||||
---|---|---|---|---|---|---|---|---|---|
Architecture meeting |
| ||||||||
Weekly General | I think we had weekly general meeting before (long time ago I think) and we switched to biweekly pros:
cons:
(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 |
| Jinghao Lei book room might be next Next saturday | |||||||
Comp registering | Done | Second firmware COOP | updates? iirc we are not taking Hiren for second fw coop this term | Mech coop next term | needed? | Sysint coop next term | needed? | Follow up next Tuesday.
| |
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 |
| ||||||||
Sysint lead | have role responsibility defined and have an onboarding document for being Sysint Lead. | ||||||||
Recuritment for next term |