Repository navigation
Simplify committer team management #438
Description
Activity
Suggestion:
- Use
.project/maintainers.yamlas the canonical list, adding comments to document their affiliation - Remove the contents of
cilium/cilium/MAINTAINERS.md. We could leave a reference to that.project/maintainers.yamlfile for ease of navigation - Update
cilium/community/GOVERNANCE.mdaccordingly
I am hoping that the CNCF tooling will make it easy to find the up-to-date affiliations for each maintainer so we wouldn't have to update the
.project/maintainers.yamlfile when people move, but...one step at a time! Strictly speaking I don't think we document anywhere keeping the affiliation up to date, though it seems common sense.- Use
I'm fine with that as an intermediate step, though I would prefer that over time this cilium/community repo becomes the source of truth for all Cilium org membership management. It already holds the primary definition for most teams, so it'd be nice not to complicate things for other community members by getting them to interact with the
.projectrepo only for this specific case.
Currently there's three Cilium-managed repositories that need to be updated when a committer is added to the Cilium committer group, as documented in this PR:
#437
It would be nice to simplify this down, ideally defining that membership once in this repository. If necessary, we can propagate this definition out to any other relevant repositories (notably, https://github.com/cilium/.project).