Page tree

Versions Compared

Key

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

...

TimeItemWhoNotes
10 minRecapCraig
10 min PoliciesAll

Things the TC will officially mandate:

  • The tech lead from each team is responsible for reviewing PRs created by their team, regardless of the repository.
    • May be delegated to a backend/frontend lead, but the responsibility ultimately lies with the tech lead.
    • The lead maintainer for each repository is still responsible for their designated repositories.
  • Tech leads must have a succession plan with sufficient overlap for knowledge transfer.
    • Onboarding/handoff must ensure that the new tech lead understands their responsibilities and duties.
    • Updating team documentation (who is the tech lead(s)) is the responsibility of the Tech lead.
  • Issues discovered after a PR is merged will be addressed by the tech leads involved during retrospective, out-of-band discussions, etc.
  • Feature-level design must be captured on the wiki for purpose of early feedback / knowledge sharing among tech leads
40 minEnablersAll

Process improvements, meetings, tooling, documentation, etc. that will help implement the new policies:

  • Tech leads go back to their teams and promote PR reviews by all devs - stress the benefits.  
  • Publish a list of teams and their structure and areas they work in.  Once created this will be maintained by the tech leads.
  • Institute regular tech leads retrospectives (each sprint? every other sprint?) and re-engage ALL tech leads
  • <something about getting the various tech leads involved in design/arch conversations earlier>
    • Promote use of wiki for capturing designs / spikes / etc. ?
    • Decision logs - part of the documentation conversation.
  • Group review of a PR led by Marc? Zak? - if not live maybe recorded and shared with appropriate tech leads?
    • May not be needed by the retrospective / design feedback loop / etc.

Action items

  •  (All) Tech leads go back to their teams and promote PR reviews by all devs - stress the benefits.  
  •  Craig McNally Publish a list of teams and their structure and areas they work in.  Marc Johnson and Taras Spashchenko to provide links.
  •  Craig McNally Jakub Skoczen Organize tech leads retrospectives - initially every sprint, eventually space out to every Nth sprint
  •  Craig McNally Reach out to all current tech leads / call a meeting dedicated to going over this - what are their new responsibilities, promoted practices, etc.
  •  (TC) Define documentation policies/formats/templates - farmed out to a subgroup, etc...
  •  Craig McNally polish the policy wording and get to David Crossley to put on dev.folio.org → 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyFOLIO-2506