Remove Homebrew Cask documentation.

3 files changed, 0 insertions, 47 deletions

diff --git a/Library/Homebrew/cask/doc/faq/apps_with_malware.md b/Library/Homebrew/cask/doc/faq/apps_with_malware.md
deleted file mode 100644
index 825c2af14..000000000
--- a/Library/Homebrew/cask/doc/faq/apps_with_malware.md
+++ /dev/null
@@ -1,13 +0,0 @@
-# Apps that bundle malware
-
-Unfortunately, in the world of software there are bad actors that bundle malware with their apps. Even so, Homebrew-Cask has long decided it is not a gatekeeper ([macOS already has one](https://support.apple.com/en-us/HT202491)) and [users are expected to know about the software they are installing](not_a_discoverability_service.md). This means we will not remove casks that link to these apps. We have several reasons for this, summarised in [a comment on issue #21399](https://github.com/caskroom/homebrew-cask/issues/21399#issuecomment-223148829).
-
-Within that context, we would still like for users to enjoy some kind of protection while minimising occurrences of legitimate developers being branded as malware carriers. We feel removing casks is an ineffective band-aid and the issue needs to be tackled earlier in the chain: at the macOS level.
-
-If an app that bundles malware was not signed with an Apple Developer ID and you purposefully disabled or bypassed Gatekeeper, no action will be taken on our part. When you disable security features, you do so at your own risk. If, however, an app that bundles malware is signed, Apple can revoke its permissions and it will no longer run on the computers of users that keep security features on — we all benefit, Homebrew-Cask users or not. **Note that for the time being, Homebrew-Cask will not quarantine download files. See [issue #22388](https://github.com/caskroom/homebrew-cask/issues/22388)**.
-
-To report a signed app that bundles malware, follow these steps:
-
-* Go to [Apple’s Bug Reporter](https://bugreport.apple.com/) and report the app that bundles malware. Be as precise as possible about how you know it bundles malware, and what steps reproduce your conclusions. Be sure to include relevant URLs, such as the app’s homepage.
-* Make the report public at [Open Radar](http://www.openradar.me/).
-* Submit a pull request with a [`malware` `caveat`](https://github.com/caskroom/homebrew-cask/blob/master/doc/cask_language_reference/stanzas/caveats.md#caveats-mini-dsl).
diff --git a/Library/Homebrew/cask/doc/faq/not_a_discoverability_service.md b/Library/Homebrew/cask/doc/faq/not_a_discoverability_service.md
deleted file mode 100644
index 022a02d5e..000000000
--- a/Library/Homebrew/cask/doc/faq/not_a_discoverability_service.md
+++ /dev/null
@@ -1,15 +0,0 @@
-# Homebrew-Cask is not a discoverability service
-
-Ever since the inception of Homebrew-Cask, various requests fell under the umbrella of this reply. Though a somewhat popular request, after careful consideration on multiple occasions we’ve always come back to the same conclusion: we’re not a discoverability service and our users are expected to have reasonable knowledge about the apps they’re installing through us before doing so.
-
-Examples of requests under this same theme:
-
-+ [Separate by categories](https://github.com/caskroom/homebrew-cask/issues/5425).
-+ [Rank by popularity](https://github.com/caskroom/homebrew-cask/issues/4323).
-+ [Add descriptions](https://github.com/caskroom/homebrew-cask/issues/16089).
-
-Amongst other things, the logistics of such requests are unsustainable for Homebrew-Cask. Before making a request of this nature, you must read through those issues, as well as any other issues they link to, to get a full understanding of why that is the case, and why “but project *x* does *y*” arguments aren’t applicable, and not every package manager is the same.
-
-You should also be able to present clear actionable fixes to those concerns. Simply asking for it without solutions will get your issue closed.
-
-There is a difference between discoverability and searchability, however, and while the former (finding new apps you didn’t know about) is unlikely to ever become part of our goals, the later (identifying the app you know about and want to install) is indeed important to us, and we continue to work on it.
diff --git a/Library/Homebrew/cask/doc/faq/rejected_casks.md b/Library/Homebrew/cask/doc/faq/rejected_casks.md
deleted file mode 100644
index e62a286c1..000000000
--- a/Library/Homebrew/cask/doc/faq/rejected_casks.md
+++ /dev/null
@@ -1,19 +0,0 @@
-# Rejected Casks
-
-Before submitting a Cask to any of our repos, you must read [our documentation on acceptable Casks](../development/adding_a_cask.md#finding-a-home-for-your-cask) and perform a (at least quick) search to see if there were any previous attempts to introduce it.
-
-Common reasons to reject a Cask entirely:
-
-+ We have strong reasons to believe including the Cask can put the whole project at risk. Happened only once so far, [with Popcorn Time](https://github.com/caskroom/homebrew-cask/pull/3954).
-+ The app is a trial version, and the only way to acquire the full version is through the Mac App Store ([documented](../development/adding_a_cask.md#trial-and-freemium-versions)).
-  + Similarly (and trickier to spot), the app has moved to the Mac App Store but still provides old versions via direct download. We reject these in all official repos so users don’t get stuck using an old version, wrongly thinking they’re using the most up-to-date one (which, amongst other things, might be a security risk).
-+ The app is both open-source and CLI-only (i.e. it only uses the `binary` artifact). In that case, and [in the spirit of deduplication](https://github.com/caskroom/homebrew-cask/issues/15603), submit it first to [Homebrew](https://github.com/Homebrew/homebrew). If it is rejected there, you may then try again in Homebrew-Cask (link us to the issue on Homebrew so we can see their reasoning for rejection).
-+ The app is open-source and has a GUI but no compiled versions (or only old ones) are provided. It’s better to have them in [Homebrew](https://github.com/Homebrew/homebrew) so users don’t get perpetually outdated versions. Examples include [`mpv`](https://github.com/caskroom/homebrew-cask/pull/20483) and [`gedit`](https://github.com/caskroom/homebrew-cask/pull/23360).
-+ The app has been rejected before due to an issue we cannot fix, and this new submission doesn’t fix that . An example would be [the first submission of `soapui`](https://github.com/caskroom/homebrew-cask/pull/4939), whose installation problems were not fixed in the two subsequent submissions ([#9969](https://github.com/caskroom/homebrew-cask/pull/9969), [#10606](https://github.com/caskroom/homebrew-cask/pull/10606)).
-+ The Cask is a duplicate. These submissions mostly occur when the [token reference](../cask_language_reference/token_reference.md) was not followed.
-+ The download URL for the app is both behind a login/registration form and from a host that differs from the homepage, meaning users can’t easily verify its authenticity. [alehouse/homebrew-unofficial](https://github.com/alehouse/homebrew-unofficial) is a sister repo where you may wish to submit your cask.
-+ The author has [specifically asked us not to include it](https://github.com/caskroom/homebrew-cask/pull/5342).
-
-Common reasons to reject a Cask from the main repo:
-
-+ The app is an alternate edition or a legacy or development version of a Cask already in the main repo, and as such should be submitted to [caskroom/versions](https://github.com/caskroom/homebrew-versions) ([documented](../development/adding_a_cask.md#beta-unstable-development-nightly-legacy-or-alternative-versions)). Common offenders include [Sublime Text 3](https://github.com/caskroom/homebrew-cask/search?utf8=%E2%9C%93&q=sublime+text+3&type=Issues) and [Firefox Developer Edition](https://github.com/caskroom/homebrew-cask/search?q=firefox+developer+edition&type=Issues&utf8=%E2%9C%93).