Start recording on Zoom!

https://ubc.zoom.us/rec/share/1RtrV4-3zPfHCzgvXBQUWb8pRdpzg7v6GhEnrVTUh96s09FB8PP0i1KQd0lEeDw.ykgmYRfrF8AChrZ-

Passcode: Coe=Nqh9

Themes and priorities for this sprint: 

1. Complete ARCH work

2. Begin work on the Animals Dashboard (https://www.figma.com/file/eMffC0h3JPlWtzNttxJpil/Litefarm-Updated?type=design&node-id=2780%3A48212&mode=design&t=mckGufx4VmYiUCAx-1)

   1. Scope includes: Mocking of interactions and links to other pages, but no actual navigation / actions and desktop, mobile, and tablet views

   2. Stretch goals include: Search, Interactive KPIs, Filters

3. Tech debt tickets

   1. SPIKE on build vs. buy for CSV upload

   2. https://lite-farm.atlassian.net/browse/LF-3830

   3. https://lite-farm.atlassian.net/jira/software/c/projects/LF/issues/LF-3946

Pre-reading for this sprint 

Intro reads:

• Getting started! [10 minutes]

• Tips and tricks [5 minutes]

• Intro to the LiteFarm app [20 minutes /w videos]

• A brief tour of the codebase and tech stack [5 minutes]

• Source control and the developer’s workflow [5 minutes]

Animals specific reads:

We’re still working on https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1378910214, so if you have 20-minutes or less before planning, read this. It’s the most relevant and probably the right level of detail for jumping in quickly without understanding the big picture.

Other readings haven’t been significantly updated since S79. However, they’re listed below from most high level to most detailed:

• https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/822018049 [10 minutes]

• https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1368227863 [10 minutes]

• https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1378910214 [15 minutes]

• https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1309999105 [10 minutes]

• https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1404567587 [reference]

• https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1394835499 [5 minutes, reference]

What’s the definition of done for a story? 

• Code

• Language tags - (run pnpm i18n script in /webapp )

  • If En copy changes on a ticket please set all the non-En tags to “MISSING”

  • Es version of the language tag as “MISSING”

  • Pt version of the language tag as “MISSING”

  • Fr version of the language tag as “MISSING”

• Unit testing

• Check in with @Loic Sans if there’s a visual component to the story

• Open up a PR, and leave it unassigned. Two reviewers from the core team will be automatically added. Core team to incorporate feedback given during peer review. (Check if this is working well for PRs from forks from contributors).

• Passes peer review x 2

  • Anto will review all PRs

  • Second reviewer will be auto-added

• Merged

• Passes verification

• Passes validation

  • Loïc and Anto to fill in for David/Kevin on validation

Team availability

S80 runs from … to …

Days in sprint: 9