Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • reference message (in private chats)

  • EFS has a lot of new members

  • They have a lot of new members

    • a lot of pretty good new members

    • not a lot of second year students

    • uncertainty of impact of work pushes people away from the team

  • Very few projects people are allowed to choose their own architecture/implementation

    • success of LED project is due to allowing people to own it and make mistakes and see results

    • people wanna write drivers especially if they’re new

    • being an owner of part of ZP isn’t that much freedom, there’s a lot of other systems

    • more projects like LED board could be nice

      • sensor cluster → harder

      • servo module stuff

      • projects require architecture

      • for ZP → managers have very clear how they should function

    • letting people do arch is messy because implementation details come up

  • Derek Tang handles a lot of ZP stuff

  • Reviewing PRs

    • video to prove working method

      • we do it for drivers

    • PRs have a massive knowledge exchange

      • other ppl should be able to review PRs

    • people want to learn good practice

    • need more PMs

  • ZP

    • is the coolest thing EFS does

    • it’s cool when people understand it

    • it is a large project and hard to achieve anything

      • Manasva worked on ZP, understands arch,

    • Adding CAN support to ZP

  • Tracking Antenna

    • fixing a lot of stuff

  • Important to ping in Aidan Bowers, Sahil Kale, & Chris Chung

  • have so few PMs so can’t assign them to review bootcamps

    • PMs is seen as a need and not really a privledge

    • lowering the barrier to being a PM

    • getting people invested in the team will cause natural tendency in this direction

  • socials

    • making it feel like a team

  • bootcamp reviewing

    • is a lot of loading on leadership

    • automated testing?

Past Progress

  • CAN Functionality

  • ZP program

  • Funding proposals

Future Goals

  •  Competition Tuning

  • experimenting with monday meeting in two halves, telling people not to show up to whole meeting

    • don’t want to waste people’s time with this

    • breaking work sessions up?

    • spend money to save time

  • lack of bay door opening holds us back

Blockers & Requests

  •  Hardware availability
    • surveying memebrs about their interests within meetings might be a path forward here

    • hard to come up with tasks, (hard for everyone)

  • member influx

    • increasing new members