This ticket comes out of the devprod Q4 retro

To improve the process of contributing to devprod projects we may want to consider drafting a contributions guideline or process. The could include:

• Code owners for projects
• What are the responsibilities of the contributor and reviewer in a PR
  • What kinds of review comments are helpful / not helpful
  • Are comments actionable? Has the reviewer identified what's wrong, why, and what could be done to improve it?
  • When to reach out for communication outside of the PR
• Semantic versioning?
• Code of conduct?
• Consistent Repo Config for all projects?

The goal would be to have a consistent process for contributing to devprod projects as well as a consistent set of expectations and processes for reviewers. However, these would need to balance consistency and process against the need for projects to be open and approachable. Process so rigid that it makes it hard for new people to contribute must be avoided.