Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Background

This retro is for S57: Thursday, February 9th - Wednesday, Feb 22nd

Please add comments before the meeting! We’ll take a few minutes to add additional comments and discuss, then put together action items to operationalize suggestions.

Last sprints (S56) retro is here: 2023-02-08 (S56) Retrospective

Retrospective

S55 Discussion topics:

  • New thoughts on Draft PRs?

    • Thoughts from last retro: Joyce Sato-Reinhold attempted to do a draft PR this sprint as a way to get feedback from the team on an approach before getting too deep into a particular solution. In the end, the approach she thought would work didn’t so she ended up coding two solutions that both look like they’ll work. There are other solutions that she thinks will work, too. Concerned it may not be super readable since it’s very commented. Structuring it was pretty difficult too. Some things to consider:

      • Does this help your personal process?

      • Is the ticket impactful enough to code out several approaches?

    • Joyce did all of the different approaches in the same branch and thought this was easier. Could also potentially do them as different branches.

    • Sayaka always creates Draft PRs first, reviews her own code, and then switches it to ready when she’s happy with the solution.

  • Feedback on Mwaya’s unit testing guidance: Jest unit test guidance

  • Thoughts on a LiteFarm calendar for tracking OOO, meetings, and events?

    • Q: How would this incorporate folks without @litefarm.org email addresses?

Start doing

Stop doing

Keep doing

Shout outs

  • Some sort of automated process / notification whenever a PR is made that needs review

  • Kevin being in charge of merging; I feel like this introduces inefficiencies and should be owned by someone(s) closer to the code

  • Getting in bigger tickets early in the sprint loads of time for feedback which is great

Action items:

  •  

  • No labels