...
Time | Item | Notes | Action | ||
|---|---|---|---|---|---|
7:00 - 7:05 | Bootcamper party feedbacks | went well 15-20 people mainly EFS, and CV, EE and mech have 2 each Big lecture hall and not much talking between the new joiners book 2004 and it’s better, same level more interactive? that would require different tasks Progress wise? it’s pretty good, people asking questions Revisit it or have another one before reading week so that they can pick up a task and work on it during reading week | send out a question about how many bootcampers are still struggling to finish it | ||
7:05 - 7:10 | report postmortem | Done with Dhruv Aidan Hamza and Anni went well, improvement | all leads read through the meeting min | ||
7:10-7:15 | event with orbital follow up? | Postpone because of Chinese year off loading? a week or two from today Jackbox, partygame, not too sport related. | |||
General Ops query pipeline | lots of Ops related tasks going on and kinda hard to follow everything discord forum for requests: easy accessment, could also just mirror stuff from Asana should not replace Asana tickets, central place to go for task management | Annoucement: Leads introduction Questions about leads Hamza Ali by Friday evening | |||
Social media pipeline | already having a pipeline Idea required, make a post in that forum | Need other subteams' input | |||
Team roster done? | Need to manually add to Mech: not done Electrical: EFS: Done! CV: Sysint Ops | Tonight 15 mins task | |||
7:15 - 7:25 | Flight test program coordination meeting outcome/timelines | All the integration stuff Buy an off the shelf frame to test software What exactly we want to do for comp sim1 or what’s actually feasible Feb 18 go? no go? good timing because before midterm Cornflakes until Feb 11 Make sure all the integration is happening Define Comp sim: all MVP from all system are ready to test so that we can go to comp. All the integration starts at that time. 1 month and a half late to all our timelines. It will likely be frame validation. We should still be flight testing frequently. Group of people flying cornflakes. Endurance test is better wording. Proof of flight test | Follow up with GUI | ||
7:25 - 7:35 | Comp selection criterias | The rest of the team should be informed about rules of selecting people to comp Being visible, because people are asking questions about the selection process: maybe during Gen meeting Timeline idea should be known to the team: applications at the start of the Winter term and final selection before reading week stream bias | |||
7:35 - 7:45 | Evaluate feasibility of weekly general meetings | Not enough changes for updating Attendance dropping, people already have subteam meetings Enough to talk about, updates mostly with lead updates. chances for people to talk and make decisions make people realize about the updates and pick out problems flight test content for each week pushing people to go to timeline to be evaluated No interaction part? ask questions in general discussion based and cut the discussion off | W23 Buy list | Social media pipelinetiming is a bit awkward. | keep weekly, keep at 8, format it differently so that we open up more discussions |
W23 Buy list | there is a thread exist, let the people know what to get spreadsheet and work with Hamza buy something/budgeting this term | Deadline next Tuesday | |||
WWFC Partnership | Flight staging Anni and Megan to be Flight reviewer courses saves us a lot of money Industry connections more outreach | Aidan, Hamza and Sahil Friday 4:30 | |||
7:45 - 7:50 | Weekend more details coming up async | ||||
General Meeting Slides | add onsite borrow/return policy |
...