Page Comparison

...

How should we incorporate developer written unit testing into tickets appropriately?
- For API tests:
  - Role based testing
What is the appropriate level of hands-on / hands-off guidance for contributors?
- Contrib channel is a great way for some people
- For meet-n-greets with new contributors, loop in one of the engineers to be their technical point of contact
Are we writing API tests? The instruction for running tests in the Readme didn't work for me (I would like to update it)

Start doing	Keep doing	Shout outs
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)
I would like to make 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

Action items:

Sayaka Ono: Update to Readme for running API tests

Lite Farm to add a ticket to Update API doc (https://api.beta.litefarm.org/api-docs/#/)
Sayaka Ono to do a knowledge transfer session with Duncan Brain and Mwayanjana Bolokonya (Unlicensed) on jest testing
Mwayanjana Bolokonya (Unlicensed) to create a Confluence document to help people set up local testing
Duncan Brain to put together 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

Mwayanjana Bolokonya (Unlicensed): Verify and update (Mwayanjana Bolokonya (Unlicensed) to find doc) to include Github Actions automations. Kevin believes backlog → Development (when creating branch from Jira) and development → verification (when a branch is merged into integration) are automated.
Lite Farm to add complexity levels to tickets

Versions Compared

Old Version 11

New Version Current

Key

Action items: