Skip to content

Fix root OWNERS approvers #93637

New issue
Jump to bottom
New issue
Jump to bottom
Closed
Closed
Fix root OWNERS approvers#93637
Labels
committee/steeringDenotes an issue or PR intended to be handled by the steering committee.kind/bugCategorizes issue or PR as related to a bug.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.
@dims

Description

@dims
dims
opened on Aug 2, 2020
Preface: IMO, we should not fix root OWNERS approvers by adding more people to it. We should fix it by distributing the 
responsibility (per area) to SIG TLs, and sub-project TLs. I actually think we should consider removing folks from root OWNERS approvers.

Follow up from: #85638 (comment)

@bgrant0607 @brendandburns @dchen1107 @lavalamp @liggitt @smarterclayton @thockin @wojtek-t , your thoughts please!

It's been a while since the previous discussion in #85638. So at this point either we move forward by implementing what @lavalamp mentions above or document steps to add someone to the root OWNERS. Let's pick one and move on.

Metadata

Assignees

No one assigned

    Labels

    committee/steeringDenotes an issue or PR intended to be handled by the steering committee.kind/bugCategorizes issue or PR as related to a bug.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions