We no longer have access to cage, @Daniel Puratich moved all of our shit to the bay, @Conall Kingshott sorting a bunch of it out.

@Daniel Puratich has been grinding admin confluence pages. Please review and add comments.

Sleeping - initial release

Package Receiving Protocol - initial release

Time Commitment - added details

Calendar - updated formatting

Bootcamper Onboarding added policy for skipping the bootcamp and who can join warg

Organization Roles initial creation - this one by Ryan

Is anyone interested in taking this up? Do we want to stick with current system? This is not an ops task.

@Anthony Luo update existing documentationand don't change

@Georgia Westerlund to add due date for team leads to update roster before mef/weef, end up in gcal. Team Roster Information ping subteam leads to get them to fill out roster before the deadline, when the deadline is known.

Do we want a room for leads or is the bay okay? @Daniel Puratich to address if desired.

@Daniel Puratich to book room try for 4417

@Anthony Luo to explain the current state of things

it needs a lot of love

2024 System Architecture

@Anthony Luo to give update

Internal Licensing & WARG's Flightline Progression Program (FPP)

@Daniel Puratich has picked dates & announced, any concerns?

@Megan Spee

There’s been a couple cases from what I can tell where an aspect of the team (behaviour or roles) have unfitting reputation

• things like sleeping in the bay

  • Sleeping

• or other general behaviors we’d like to phase out - especially anything that is unsafe.

If things like this are regarded as cool or desirable on the team especially among leads/senior members it can propagate pretty badly. And, on the other hand, things like treating specific roles like they’re undesirable or uninteresting has a bad effect

• this was seen in safety captain ~last year, if anyone remembers that far back (it was hard to find more people to be safety captain)

• Culture (this page is literally empty though)

We don’t want people who’ve just joined the team to suddenly be discouraged about what they’re doing! :)

@Anthony Luo and @Daniel Puratich have been going back and forth on arch doc structure with anni doing a bunch of organizations. we would appreciate more eyes/opinion on the current state of it 2024 System Architecture

• Conops out. Please all leads at least read it once.

• @Daniel Puratich added all dates to gcal

• @Daniel Puratich Awaitting reply from Robohub to schedule trainnings

• @eeleads to give update on roadblocks and timeline

  • dates r reasonable

  • Baseline power on for high-current modules to ensure no HV shorts

• Is what’s in Asana right now good?

  • yes

Need more help writing Competition Roster Selection, anyone interested?

@Daniel Puratich doc finalized by oct 1st

@R D (Deactivated) can continue writing

@Megan Spee made form, need to roll out in next weeks, reading week

deadlines in gcal

• announced through meetings (subteams, leads, gen, comp syncs) instead of announced globally… increases saturation of people who are actually involved in team to fill out form

@Daniel Puratich deadlines for this

• Idea is technical subteams will need to delegate out the technical topics

  • but this is not a technical paper! it is a business proposal

  • (technical content is of course required though)

• Operations will only provide templating & organizational structure to meet phase 1 requirements

  • Onedrive - Anni (ms word)

Organization Rolesplz people comment

plz look at asana

anni describing task hazards