Meeting Dates/Times for the Term:

Proposed S22 (and potentially indefinitely schedule):

Aidan’s reasons to move Mech Leads/Mech Check-in's:

• How will this impact my weekly schedule? Meetings will be condensed to 4/7 days of the week (all weekdays) opposed to 5/7 days of the week (for Mech team). It is much easier to work in dedicated chunks of time, rather than having most windows/opportunities absorbed by meetings.

• Why hold a meeting in the evening? In my experience, it is difficult to coordinate mass meetings (especially for university students) before the time of 11am. The alternative to this is evenings since afternoons are often used for school/work hours.

• Why Monday and not any other weekday? You have the entire weekend to make substantial progress on the slide decks/tasks/deliverables to then present on the Monday (if not much work was done throughout the week). Monday’s are not traditionally a day that professors assign homework/project due dates (usually Friday’s at 11:59pm for example). Finishing the Monday meetings will give everyone a clear idea of what to expect for the remainder of the calendar week.

• How will this impact my mental health and productivity? Personally, I think having back to back meetings (mech leads/leads/mech checkin) Saturday afternoon places a lot of strain on people who want to make plans for the weekend, and given that it's the summer term, I'll be maximizing my productivity midweek and while the sun is down, and I'll be out Saturday/Sunday during the day (and I'm going to encourage you all to do the same). There will obviously be times where we need to buckle down for the day and grind out a work session, but while the work is still remote (and required everyone completes their deliverables on schedule). More flexibility in your schedule will enable you to take the time to do what you need to do to maximize productivity!

• Can we still meet in the bay on Saturdays? Of course!! Working/jam sessions can be held any time and are encouraged so long as every one is respectful of SSDC hours and maintain the upkeep of the bay! I just want to remove the obligation for the members who come to E5 just for the Mech check-in, and leave right after. When manufacturing terms begin, I can imagine a schedule where it may make sense to have the mech check-in paired with a work session:

  • 9am-12noon: Hands on work to build the car

  • 12noon - 1:00pm: Lunch

  • 1:00 - 1:30 Mech Check-in

  • 1:30-4:30: Hands on work to build the car

Concerns to address:

• Monday is the start of the week, the end of the day is time to figure out what needs to be done for the rest of the week.

  • Syllabus is released at the beginning of a term so most major assignments/tests/exams will be established well in advance of the date.

• Meetings keep the team in check to complete their tasks.

  • While the weekly meetings may provide a reminder to newer members to show up, perhaps we should revisit our incentives to why they should contribute to the team - think about what motivates you to contribute; Is it a title? The tasks/responsibilities you have? The opportunities you’ve been given? What you’ve learned? The people you work with? The vision that one day a car will be made that you can say you’ve helped create?

Questions:

Any opposition to moving the mech meetings from Saturday to Monday (for the time being)?

Is there a need to have Mech Check-in every week?

• Can we host a Bi-weekly/monthly instead?

• Can we more effectively use our tools (slack, confluence, Jira) to provide updates to the team (weekly newsletter)?

Saturday:

Mech Leads: 9:30am-10:00am

Mech 101: 10am-11am

Working session: 11:00am - 12:00noon

Mech Check in “During Lunch”: 12:00noon-1:00pm

Working session: 1:00pm~

S22 Mech Purchase List

/wiki/spaces/MECH/pages/3034218497

S22 Onboarding

Confluence has become an incredible database for recordings and knowledge shares that go untouched afterwards, if we can create an effective list to get any user quickly and efficiently onboarded they can be immediately given a task to start making meaningful contributions to the team while learning and developing their own skills.

Training Hub

I want to have core members become DRI’s for running onboarding to new members. Their responsibilities this term would be answering questions new members may have, troubleshooting issues with software (what/how to download), and directing them to the required confluence resources that have been created already.

To Do:

• Select 1/2 Members to Run Onboarding

  • Aidan D - potential candidates

  • Jasmine - good candidate

  • Shangeethan - good presentation skills

  • Jeyoung - outgoing, good candidate

• Ensure “Training Hub” is detailed enough to give a new member a good enough start

  • It can later be developed into a more formal database for subteam specific activities etc.

Term Goals and Timeline Revisions