Page Comparison

• 15 minute call before sprint planning with new contributors to do a quick run through of the agenda. Otherwise, heavy information overload during sprint planning.

  • For really green folks probably best to just hand them 1 - 2 tickets rather than thrusting them into planning

  • Might be a good idea to create a 1-pager to give contributors so they can self-classify

    • Persona 1: Total newbie, never worked on production code. Maybe self-taught or a boot camp

    • Persona 2: Some experience on a team,

    • Persona 3: No issues slotting in, comfortable with open source

• Asking for help if you need it or have questions

• Duncan Brain for taking on a lot of responsibility and building processes that are going to make LiteFarm a better product and better team!

• Sayaka Ono for a great start, sober analysis and estimations, good questions, and diligence in becoming a member of the team.

• Carolina di Lello (Unlicensed) for deftly incorporating good research into her designs!

• David Trapp for drumming up a lot of interest amongst farmers, farmer associations, certifiers, and acedemics on his roadtrip in Paraguay!

• Craig Yu for knocking down his tickets like it hasn’t been 2 years since he’s looked at the codebase

• Mwayanjana Bolokonya (Unlicensed) for his patience and for keeping the train moving on tickets that required a lot of in-depth QA.

• Onboarding suggestion: inform contributors that Jira tickets will be automatically moved to Verification from Development once the PR is merged, don’t do it manually. (It could be that I missed this info from the last sprint planning)

• Make the API documentation more useful. We should be able to run APIs here, but it doesn’t work now. (Generating API documentation)

Thank you everyone for the warm welcome!
Lite Farm Duncan Brain Thank you for checking in, offering help and helping me!

• Categorize tickets as low, medium, high complexity levels