We'd like our community managers to be able to assist in issue
triage - mostly to justify giving them the Github permissions to
add and edit labels on issues in the project.
As community managers are not expected to be technical, we're not
expecting them to act fully as reviewers, but letting them move
issues between repos, close issues that have gotten out of hand
and are accumulating CoC violations, and label persistent
problems as things that should be strongly considered for future
releases are valuable.
Signed-off-by: Matt Heon <matthew.heon@pm.me>
When I worked up changes to Buildah's Governance, I found
that Podman's version was missing a few links, and there were
a few minor grammatical tweaks needed.
This addresses those.
For reference, Buildah's Governance Update PR: https://github.com/containers/buildah/pull/6124
Signed-off-by: tomsweeneyredhat <tsweeney@redhat.com>
I noticed that the GOVERNANCE.md file did not have links to the
MAINTAINERS.md file. Also added a link or two to the OWNERS file.
This change just adds links and does not change any wording.
Signed-off-by: tomsweeneyredhat <tsweeney@redhat.com>
Firstly, include both subprojects in the model and link to them.
Ensures complete clarity on what is part of the Podman Project in
CNCF.
Secondly, add that Community Managers are expected to take notes
on Core Maintainer meetings and make those notes available to the
public.
Signed-off-by: Matt Heon <mheon@redhat.com>
This is the initial version of the governance model we're looking
to implement. It is still very early, and comments and
suggestions are very welcome!
Signed-off-by: Matt Heon <mheon@redhat.com>
