Proposal: Duncan's interests / How to keep open source contributors engaged?

Owned by Lite Farm
Last updated: Oct 21, 2022
2 min read

Slideshow (external): https://docs.google.com/presentation/d/1K6VH7Ln5ukyFSh9aJX8c0lplMS3t5xIAmguApAF-g1s/edit?usp=sharing

Video of session (second half), password: ^NmSdb7v

Problem:

@Duncan Brain

 

Context:

@Duncan Brain's interests (as a micro scale farmer):

  • Weather dependent tasks:

    • If there’s rain coming, move up or back harvest tasks automatically

 

Proposal:

  1. Create rules for tasks, similar to Gmail. Examples:

  • “if this happens, do this”.

  • If it rains, push back tasks 3 days.

Could be cron job based

 

@David Trapp likes this idea. However, he already hears feedback that tasks take a long time to create and manage.

@Lite Farm I see this as a separate feature than being included on the task creation. a separate thing to set FOR x condition, IF this thing happens, THEN do a thing.

@Duncan Brain: Agreed, it would be power users.

@David Trapp: then I’m on board.

 

2. Be able to print tasks assigned to a particular person. Could have a scantron-esque reader for people to pencil in responses and scan them using a webcam.

@David Trapp: this is a feature we’ve heard from other users as well.

@Lite Farm: We’ve heard this request in various forms many time. I

@Duncan Brain: Could have an administrative task to update all the tasks assigned to other people based on their paper-based tasks.

 

@Carolina di Lello (Unlicensed) likes this idea as well. Many farmers in Argentina don’t have smart phones so being able to print it would be great. Would also be nice to add a calendar view that shows “Tasks for the day”.

 

3. Duncan wants to learn more about how the backend work:

 

Benefits:

 

 

Execution:

  • Duncan wants to build a local version on kubernetes and could potentially contribute back if useful

  • @Duncan Brain to design what a good print out could look like and work with Caro to refine it. Could be good to use a React library to pretty print. Kevin suggested writing up a 1-page goal statement to make sure the features support that goal. Caro will support with UX to make it more accessible in a paper medium.