Title. Use folders & Labels as necessary

• End of each term, we can sell equipment to put cash (back) into our cash-box. 24 hours items are listed, FCFS and ig people can bid for it if they want? Maybe just a google sheets with a linked form and ppl can put in name/bid. idk.

• Usually consider: broken, in need of repair, no longer used items.

• Parts come with a written paper saying warg is not responsible for safety or damage to items…

Potential list of things we can sell off:

• older / in a bad state ESC’s.

• Broken/badly damaged video transmitters

• ICARUS motors (vtol, we’ll likely not use them again for a while)

• Older quad/hex motors (we can use them, but don’t really have the parts necessary to actually run them)

• Large/random props

  • we do use these occasionally, but very rarely for warg purposes (usually thrust stand, most recently icarus) and it’s probably better just to sell them off instead of keeping them.

  • We should keep 10-14” props as well as the small props

• Old ESC’s (T-motor ones)

  • these have failed a large number of times… I would not trust flying anything on them anymore

• Old GPS stuff / A/v stuff / etc

  • idk do we ever use this?

• Old 3d printer filament

  • the “USE PLEASE” ASA and the grimy looking transparent PVA?

In the past, we have sold:

• receivers/transmitters

• controllers

• Confirmed. Most of our stuff in the downstairs bay right now, furniture and non-valuables outside.

• Tomorrow morning will help VEXU move out, and then move in, inventory, sort, layout.

• Bay code tracking, reset document, etc.

Anthony Luo Megan Spee

• Levels for each thing

  • a level, for example, unlocks some classes of aircraft? small (houston, phoenix, judie), up to icarus (discontinued lol but this would be the hardest…)

• Confluence documentation for each level

• online quiz + in person demo (for some) levels.

• Will go from basic (no qualification) up to competition ready?

Megan Spee

Anything in this box please critique/discuss, comp selection processes should be scrutinized pretty hard so we can make it better

• How many people, from which subteams, etc.

• Looking at 14-16ish people? or 10-12?

  • this has definitely been discussed before. make a decision if possible

• the ‘process for selecting competition-goers’ documentation should be made easily available start of fall term, with expectations outlined pretty clearly.

• Workload assessment, being ready for a LOT of new bootcampers

  • Do we want to continue accepting everyone? Can have applications // reduce number of bootcampers // give tasks directly. Can be subteam specific. Can (potentially) automate onboarding reviews to some degree (esp for linting code style and/or a testbench for code functionality like ECE labs). Unsure.

• Reviewing recruitment & marketing approach.

  • Making sure we’re clear on what each team is doing (ties into project goals for short/medium term)

  • having information available.

Megan Spee , Georgia Vachon Westerlund

Generally:

• making sure we are advertising that we are always open to new members (depending on how many ppl we want to onboard)

• allowing members to quickly and easily understand what teams are working on and what they can expect to do on all of those teams

• on my mind:

  • posterboards explaining our drones (looks cool, easy to understand)

  • WARG branding (banners/stickers/idk)

  • Website to include more info?

The rest of it

• idk we’ll discuss this in the meeting

Georgia Vachon Westerlund Megan Spee

• Also to be discussed. Projected income and areas that need the most funding

(on my mind: printer, rf stuff, electronics)

• bambu printer :stare:

This is something we used to do, and we should continue to do!

• Have some contacts in our e-mails (usually very fast response)

• Leverage discords && other community forums

< Section content moved to end of page for (better formatting) reasons>

• Who will be on-site next term?

• Focusing on comp stuff

• Conops kick-offs - we need to be ready. Schedule out meeting times regularly each week for those syncs and architecture meetings to happen.

• Can leverage existing sync shedules.

• Increasing sync-schedules for comp specific parts (tracking antenna, RF infra, etc?)

• Having concrete test & project plans before the term starts

  • not just “what are we going to test” but also making sure “how are we going to test it” is cared for from all sub-teams and there’s points of contact listed for active projs.

  • Hopefully done before next leads meeting (early sept, probably).

Megan Spee

• interest in aero design and simulation should be utilized this comp season