- At the AGM we formed an ad-hoc documentation working group.
- One of our ideas was that we should have a last reviewed date for
documentation, so that we can periodically implement a review
mechanism (GitHub Actions posts to Slack for a regular documentation
outdatedness check?) to track how old docs are and ensure they're
still relevant.
- This is a first step towards that goal, by adding a `last_review_date`
to the metadata of all docs with a date of earlier than Homebrew's
inception because everything needs reviewing so that we start from a
good base!
These are changes that were made in the private repository mirror
and either voted on by members already (where they were changes) or
were agreed clarifications on existing policy.
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
- I tried to set up the Project Leader election in OpaVote and couldn't find "Schultz Condorcet" in the list of methods. Let's save the next person who does this a click by specifying its alternative name that _is_ in OpaVote, "beatpath".
Anywhere we can use `blob/master` we can use `blob/HEAD` instead. This
will make life easier if we ever rename our default branch in future
(once/if Git and GitHub provides the necessary tooling to do so).
