Separate OWNERS for cloud/*

Question

Separate OWNERS for cloud/*

karan opened this issue 7 years ago · 5 comments

In the external apiserver world, the provider-specific code that lives in cloud/ is disjoint from the controller. As such, for reviews for any provider, it can be a bad experience to be blocked on development.

We should have separate OWNERS for the provider-specific code, so changes there don't (always) need cluster-api owners approvals.

scheeles commented 7 years ago

sgtm

Answer 1 · 2018-03-01T17:01:55.000Z

From https://github.com/kubernetes/community/blob/master/contributors/guide/owners.md

Each directory that contains a unit of independent code or content may also contain an OWNERS file

Answer 2 · 2018-03-01T17:02:27.000Z

cc @kubernetes/sig-cluster-lifecycle-misc

Answer 3 · 2018-03-01T17:06:48.000Z

cc @mrIncompetent @scheeles @p0lyn0mial

Answer 4 · 2018-04-17T18:54:39.000Z

This issue was moved to kubernetes-sigs/cluster-api#100