You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide a detailed description of the proposed feature
We should combine as many repositories in the Homebrew organisation as possible. This includes moving as many external commands (e.g. homebrew-bundle, homebrew-services) taps into Homebrew/brew and all private repos into Homebrew/private.
After this, when creating new repositories or internet-accessible services with repositories in the Homebrew organisation: we should strive to reuse an existing repositories/service unless it is extremely painful to do otherwise (and, ideally, after discussion with @MikeMcQuaid and getting his 👍🏻).
Note: GitHub Pages sites (e.g. rubydoc.brew.sh, formulae.brew.sh, docs.brew.sh) are fine to be one-repo-per-pages-site.
What is the motivation for the feature?
Many reasons:
external commands are less discoverable than non-external commands and documented inconsistently
external commands rely on either slow public APIs/shelling out or break periodically due to using internal APIs
the more repositories we have: the more we need to sync, run dependabot updates on, check access control for, etc. etc.
How will the feature be relevant to at least 90% of Homebrew users?
It won't be but maintainers will like it.
What alternatives to the feature have been considered?
Doing nothing.
The text was updated successfully, but these errors were encountered:
My sole hesitation is my perception of homebrew-bundle as an example of an external command.
Should a part of this effort include or inspire the creation of a template external command repo since this effort could effectively eliminate the external command repos that Homebrew owns?
Verification
brew install wget
. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.Provide a detailed description of the proposed feature
We should combine as many repositories in the Homebrew organisation as possible. This includes moving as many external commands (e.g. homebrew-bundle, homebrew-services) taps into Homebrew/brew and all private repos into Homebrew/private.
After this, when creating new repositories or internet-accessible services with repositories in the Homebrew organisation: we should strive to reuse an existing repositories/service unless it is extremely painful to do otherwise (and, ideally, after discussion with @MikeMcQuaid and getting his 👍🏻).
Note: GitHub Pages sites (e.g. rubydoc.brew.sh, formulae.brew.sh, docs.brew.sh) are fine to be one-repo-per-pages-site.
What is the motivation for the feature?
Many reasons:
How will the feature be relevant to at least 90% of Homebrew users?
It won't be but maintainers will like it.
What alternatives to the feature have been considered?
Doing nothing.
The text was updated successfully, but these errors were encountered: