Create a Best Practices document for handling issues across CCDH repositories

[gaurav]

Description: The Tools and Terminologies teams recently realized that we use slightly different systems for tracking our issues, and thought it might be a good idea to come up with a single document that provides recommendations to both of our groups, while giving us the flexibility to "do our own thing" if needed. This will be particularly important to do this quarter, as we now have several repositories in GitHub (ccdhmodel, ccdh-terminology-service, example-data, sheet2linkml, jdvt), and should make the process of interacting with repos via issues somewhat standardized to make it easier for people from one team to understand what's going on in the next team.

Action item:

• [ ] Produce a document that describes how best to use the GitHub issue tracker to track project-related issues, including:
  • [ ] Use of milestones to ensure that issues are listed on the CCDH Dashboard.
  • [ ] Use of labels to categorize issues.
  • [ ] Use of project boards to arrange tasks by priority and to plan sprints.
  • [ ] Use of issue templates to
  • [ ] Determine if there are any unmet needs that we should look towards meeting.
• Probably out of scope: figure out how to use GitHub's new project management system, currently in closed beta.

[jooho-lee-kim]

Yes, documentation!!

See related issues on ccdhmodel repository: https://github.com/cancerDHC/ccdhmodel/issues/136 https://github.com/cancerDHC/ccdhmodel/issues/137

[joeflack4]

That's helpful; thanks Jooho!