How to vote in codeowner changes (update 1) #6297
hcgatewood
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How to vote in codeowner changes (update 1)
This Discussion is the first update to #5524. See that Discussion for desiderata.
The current pain point is insufficient votes for common/straightforward codeowner motions. The high-level change will be a shift away from time-bounded vote periods to vote-bounded vote periods. That is, the motion stays open until sufficient votes are achieved.
Change 0: prune outdated codeowners
Preamble: there are a number of codeowners who have rolled off the project, who we can remove.
This will reduce our total number of codeowners to 23, requiring 12 for majority.
We will institute this change via a codeowner change vote following the process outlined below.
Change 1: coordinate votes via email+trusted admin
The bot process outlined in the previous discussion isn't resilient against codeowner non-responsiveness. Instead, we will have Gale (gmccommons@linuxfoundation.org) handle coordinating votes by sending out respective emails to the codeowners email list. Each codeowner will reply to Gale (not reply-all) with their vote.
From there, Gale can handle pinging non-responsive codeowners until sufficient votes are achieved for an actionable outcome ("yes", "no", "split into separate motions"). She can also record and track votes (privately), to aid in identifying consistently non-responsive codeowners.
In the future, perennial non-responsiveness can be handled systematically, but for now we assume pinging reminders will be sufficient.
Beta Was this translation helpful? Give feedback.
All reactions