Homebrew-Governance: import merged PRs from homebrew-governance-private #14482

MikeMcQuaid · 2023-02-02T17:31:30Z

These PRs were all approved by the majority of the PLC and the majority of them approved by the majority of the TSC. They are being put here for a members vote, ideally before the AGM.

Replace some "Owners" with "billing managers" and "moderators"
- Now that GitHub has more granular roles available such as "billing managers" and "moderators": let's tighten up our security posture by only have 3 folks who need to be "Owners" rather than 10.
Max two PLC terms
- We discussed this one year terms last year but this seems a better solution. Given we refresh maintainers, TSC and the Project Leader yearly: this seems more consistent, responsive and fair. Note this would only apply to candidates for the PLC from 2024.
Tweak nomination rules
- Do not require any nomination: any member can run for the PLC. This simplifies the procedure: no nomination vote has to be done inside the old PLC. Members do not need to go and find someone to sponsor them. Just apply and let the vote begin. Ask to write down the intentions and keep a candidate list by using a Slack channel, to keep track of everything
Mandate that the PLC report their activities
- Mandating that the PLC report back their actions throughout the year. The wording here is intentionally strong - I feel it is very important for the health of the PLC and the membership for this to be stuck to.
Don't need financial statements, have OpenCollective
- Now that we have an open, publicly readable ledger of all our financial transactions: there does not seem to be any need to continue to have the PLC re-publish reports of our finances (which were hidden to all but the PLC in our SFC days).
Make maintainer removal more explicit.
- Improve this guidelines to provide more evidence for why, what and how this process occurs
- Allow maintainers to appeal the decision of the project leader
- Allow the project leader to re-request this vote if no progress is made
Clarifies maintainer nomination process language/formatting

This PR will be voted on by @Homebrew/members before it is merged (hopefully by or at the AGM on Monday next week).

These PRs were all approved by the majority of the PLC and the majority of them approved by the majority of the TSC. They are being put here for a members vote, ideally before the AGM. - Replace some "Owners" with "billing managers" and "moderators" - Now that GitHub has more granular roles available such as "billing managers" and "moderators": let's tighten up our security posture by only have 3 folks who need to be "Owners" rather than 10. - Max two PLC terms - We discussed this one year terms last year but this seems a better solution. Given we refresh maintainers, TSC and the Project Leader yearly: this seems more consistent, responsive and fair. Note this would only apply to candidates for the PLC from 2024. - Tweak nomination rules - Do not require any nomination: any member can run for the PLC. This simplifies the procedure: no nomination vote has to be done inside the old PLC. Members do not need to go and find someone to sponsor them. Just apply and let the vote begin. Ask to write down the intentions and keep a candidate list by using a Slack channel, to keep track of everything - Mandate that the PLC report their activities - Mandating that the PLC report back their actions throughout the year. The wording here is intentionally strong - I feel it is very important for the health of the PLC and the membership for this to be stuck to. - Don't need financial statements, have OpenCollective - Now that we have an open, publicly readable ledger of all our financial transactions: there does not seem to be any need to continue to have the PLC re-publish reports of our finances (which were hidden to all but the PLC in our SFC days). - Make maintainer removal more explicit. - Improve this guidelines to provide more evidence for why, what and how this process occurs - Allow maintainers to appeal the decision of the project leader - Allow the project leader to re-request this vote if no progress is made - Clarifies maintainer nomination process language/formatting

BrewTestBot · 2023-02-02T17:31:45Z

Review period will end on 2023-02-03 at 17:31:30 UTC.

BrewTestBot · 2023-02-02T17:32:53Z

Review period skipped due to critical label.

MikeMcQuaid · 2023-02-02T17:49:19Z

I have also updated the New-Maintainer-Checklist based on assuming the above passes. This should not be consider part of what is being voted on but more the logical consequences.

issyl0

As a member, I vote yes.

issyl0 · 2023-02-03T08:20:47Z

The OpaVote for this is now live for Homebrew members, please leave your votes yes/no in there.

Rylan12 · 2023-02-03T08:33:10Z

docs/Homebrew-Governance.md

 ## 8. Maintainers

 1. All maintainers are automatically members. Some, not all, members are maintainers.

 2. Maintainers are members with commit/write-access to at least one of: Homebrew/brew, Homebrew/homebrew-core, Homebrew/homebrew-cask.

-3. New maintainers can be nominated by any existing maintainer. They require one approval from the Project Leader or a member of the TSC and no opposition from these people in a 24 hour "working" period (i.e. 7pm on a Friday waits until 7pm on a Monday). If there is opposition, it will be subject to a TSC Slack vote with a majority taking effect after a week.
+3. New maintainers can be nominated by any existing maintainer. To become a maintainer, a nomination requires approval from one of the PL or any member of the TSC with no opposition from any these people within a 24 hour period excluding 19:00 UTC on Friday until 19:00 UTC on the following Monday. If there is opposition, the TSC must vote on the nomination in the #tsc private Slack channel, with the vote closing after a week or when a majority of the TSC has voted. The nomination will succeed by simple majority vote of the votes cast.


For consistency with `#members` above

Suggested change

3. New maintainers can be nominated by any existing maintainer. To become a maintainer, a nomination requires approval from one of the PL or any member of the TSC with no opposition from any these people within a 24 hour period excluding 19:00 UTC on Friday until 19:00 UTC on the following Monday. If there is opposition, the TSC must vote on the nomination in the #tsc private Slack channel, with the vote closing after a week or when a majority of the TSC has voted. The nomination will succeed by simple majority vote of the votes cast.

3. New maintainers can be nominated by any existing maintainer. To become a maintainer, a nomination requires approval from one of the PL or any member of the TSC with no opposition from any these people within a 24 hour period excluding 19:00 UTC on Friday until 19:00 UTC on the following Monday. If there is opposition, the TSC must vote on the nomination in the `#tsc` private Slack channel, with the vote closing after a week or when a majority of the TSC has voted. The nomination will succeed by simple majority vote of the votes cast.

Rylan12 · 2023-02-03T08:42:06Z