- 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!
As discussed at the AGM:
- Only allow formula/cask forks to be used when either blessed by
the source or used by two other major distributions,
- Further elaborate and tweak reasons to deprecate/disable formulae.
- Allow more versioned formulae when widely used.
- Add a document (based on above) for deprecating/disabling casks.
While we're here:
- let VSCode Markdown linting remove the trailing `!` from an
Acceptable Casks heading
This is based on the discussion at Homebrew/homebrew-core#91368.
A few reasons why we don't want to deprecate formulae that have
dependents:
1. This results in displaying warning messages to (at least some) users
that they can't do anything about.
2. `test-bot` does not test deprecated formulae, so we risk breaking
dependent formulae when one of its dependencies is not tested.
3. It is much harder to commit to a disable date for formulae with
dependents because we don't know when we'll be able to wean
dependents off of a deprecated formula.
I think it's important to have a disable date in mind when we deprecate
formulae. Otherwise, we might end up leaving formulae deprecated
indefinitely. This is bad because it teaches users to not take
deprecation warnings seriously.
