Guidelines for a well-maintained upstream repository.

[bwplotka]

Can you provide more info on what elements you are looking for @fpetkovski?

[fpetkovski]

Sure thing. These are some of the questions that come to my mind:

• How to triage issues: when does an issue go stale? Are there some bots that we want to use across the team for all projects?
• Which CI system to use? Github actions, Prow, CircleCI, Travis?
• Are there set of CI actions that we want to have on all repositories for consistency purposes? For example, prometheus-operator does not allow go package names with dashes and underscores. Do we want to have this constraint for other projects?
• How to interact with the community and maintain open and transparent communication.
• How to keep a changelog. Should it be auto-generated from PRs? If yes, can we automate this for all repositories?
• Which docker base image to use when deploying to Kubernetes/Openshift? Should everything be based on scratch or is that too restrictive? Do we have security policies in Openshift which govern this decision?