REQUEST: migrate github.com/dims/maintainers

[dims]

New repo, staging repo, or migrate existing

migrate dims/maintainers to kubernetes-sigs/maintainers

Is it a staging repo?

no

Requested name for new repository

maintainers

Which Organization should it reside

kubernetes-sigs

Who should have admin access?

dims, nikhita

Who should have write access?

dims, nikhita, MadhavJivrajani, palnabarun, mrbobbytables

Who should be listed as approvers in OWNERS?

dims, nikhita, MadhavJivrajani, palnabarun, mrbobbytables

Who should be listed in SECURITY_CONTACTS?

dims, nikhita

What should the repo description be?

Tools and utilities to parse OWNERS, OWNER_ALIASES in kubernetes related github orgs

What SIG and subproject does this fall under?

contributor-experience

Please provide references to appropriate approval for this new repo

This repository was created to help with auditing / cleaning up etc of OWNERS files during annual reviews.

• https://kubernetes.slack.com/archives/D7HJ6KZJN/p1640054607000700
• https://kubernetes.slack.com/archives/CD6LAC15M/p1639578327074300
• https://kubernetes.slack.com/archives/C1TU9EB9S/p1637062642173400

cc @mrbobbytables @alisondy

Additional context for request

No response

[nikhita]

/assign

[palnabarun]

xref: kubernetes-sigs/maintainers#3 for adding the remaining boilerplate

[palnabarun]

/assign
(taking up some of the tasks)

[justaugustus]

Huge +1 to this!
Also, happy to help do reviews/approvals here!

[mrbobbytables]

LGTM from me, but technically needs approval from our TLs before adopting a subproject. @nikhita has acked, but would like @cblecker to lgtm as well 👍
/assign @cblecker

[cblecker]

Tool is great. The repo name... not so much. "maintainers" is extremely generic. Any suggestions if we can make this more specific? Or does anyone disagree with me?

[justaugustus]

Tool is great. The repo name... not so much. "maintainers" is extremely generic. Any suggestions if we can make this more specific? Or does anyone disagree with me?

Same vibes over here!
I mentioned to @dims when he first unveiled it and he suggested we take the bikeshed as a post-migration step :)

[dims]

+1 to bikeshed a name :)

[cblecker]

We usually don't bikeshed repo names after migrating a repo in though. It's usually a step during this exact process to do any bike shedding.

[nikhita]

Maybe maintainer-stats similar to devstats? 🤔

[mrbobbytables]

FYI - accidentally referenced this issue in 3223, it is not related to org membership requests. XD

[nikhita]

Would really like to move ahead with this, and I'm okay with maintainers for the repo name tbh.

@cblecker do you still have concerns and/or do you have ideas for the rename?

[justaugustus]

+1 to moving along. Bikeshed seems unnecessary here.

[dims]

+1 to move ahead

[cblecker]

sounds like there is consensus to move ahead with the name as is.

lgtm from me

[nikhita]

/assign

will help move this ahead

[nikhita]

Repo has been migrated - https://github.com/kubernetes-sigs/maintainers

Also created:

• Add GitHub teams for maintainers #3300 - to create GitHub teams to grant access
• sig-contribex: add maintainers repo community#6514 - to add the repo to sigs.yaml

Once both PRs merge, we can close this issue.