Trim cosign-codeowners list about community HOT 6 CLOSED

Not directly related to this PR but got me thinking :)

I just wanted to throw out some learnings that we had in Knative wrt achieving consensus, so just wanted to share that here as something to think about moving forward. Here's the process as well as some background that we found quite useful.

I think reducing the number of owners is fine, but I'm not quite sure it addresses the fundamental problem of getting the consensus. I'm not sure we need this, but just figured it might be useful to think about :)

https://docs.google.com/document/d/1l7pWR2qyEgmCu1zbYwiufQH6aSM9DnwlJ1xtjuxz4MA/edit#heading=h.rlgskeckhfva

More background / discussions here:
sigstore/cosign#2466

from community.

Feel free to remove me! 👍

from community.

from community.

Should this be based on whether the maintainer is adhering to the community guidelines? For example, if there has been no recent development or reviews, probably should remove the maintainer.
Edit: There are guidelines for inactive members too.

from community.

Should this be based on whether the maintainer is adhering to the community guidelines? For example, if there has been no recent development or reviews, probably should remove the maintainer.
Edit: There are guidelines for inactive members too.

It's best to apply some judgement on stuff like this but definitely base it on the guidelines. I've seen projects trim too aggressively to the point where they don't even have enough people to keep it running and add more people back.

from community.

fun fact, i'm not part of the cosign lol

from community.