Page Comparison

Comp Focusing all projects

• We want to learn by doing

• Shift will happen slowly but this is where we want to be

  • zp will continue for now to keep most of EFS team occupied until new projects are properly scoped

What we don’t want to be

• We’re not a research group

• We’re not a pcb design club

Members need to understand the system before they should be given the go ahead for very technical stuff.

• It’s brutal all our system engineering is wrapped up in a few people.

• It’s hard to design a board without understanding the application (and even harder if it’s your first board ever)

• will be discussed next leads meeting, very contentious

• Daniel Puratich

  • you need to understand what your customer wants before u make a product

  • you need to see use case before implementing

• R D

  • leads should provide resources and direction

  • we need to have leads who get the system instead

  • retention isn’t great, we put a lot of effort into onboarding but after the polish members are thrown into deep end

  • in autonomy people complained about getting easy tasks

    • new members constantly got easy tasks and not more development

  • we need to develop our members, this is hard, we dont have management experience,

  • management stuff is a lot of time, most people dont wanna be managers

  • most of warg’s management is sorta good enough

  • will get a lot of push back from people who want the interesting engineering when pushing for dedicated managers

  • we are hour constrainted, more managers is more inefficiency

  • low amounts of glue work is hurting warg https://noidea.dog/glue

  • monthly system time for questions, more of a presentation and explanation with diagrams, from tech dir Nathan Green for thoughts here

Do we all agree with this? this is big …

• This is an interpretation of Team Charter , do we agree?

• my examples are mostly ee related but arguments extrapolate to all subteams

Systems Meeting

• Weekly sync for zeropilot program in addition to aeac? We’re in integration phase now, need mech stuff soon ish

Next Major Projects

• Baby steps to learn and improve as we go!!

• Pegasus is for two competition seasons, this one and next

  • give us more time for the harder developments for comp after

• Fixed wing (then maybe VTOL) program is on the side

  • no proper plan, we discuss after comp, start simple, learn over time

  • smaller scrappy initially then go better over time

  • for anyone confused: https://en.wikipedia.org/wiki/VTOL

• do AEAC this year (ofc lol) then once more for sure

  • , then SUAS? See how competition goes but we figure this out in future

Concerns

• possibly we cant get tasks for all EFS people to work on

• change name from EFS to firmware

• “I have no concerns when it comes to the team direction. I think moving to CAN is a great idea and me (and other EE leads I think I can speak for them) emphatically agree that system understanding is a requirement among general members. We have discussed this in our own meetings and have come up with some ideas to remedy this.” -Nolan

DRAFT Open Source Licencing

• mech cad isn’t public so no point in licensing right now

• make license for software only

• determined hardware would be closed source

• https://github.com/UWARG/hardware/tree/master/Projects ← ee hardware is open source

• https://www.oshwa.org/definition/

• make ee stuff not be open source