/
jan 26 post-recruitment pre-induction

jan 26 post-recruitment pre-induction

Participants

Apologies

Discussion topics

Topic

Context and Discussion Points

Action Items and Decisions

Topic

Context and Discussion Points

Action Items and Decisions

CATEGORY

Pre-induction team meetup

  • Schedule

    • 12pm meet at some uni room

    • 12:30pm head to lunch at kensington

    • 2-3pm arrive back at campus

    • 3pm induction

  • Onboarding slides

Do onboarding slides, ask for photos, mbti, etc

Post induction dinner

  • By ourselves as a team

 

Team meetings

  • Types

    • Regular standups

      • async

    • In-person & online dev sessions

      • Regular e.g. 2-3 each week, could vary throughout term

      • When2meet

      • Optional

      • At least one director

      • Anyone can attend

      • Would help with motivation, productivity, support

    • Planning meetings

      • design decisions

      • hgih level planning

      • new features

      • every ~6wks

  • members take on meeting minutes

  • When2meet

Team structure

  • Sub-teams, not free-for-all choose tickets

    • Potential team break-up

      • code runner

      • visualiser

      • UI/UX

      • collaborative

      • misc

 

Team Planning

  • reduce overlap of earlier tasks with eventual later plans that render it redundant

  • balance between long term plans and short-term progress

  • In beginning, while team works on small tickets, directors

  • 1:1s to figure out interests, what they would like to work on, issues

@Gordon Huang (Unlicensed) @Luke Fisk-Lennon (Unlicensed) @Edward Qian (Unlicensed) member assessment: go through each member again, figure out their interests and skills
@Gordon Huang (Unlicensed) make suggested way to allocate members who we’re unsure
@Gordon Huang (Unlicensed) @Luke Fisk-Lennon (Unlicensed) @Edward Qian (Unlicensed) make onboarding tasks
@Edward Qian (Unlicensed) write up necessary documentation
@Edward Qian (Unlicensed) clean up confluence pages
plan 1:1s (later)

General planning

Structs v2 repo (staging? experimental) for new team
  • from scratch? construct using snippets from origin

  • How much of existing code are we going to keep?

Structs v2 repo (staging? experimental) for new team
figure out which parts of codebase we’re keeping/deleting

Team & Leadership principles

  • Team input and impact

  • Be firm with responsibilities and accountability, while being flexible

  • Epics/goals/targets, members set estimates how long to complete

  • At all times, members should have some direction, not confused about what to do

 

Actions

directors task board
team task board (linear)
set up notion for directors
directors assign project responsiblities?

 

  • DAP

  • Tree-sitter

(thanks hussain)

research how we might use this

Useful links

Related content