Move not-easily-convertible files to main repo; remove deprecated files

https://groups.google.com/g/qubes-devel/c/ASj7tehn1G0/m/jhLmFjdMBwAJ

project-security/canary-checklist.md

@@ -1,24 +0,0 @@
----
-lang: en
-layout: doc
-permalink: /security/canary/checklist/
-redirect_from:
-- /security/canaries/checklist/
-ref: 216
-title: Qubes canary checklist
----
-
-## Preparation
-
-* Draft canary and push to private repository
-* Finalize canary, sign, and add signed tags
-
-## Announcement
-
-* Push canary to public repository
-* Publish a [news post](/news/) using the [Canary
-  Template](/security/canary/template/)
-* Send the content of the news post to the appropriate [mailing
-  lists](/support/)
-* Share link to news post on social media
-* Set a reminder for the next canary

project-security/canary-template.md

@@ -1,12 +0,0 @@
----
-lang: en
-layout: doc
-permalink: /security/canary/template/
-redirect_from:
-- /security/canaries/template/
-- /doc/canaries/template/
-redirect_to:
-- https://github.com/QubesOS/qubes-secpack/blob/master/canaries/canary-template.txt
-ref: 212
-title: Qubes canary template
----

project-security/canary.md

@@ -1,29 +0,0 @@
----
-lang: en
-layout: doc
-permalink: /security/canary/
-redirect_from:
-- /security/canaries/
-- /doc/canaries/
-ref: 208
-title: Qubes canaries
----
-
-A **Qubes canary** is a security announcement periodically issued by the [Qubes
-security team](/security/#qubes-security-team) through the [Qubes security
-pack](/security/pack/) consisting of several statements to the effect that the
-signers of the canary have not been compromised. The idea is that, as long as
-signed canaries including such statements continue to be published, all is
-well. However, if the canaries should suddenly cease, if one or more signers
-begin declining to sign them, or if the included statements change
-significantly without plausible explanation, then this may indicate that
-something has gone wrong.
-
-The name originates from the practice in which miners would bring caged
-canaries into coal mines. If the level of methane gas in the mine reached a
-dangerous level, the canary would die, indicating to miners that they should
-evacuate. See [Wikipedia: warrant
-canary](https://en.wikipedia.org/wiki/Warrant_canary) for more information, but
-bear in mind that Qubes Canaries are not strictly limited to legal warrants.
-
-## Full list

project-security/pgp-keys.md

@@ -1,8 +0,0 @@
----
-lang: en
-layout: doc
-permalink: /security/pgp-keys/
-redirect_to: https://keys.qubes-os.org/keys/
-ref: 250
-title: PGP keys
----

project-security/qsb-checklist.md

@@ -1,26 +0,0 @@
----
-lang: en
-layout: doc
-permalink: /security/qsb/checklist/
-redirect_from:
-- /security/bulletins/checklist/
-- /doc/security-bulletins/checklist/
-ref: 215
-title: Qubes security bulletin (QSB) checklist
----
-
-## Preparation
-
-* Draft QSB and push to private repository
-* Build fixed packages
-* Finalize QSB, sign, and add signed tags
-
-## Announcement
-
-* Upload packages to `security-testing` and `current-testing` repositories
-* Push QSB to public repository
-* Publish a [news post](/news/) using the [QSB
-  Template](/security/qsb/template/)
-* Send the content of the news post to the appropriate [mailing
-  lists](/support/)
-* Share link to news post on social media

project-security/qsb-template.md

@@ -1,12 +0,0 @@
----
-lang: en
-layout: doc
-permalink: /security/qsb/template/
-redirect_from:
-- /security/bulletins/template/
-- /doc/security-bulletins/template/
-redirect_to:
-- https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-template.txt
-ref: 209
-title: Qubes security bulletin (QSB) template
----

project-security/qsb.md

@@ -1,23 +0,0 @@
----
-lang: en
-layout: doc
-permalink: /security/qsb/
-redirect_from:
-- /security/bulletins/
-- /doc/security-bulletins/
-- /en/doc/security-bulletins/
-- /doc/SecurityBulletins/
-- /wiki/SecurityBulletins/
-- /trac/wiki/SecurityBulletins/
-ref: 218
-title: Qubes security bulletins (QSBs)
----
-
-A **Qubes security bulletin (QSB)** is a security announcement issued by the
-[Qubes security team](/security/#qubes-security-team) through the [Qubes
-security pack](/security/pack/). A QSB typically provides a summary and impact
-analysis of one or more recently-discovered software vulnerabilities, including
-details about patching to address them. For Xen Security Advisories (XSAs), see
-the [XSA tracker](/security/xsa/).
-
-## Full list

project-security/xsa.md

@@ -1,42 +0,0 @@
----
-lang: en
-layout: doc
-permalink: /security/xsa/
-ref: 214
-title: Xen security advisory (XSA) tracker
----
-
-This tracker shows whether Qubes OS is affected by any given [Xen security
-advisory (XSA)](https://xenbits.xen.org/xsa/). Shortly after a new XSA is
-published, we will add a new row to this tracker. Whenever Qubes is
-significantly affected by an XSA, a [Qubes security bulletin
-(QSB)](/security/qsb/) is published, and a link to that QSB is added to
-the row for the associated XSA.
-
-Under the "Is Qubes Affected?" column, there are two possible values: **Yes**
-or **No**.
-
-* **Yes** means that the *security* of Qubes OS *is* affected.
-* **No** means that the *security* of Qubes OS is *not* affected.
-
-## Important notes
-
-* For the purpose of this tracker, we do *not* classify mere [denial-of-service
-  (DoS) attacks](https://en.wikipedia.org/wiki/Denial-of-service_attack) as
-  affecting the *security* of Qubes OS. Therefore, if an XSA pertains *only* to
-  DoS attacks against Qubes, the value in the "Is Qubes Affected?" column will
-  be **No**.
-* For simplicity, we use the present tense ("is affected") throughout this
-  page, but this does **not** necessarily mean that up-to-date Qubes
-  installations are *currently* affected by any particular XSA. In fact, it is
-  extremely unlikely that any up-to-date Qubes installations are vulnerable to
-  any XSAs on this page, since patches are almost always published concurrently
-  with QSBs. Please read the QSB (if any) for each XSA for patching details.
-* Embargoed XSAs are excluded from this tracker until they are publicly
-  released, since the [Xen security
-  policy](https://www.xenproject.org/security-policy.html) does not permit us
-  to state whether Qubes is affected prior to the embargo date.
-* Unused and withdrawn XSA numbers are included in the tracker for the sake of
-  completeness, but they are excluded from the [statistics](#statistics)
-  section for the sake of accuracy.
-* All dates are in UTC.

user/downloading-installing-upgrading/downloads.md

@@ -1,11 +0,0 @@
----
-lang: en
-layout: site
-permalink: /downloads/
-redirect_from:
-- /doc/QubesDownloads/
-- /wiki/QubesDownloads/
-ref: 2
-title: Download Qubes OS
----
-{% include downloads.html %}

user/hardware/hcl.md

@@ -1,16 +0,0 @@
----
-lang: en
-layout: hcl
-model: all
-permalink: /hcl/
-redirect_from:
-- /doc/hcl/
-- /compatible-hardware/
-- /en/doc/hcl/
-- /doc/HCL/
-- /wiki/HCL/
-- /wiki/HCLR1/
-- /wiki/HCL-R2B2/
-ref: 143
-title: Hardware compatibility list (HCL)
----