Shall we add permission limit for subproject

[Colstuwjx]

Hi team,

We have some subprojects from our community, and sometimes the PR approver and reviewer for the subprojects is distinct with the main project, for example, our website docs owner is inside OWNERS.md of the website root, and content/en has its own OWNERS.md, what's more, blog under the content/en is another subproject, and it has its own OWNERS.

The problem is, when someone submitted a PR for blog related issues, docs OWNER and content/en OWNER could also do approve. This action is NOT suitable to the context, since the blog content is subproject from the website, and should be reviewed\approved from the blog subproject OWNERS.

What would you like to be added:
For OWNERS.md, we could add some permission level limitations and overrides, such as the subproject things should ONLY be approved/reviewed by the subproject OWNERS.

Why is this needed:
Currently, we seems not limit to this, and the project OWNERS could do approve/review for subproject PRs without subproject OWNERS reviews. It would make our subproject messy, so we should enhance this level permission controls.

Thanks.

[alvaroaleman]

I believe this can be achieved already by setting no_parent_owners: true in the subprojects OWNERS file, ref: https://github.com/kubernetes/community/blob/master/contributors/guide/owners.md

[Colstuwjx]

Awesome！