01/02: website: Update draft post on the QA front-page.

[Christopher Baines]

cbaines pushed a commit to branch master
in repository guix-artwork.

commit 92eb51b5ef8cdbde344ec7c62212d6bb394e4488
Author: Christopher Baines <mail@cbaines.net>
AuthorDate: Tue Sep 12 15:23:05 2023 +0100

    website: Update draft post on the QA front-page.
    
    * website/drafts/progress-on-the-qa-frontpage.md: Update.
---
 website/drafts/progress-on-the-qa-frontpage.md | 39 +++++++++++---------------
 1 file changed, 17 insertions(+), 22 deletions(-)

diff --git a/website/drafts/progress-on-the-qa-frontpage.md 
b/website/drafts/progress-on-the-qa-frontpage.md
index 9a897f0..13f84d7 100644
--- a/website/drafts/progress-on-the-qa-frontpage.md
+++ b/website/drafts/progress-on-the-qa-frontpage.md
@@ -15,18 +15,15 @@ software, the term testing is normally used.  While Guix is 
software,
 and has tests, much more than those tests are needed to maintain Guix
 as a distribution.
 
-So what might quality mean in the context of Guix as a distribution?
-This will differ from person to person, but these are some common
-concerns:
-
- - Packages not building
-    - Either now or in the future (as is the case with so-called
-      [*time bombs*](https://issues.guix.gnu.org/56137))
-    - Packages building reproducibly
-    - Packages building on or for a specific architecture
+So what might quality relate to in the context of Guix as a
+distribution?  This will differ from person to person, but these are
+some common concerns:
 
+ - Packages successfully building (both now, and without any
+   [*time bombs*](https://issues.guix.gnu.org/56137) for the future)
  - The packaged software functioning correctly
-
+ - Packages building on or for a specific architecture
+ - Packages building reproducibly
  - Availability of translations for the package definitions
 
 # Tooling to help with Quality Assurance
@@ -34,13 +31,13 @@ concerns:
 There's a range of tools to help maintain Guix.  The [package
 linters](https://guix.gnu.org/en/manual/en/html_node/Invoking-guix-lint.html)
 are a set of simple tools, they cover basic things from the naming of
-packages to more complicated checkers like the validity of the
-home-page URL and the formatting of the package definition.
+packages to more complicated checkers that look for security issues
+for example.
 
 The [`guix 
weather`](https://guix.gnu.org/en/manual/en/html_node/Invoking-guix-weather.html)
 tool looks at substitute availability information and can indicate how
 many substitutes are available for the current Guix and system.  The
-[guix 
challenge](https://guix.gnu.org/en/manual/en/html_node/Invoking-guix-challenge.html)
+[`guix 
challenge`](https://guix.gnu.org/en/manual/en/html_node/Invoking-guix-challenge.html)
 tool is similar, but it highlights package reproducibility issues,
 which is when the substitutes and local store items (if available)
 differ.
@@ -51,10 +48,10 @@ which can provide information on how many translations are 
available.
 
 # The QA front-page
 
-Then there's the relatively new Quality Assurance (QA) front-page, the
-aim of which is to bring together some of the existing Quality
-Assurance related information, as well as new being a good place to do
-additional QA tasks.
+Then there's the relatively new [Quality Assurance (QA)
+front-page](https://qa.guix.gnu.org/), the aim of which is to bring
+together some of the existing Quality Assurance related information,
+as well as new being a good place to do additional QA tasks.
 
 The QA front-page
 [started](https://lists.gnu.org/archive/html/guix-devel/2022-09/msg00054.html)
@@ -62,7 +59,7 @@ as a service to coordinate automated testing for patches. 
When a patch
 or patch series is submitted to guix-patches@gnu.org, it is
 automatically applied to create a branch; then once the information is
 available from the [Data Service](https://data.qa.guix.gnu.org/) about
-this branch, the QA frontpage web interface lets you view which
+this branch, the QA front-page web interface lets you view which
 packages were modified and submits builds for these changes to the
 [Build 
Coordinator](https://guix.gnu.org/en/blog/2021/building-derivations-how-complicated-can-it-be/)
 behind 
[bordeaux.guix.gnu.org](https://guix.gnu.org/en/blog/2021/substitutes-now-also-available-from-bordeauxguixgnuorg/)
@@ -102,10 +99,8 @@ the package changes and substitute availability.
 
 There's also plenty of ways to contribute to the QA front-page and
 connected tools.  You can find some ideas and information on how to
-run the service in the
-[README](https://git.savannah.gnu.org/cgit/guix/qa-frontpage.git/tree/README.org)
-and if you have any questions or patches, please email
-`guix-devel@gnu.org`.
+run the service in the [README](https://qa.guix.gnu.org/README) and if
+you have any questions or patches, please email `guix-devel@gnu.org`.
 
 # Acknowledgments