Merge pull request ubuntu#72 from s-makin/aa-round-three

Next round of AA changes

Author: s-makin

docs/.custom_wordlist.txt

@@ -32,6 +32,7 @@ Bileto
 blocklist
 BOF
 BOFs
+boolean
 bootable
 bootloader
 bootloaders
@@ -62,6 +63,8 @@ cryptographically
 CVE
 CVEs
 datacenter
+Debcrafter
+Debcrafters
 debdiff
 debhelper
 debian
@@ -117,6 +120,7 @@ https
 ia
 IA
 IEEE
+incrementing
 Intersphinx
 ISO
 ISOs
@@ -143,6 +147,8 @@ Lubuntu
 macOS
 Maintainer's
 manpage
+Masters
+matic
 Matic
 meetingology
 mentorship
@@ -184,11 +190,16 @@ Rockcraft
 rst
 rulebook
 RULEs
+runtime
 SCM
 schroots
+SLA
+SLAs
 SLO
 SLOs
 SONAME
+SOP
+SOPs
 SRU
 SRUs
 subdirectory
@@ -234,6 +245,7 @@ VMs
 vorlon
 WCAG
 webops
+whitelist
 WNPP
 wordlist
 workspaces

docs/contributors/advanced/plus-one-maintenance.md

@@ -44,7 +44,7 @@ to tackle on one's free time — and makes for less administrative overhead.
 Furthermore many of the cases eventually need a build, or a combined proposed
 migration which you'd want to track and follow up on for a few days.
 
-However, it is perfectly fine to pick up shifts for shorter durations.
+However, it is perfectly fine to pick up shifts for a shorter duration.
 
 ## The work
 
@@ -56,7 +56,7 @@ report to be posted to the [dedicated Discourse
 category](https://discourse.ubuntu.com/c/pre-release-discussion/plusone-maintenance/415)
 at the end of shift.
 
-The report has two main purposes. The first is to act as a handoff document to
+The report has two main purposes. The first is to act as a hand-off document to
 the next shift, outlining work items that need following up on. Those could be
 fixes needing sponsorship, unfinished investigations, upcoming transitions from
 Debian, etc.
@@ -120,7 +120,7 @@ The priority of these rises along with the cycle. We want as few packages
 failing to build at release time as possible, as it makes security updates of
 these packages that much harder. An interesting aspect of these is that they
 are usually isolated and can be worked on without interfering much with other
-contributers.
+contributors.
 
 Good sources for these are test rebuild results, periodically posted to [the
 ubuntu-devel list](https://lists.ubuntu.com/archives/ubuntu-devel/), as well as

docs/how-ubuntu-is-made/processes/sru-process.md

@@ -1,2 +1,2 @@
-(sru-process)
+(sru-process)=
 # The SRU process overview

docs/staging/AA/aa-museum.md

@@ -1,15 +1,19 @@
 (aa-museum)=
 # Archive Admin museum
 
+```{important}
+This page should not be moved out of the staging area in its current state.
+```
+
 All this content is saved from
 [the Wiki Archive Admin page](https://wiki.ubuntu.com/ArchiveAdministration)
-
+This page houses all the content which is no longer up-to-date, but might
+still be of historical interest.
 
 ## The museum
 
-This section houses all the content which is no longer up-to-date, but might
-still be of historical interest. All of this content is now deprecated and
-you should refer to the main {ref}`archive-administration` documentation.
+All of this content is now deprecated and you should refer to the main
+{ref}`archive-administration` documentation.
 
 
 ### Useful runes
@@ -68,20 +72,25 @@ Archive.
 
   Shows override discrepancies between architectures, which are generally bugs.
 
-* [`http://people.canonical.com/~ubuntu-archive/testing/xenial_probs.html`](http://people.canonical.com/~ubuntu-archive/testing/xenial_probs.html)
+* `http://people.canonical.com/~ubuntu-archive/testing/xenial_probs.html`
+
+  **note, this link 404s and is outdated**
 
   Generated by the half-hourly run of `britney` and indicates packages that are
   uninstallable on Xenial, usually due to missing dependencies or problematic
-  conflicts. **note, this link 404s**
+  conflicts.
+
+* `http://people.canonical.com/~ubuntu-archive/testing/xenial_outdate.html`
 
-* [`http://people.canonical.com/~ubuntu-archive/testing/xenial_outdate.html`](http://people.canonical.com/~ubuntu-archive/testing/xenial_outdate.html)
+  **note, this link 404s and is outdated**
 
   Lists differences between binary and source versions in the Archive. This
   often shows up both build failures (where binaries are out of date for
   particular architectures) but also where a binary is
-  No longer Built from the Source. **note, this link 404s**
+  No longer Built from the Source. 
 
-* [`~ubuntu-archive/NBS/`](https://ubuntu-archive-team.ubuntu.com/NBS/) and [`~ubuntu-archive/nbs.html`](https://ubuntu-archive-team.ubuntu.com/nbs.html)
+* [`~ubuntu-archive/NBS/`](https://ubuntu-archive-team.ubuntu.com/NBS/) and
+  [`~ubuntu-archive/nbs.html`](https://ubuntu-archive-team.ubuntu.com/nbs.html)
 
   This contains a list of binary packages which are Not Built from Source (NBS)
   any more. The files contain the list of reverse dependencies of those packages
@@ -107,7 +116,7 @@ Soyuz stores one chroot per (suite, architecture).
 
 `manage-chroot` allows the following actions upon a specified chroot:
 
-```bash
+```none
 $ ./manage-chroot
 Usage: manage-chroot -a ARCHITECTURE [options] <get|info|remove|set>
 
@@ -116,7 +125,7 @@ manage-chroot: error: You must specify an architecture.
 
 Downloading (`get`) an existing chroot:
 
-```bash
+```none
 $ ./manage-chroot [-s SUITE] <-a ARCH> get
 ```
 
@@ -125,7 +134,7 @@ The chroot will be downloaded and stored in the local disk name as
 
 Uploading (`add`/`update`) a new chroot:
 
-```bash
+```none
 $ ./manage-chroot [-s SUITE] <-a ARCH> set -f <CHROOT_FILE>
 ```
 
@@ -169,7 +178,7 @@ in the usual way.
 This works the same as the `ubuntu-mozilla-security` PPA, above. E.g., using
 `lp:ubuntu-qa-tools/security-tools/unembargo`:
 
-```bash
+```none
 $ unembargo --ppa=ubuntu-security-proposed -r xenial --pocket=proposed gnupg
 ```
 
@@ -179,12 +188,13 @@ $ unembargo --ppa=ubuntu-security-proposed -r xenial --pocket=proposed gnupg
 With the new
 [Stable Release Cadence](https://wiki.ubuntu.com/Kernel/StableReleaseCadence),
 kernels are built in the
-[Kernel Team PPA](https://launchpad.net/~canonical-kernel-team/+archive/ppa)
+[Kernel Team PPA](https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa)
 and then pocket copied to the proposed pocket in the main archive once they are
 ACK-ed.
 
 The two most useful URLs for this process are the
-[Kernel SRU Report](http://status.qa.ubuntu.com/reports/kernel-bugs/reports/sru-report.html),
+Kernel SRU Report `http://status.qa.ubuntu.com/reports/kernel-bugs/reports/sru-report.html`
+(**note that this link is outdated**),
 where you will find links to the tracking bugs (the magnifying glasses), as well
 as the status of each package in each release, and the
 [Kernel SRU workflow](https://wiki.ubuntu.com/Kernel/kernel-sru-workflow),
@@ -194,7 +204,8 @@ on tasks assigned to your team, and only when they're in the *Confirmed* state,
 and when you do, please reassign to yourself and set the task to *Fix Released*
 when you're done".
 
-The [Pending SRU report](https://ubuntu-archive-team.ubuntu.com/pending-sru.html#kernelppa)
+The Pending SRU report `https://ubuntu-archive-team.ubuntu.com/pending-sru.html#kernelppa`
+(**The section for "kernel PPA" referenced in this URL gives a 404**)
 has a section for the kernel PPA which shows all newer kernels in the PPA,
 provides click-able links to open all bugs (with separate CVE bugs), and
 copy-and-paste-able `copy-proposed-kernel` and `sru-accept` commands (both in
@@ -237,7 +248,7 @@ following:
   `-updates`/`-security`. `find-bin-overrides` from `lp:ubuntu-qa-tools` can
   help with this. You use it like so:
 
-  ```bash
+  ```none
   find-bin-overrides <pocket to compare to> <target pocket> <ubuntu release> <source package>=<version in pocket to compare to>,<old abi>,<new abi>
   ```.
   
@@ -247,7 +258,7 @@ following:
   `-release` pocket of Hardy. For the
   `linux-restricted-modules-2.6.24 source package`, you might use:
   
-  ```bash
+  ```none
   $ find-bin-overrides release proposed hardy \
   linux-restricted-modules-2.6.24=2.6.24.12-16.34,2.6.24-16,2.6.24-30
   ## hardy/linux-restricted-modules-2.6.24
@@ -257,7 +268,7 @@ following:
 
   For the `linux` source package, you might use:
 
-  ```bash
+  ```none
   $ find-bin-overrides release proposed hardy linux=2.6.24-16.30,2.6.24-16,2.6.24-30
   ## hardy/linux
   ...
@@ -300,7 +311,7 @@ case, it will report that the package needs to be merged by hand.
 
 The output of the tool looks like this:
 
-```bash
+```none
 $ ./copy-report
 The following packages can be copied safely:
 --------------------------------------------
@@ -334,25 +345,25 @@ built and then cleaned up from the `-proposed` pocket. The process is as follows
 1. When the package builds on all architectures, copy it to the partner release
    pocket (this makes it available to users). E.g.:
 
-  ```bash
+  ```none
   $ ./copy-package -b --auto-approve --from=ubuntu/partner -s xenial-proposed --to-suite xenial adobe-flashplugin
   ```
 
   or to do all at once:
 
-  ```bash
+  ```none
   $ for i in xenial bionic focal groovy; do ./copy-package -b --auto-approve --from=ubuntu/partner -s $i-proposed --to-suite $i adobe-flashplugin ; done
   ```
 
 1. Remove the package from proposed in the partner archive. E.g.:
 
-  ```bash
+  ```none
   $ ./remove-package -A ubuntu/partner -m "copied to release" -s xenial-proposed adobe-flashplugin
   ```
 
   or to do all at once:
 
-  ```bash
+  ```none
   $ for i in xenial bionic focal groovy; do ./remove-package -A ubuntu/partner -m "copied to release" -s $i-proposed adobe-flashplugin ; done
   ```
 
@@ -374,7 +385,7 @@ Most updates available in Debian are automatically synced before
 that were previously in Ubuntu will not be automatically reintroduced. To
 process these interactively:
 
-```bash
+```none
 $ ./auto-sync --new-only
 ```
 
@@ -396,7 +407,7 @@ There are other useful tools in your `PATH` which are invaluable.
 `rmadison` (in the `devscripts` package, run on your client system) examines
 the current state of the archive for a given binary/source package:
 
-```bash
+```none
 $ rmadison dpkg
       dpkg | 1.10.22ubuntu2 |         warty | source, amd64, i386, powerpc
       dpkg | 1.10.22ubuntu2.1 | warty-security | source, amd64, i386, powerpc
@@ -407,7 +418,7 @@ $ rmadison dpkg
       dpkg | 1.13.11ubuntu5 |        dapper | source, amd64, hppa, i386, ia64, powerpc, sparc
 ```
 
-```bash
+```none
 $ rmadison dselect
    dselect | 1.10.22ubuntu2 |         warty | amd64, i386, powerpc
    dselect | 1.10.22ubuntu2.1 | warty-security | amd64, i386, powerpc
@@ -421,7 +432,7 @@ $ rmadison dselect
 Or when used with `-S` and a source package, the source and every binary built
 by it:
 
-```bash
+```none
 $ rmadison -S dpkg
       dpkg | 1.10.22ubuntu2 |         warty | source, amd64, i386, powerpc
       dpkg | 1.10.22ubuntu2.1 | warty-security | source, amd64, i386, powerpc
@@ -453,13 +464,13 @@ $ rmadison -S dpkg
 
 `checkrdepends` lists the reverse dependencies of a given binary:
 
-```bash
+```none
 $ checkrdepends -s zesty -b nm-applet
 ```
 
 or source package:
 
-```bash
+```none
 $ checkrdepends -s zesty network-manager
 ```
 
@@ -514,7 +525,7 @@ Packages in `-proposed` can be moved to `-updates` once they are approved by
 someone from `sru-verification`, and have passed the minimum aging period of
 **7 days**. Use the `sru-release` script from `ubuntu-archive-tools` for this:
 
-```bash
+```none
 $ ./sru-release xenial kdebase
 ```
 
@@ -547,13 +558,13 @@ To publish `firefox` version `22.0+build2-0ubuntu0.12.04.2` from the
 `ubuntu-mozilla-security` PPA to the `-security` pocket of Ubuntu's `precise`
 release, you would do the following:
 
-```bash
+```none
 $ ./copy-package -b --from=~ubuntu-mozilla-security/ubuntu/ppa -s precise --to=ubuntu --to-suite precise-security -e 22.0+build2-0ubuntu0.12.04.2 firefox
 ```
 
 Alternatively, can use `lp:ubuntu-qa-tools/security-tools/unembargo` like so:
 
-```bash
+```none
 $ unembargo --ppa=ubuntu-mozilla-security -r xenial --pocket=proposed chromium-browser
 ```
 
@@ -620,10 +631,8 @@ Additionally, performing the following should be considered:
 
 ### Outdated
 
-```{admonition} Question
-:class: important
-This section is actually marked on the AA page as being outdated. Should we
-keep it for historical interest?
+```{note}
+This section is actually marked on the AA page as being outdated.
 ```
 
 #### Logging in