Recording link:
Agenda
Quick clarification requested from devs: what is it proposed we are releasing in January?
LF-3830 is NOT GOING TO BE RELEASED (data won’t be migrated)
Harvest terminology is going back to evaluation
Releasing consent?
LiteFarm user guide (David Trapp)
Plans for pivoting to pivot (what is next epic?)– meeting with appropriate team (Duncan Brain)
Sensors: Devs would like to discuss sensor-array configuration on the map with Loic Sans
(If needed) harvest / crop plan terminology
Discussion points
January release
David Trapp in favour of releasing the consent fixes on their own
Should check with Divya Chayanam when she returns
Proposed release date: next week – Wednesday January 29th
LiteFarm user guide
David walking through the process by which the videos and script have been generated
Anto: what’s the strategy for keeping this up to date?
Both screen recordings and script should be easy to update (compared to, e.g. the original YouTube videos)
Joyce: if the need to request human translation could be omitted, the process of update would be a lot easier
The possibility of AI translating or reading the script has been considered and can be pursued
Loïc: where will it be hosted? Wix is not the best for this
There should be services that specifically provide documentation sites, with good support for searching and translation functionality
Where should the link to the guide reside?
The YouTube tutorials should be taken down and the link replaced if they are not considered up-to-date
Anto: what about User Pilot (or a free alternative) that walks the user through the actual app
David: this is the actual dream – but this becomes a dev/design project at that point compared to a standalone user guide which is on the support team’s side
Loïc: This user onboarding is a one-time thing, so can’t replace a proper support guide
Duncan: forward looking to the next epic. With the revamped scope sensors is going to be a quick module from the dev side. Are we in touch with a manufacturer already?
Loïc: no, we don’t even have the name of the manufacturer. We have gotten in touch with Farming Smarter but in order to avoid a repeat of the sensor situation, we need to talk to the tech team of a manufacturer ASAP
Anto: since it’s relating to the grant, Farming Smarter should know who these are
There are 4 farms per year for 3 years in this grant. There COULD be as many as 4 manufacturers per year involved!
Farming Smarter has given us general guidelines about how the pivots behave and how the irrigation subscription is communicated to the pivots (manually via USB transfer of the file) – these will have to checked
Tentatively speaking we have some early assumptions about what e.g. the add flow looks like but these have to be checked
The constraints are coming from not necessarily the user experience, nor the technology but what the partners were assuming
Loïc: We need less second hand discussion and getting all parties in the same room (Joyce: including Ensemble would be my preference when it comes to talking to the manufacturers)
Joyce: I don’t think the pivot manufacturers will be meeting with us if they aren’t grant partners…
Anto: the
.vrifile being downloaded and given to the pivot is enough for the sake of the grant; there might not be an communication hereDuncan: We need to confirm if we are integrating with a pivot API at all – otherwise it’s manual entry into LiteFarm and a totally different situation
Action items moving into pivots:
Loic Sans to get the actual manufacturers from Farming Smarter
Confirm with Divya Chayanam the scope of the grant whether talking to the pivot is part of the requirements or not. (Farming Smarter should know this as well) – confirm the end of the flow – for Anto Sgarlatta (in shared channel)
ALSO (needs the names of manufacturers) to know if they have read APIs (i.e. if it is a Ensemble situation or not)
Dev and Design discussed array and sensor icons on the map – points will be added to Figma
TO DO
Task | Owner | Due date | Notes |
|---|---|---|---|