Complete migration to OWNERS file

[jmhbnz]

As part of our setup for sig-etcd we intend to adopt the kubernetes project OWNERS file approach for managing repository and github org permissions automatically as code.

In #16600 we introduced the OWNERS file for etcd.

This pull request is a tidy-up to remove the old MAINTAINERS file approach.

Sub task under: #16367

[fuweid]

LGTM

Thanks!

[jberkus]

We need the MAINTAINERS file for the CNCF. We're currently both a project and a SIG, and the CNCF needs us to have a MAINTAINERs file in this repo (as well as OWNERs), and only this repo. So leave that in place while updating OWNERs.

[ahrtr]

and only this repo

Could you clarify this? Do you mean that we only need to keep the MAINTAINERS in this repo? In other words, we can remove MAINTAINERS files from all other repositories, e.g. bbolt/MAINTAINERS, raft/MAINTAINERS, etc.?

[jberkus]

and only this repo

Could you clarify this? Do you mean that we only need to keep the MAINTAINERS in this repo? In other words, we can remove MAINTAINERS files from all other repositories, e.g. bbolt/MAINTAINERS, raft/MAINTAINERS, etc.?

That's correct. Only the one in this repo matters.

[ahrtr]

That's correct. Only the one in this repo matters.

OK, thx for the clarification.

[jmhbnz]

MAINTAINERS file will no longer be deleted by this PR. Thanks for catching this requirement @jberkus.

[serathius]

@jberkus is right that we need a file that lists project "maintainers", but it doesn't necessarily requires a MAINTAINERS file.

We can just change the file name mentioned in https://github.com/cncf/foundation/blob/main/project-maintainers.csv#L264-L269. In the file there are sigs that directly link to repo https://github.com/kubernetes/community

To make the transition complete (not necessarily in this PR) we should remove the MAINTAINERS file and change https://github.com/cncf/foundation/blob/main/project-maintainers.csv#L264-L269 to link to https://github.com/kubernetes/community/tree/master/sig-etcd#leadership

[jmhbnz]

Thanks for the idea above @serathius. This pull request was discussed during the recent etcd triage meeting (08:24).

We discussed a plan which is:

1. Establish maintainer consensus vote to:
   a. update the cncf maintainers csv file so that it refers to our new OWNERS file.

   b. add a second section to the cncf maintainers csv file to cover the sig-etcd leadership (chairs + tech leads). This is a pattern other projects have used for example Istio or Harbour. Which allows us to resolve some cncf account permission issues without having to have sig chairs defined as an approver aka maintainer in our code OWNERS file.

2. Raise a pr to update the cncf csv file provided the vote passes.

3. Update this pr and proceed with removing MAINTAINERS file here.

@etcd-io/maintainers-etcd can you please give a +1 on this comment or reply with either approval to proceed with this plan or any questions. Thanks! 🙏🏻

[ahrtr]

+1 Thanks all.

[serathius]

+1

[jmhbnz]

Gentle ping @wenjiaswe, @mitake, @ptabor, @spzala - please see the plan outlined in my comment above and provide a +1 or any questions so we can move forward with consensus.

[wenjiaswe]

+1 thank you very much @jmhbnz !

[spzala]

+1 Thanks @jmhbnz

[jmhbnz]

cncf/foundation#666 has now merged so we are good to merge this one now @serathius.