dnrops
/
homebrew-cask
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Create exceptions_notability_threshold.md (#96934)

This commit is contained in:
Vítor Galvão 2020-12-29 10:03:39 +00:00 committed by GitHub
parent 3747fd2ca3
commit e8da44c3f1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/faq/exceptions_notability_threshold.md Normal file
View File

@ -0,0 +1,9 @@
# Exceptions to the Notability Threshold
Casks which do not reach a minimum notability threshold (see [Rejected Casks FAQ](https://github.com/Homebrew/homebrew-cask/blob/master/doc/faq/rejected_casks.md)) aren’t accepted in the main repositories because the increased maintenance burden doesn’t justify the poor usage numbers they will likely get. This notability check is performed automatically by the audit commands we provide, but its decisions aren’t set in stone. A cask which fails the notability check can be added if it is:
1. A popular app that has their own website but the developers use GitHub for hosting the binaries. That repository won’t be notable but the app may be.
2. Submitted by a maintainer or prolific contributor. A big part of the reasoning for the notability rule is unpopular software garners less attention and the cask gets abandoned, outdated, and broken. Someone with a proven investment in Hombrew Cask is less likely to let that happen for software they depend on.
3. A piece of software that was recently released to great fanfare—everyone is talking about it on Twitter and Hacker News and we’ve even gotten multiple premature submissions for it. That’s a clear case of an app that will reach the threshold in no time so that’s a PR we won’t close immediately (but may wait to merge).
Note none of these exceptions is a guarantee for inclusion, but examples of situations where we may take a second look.