Start the recording

Themes and priorities for this sprint: 

1. LF-4150 - Getting issue details... STATUS

2. Implementation of new filters component LF-4100 - Getting issue details... STATUS

3. LF-4149 - Getting issue details... STATUS

4. Tech debt tickets

   1. Reviewing and merging in the implementation of LF-4022 - Getting issue details... STATUS

   2. This is awaiting a design for the modal that warns about destructive (form-clearing) action via browser back button (should apply to animal creation as well). Loic Sans could you create a user-story ticket for this?

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:

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

• /wiki/spaces/LITEFARM/pages/822018049 [10 minutes]

• /wiki/spaces/LITEFARM/pages/1368227863 [10 minutes]

• /wiki/spaces/LITEFARM/pages/1378910214 [15 minutes]

• /wiki/spaces/LITEFARM/pages/1309999105 [10 minutes]

• /wiki/spaces/LITEFARM/pages/1404567587 [reference]

• /wiki/spaces/LITEFARM/pages/1394835499 [5 minutes, reference]

• /wiki/spaces/LITEFARM/pages/1428750337 [completed]

Forward-looking reads:

• FY2025

• Soil Health V1

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 1

  • Anto will review all PRs

  • Reviewer will be auto-added

• Merged

• Passes verification

• Passes validation

Team availability

S84 runs from … to …

Days in sprint: 10