all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: guix-devel@gnu.org
Subject: Notes regarding Quality Assurance from yesterday at the Guix Days
Date: Fri, 03 Feb 2023 11:30:37 +0100	[thread overview]
Message-ID: <87pmarf2y8.fsf@cbaines.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]

Here are some rough notes from when I spoke about Quality Assurance,
plus the smaller discussion in the afternoon.

quality issues
 - making sure we know about problems
 - package reproducibility causing problems
 - packages not building in the future
 - quality of packages, how well they match up to that
 - availability of translations
 - documentation

what already exists?
 - the linters
 - the release process
 - patch review
   - QA frontpage
 - package reproducibility information
 - build information from ci.guix.gnu.org/data.guix.guix.gnu
 - guix weather
 - weblate (translations)

things to talk about:
 - qa-frontpage overview (guix build coordinator, guix data service)
 - try and work out what the most important bugs/issues?
 - how to make changes, keep things up to date, patch review, how to do that better


In the smaller discussion, the areas of interest were:

 - Addressing the lack of translations in the qa-frontpage code
 - How to help out
 - Learning more about how current quality assurance related things work

The topics to continue thinking about were:

- Looking at the things in Guix that would help the Guix Data Service
- Adding RSS feed to the QA frontpage
- Look at moving the qa-frontpage, guix-build-coordinator, and
  nar-herder repositories to Savannah
- Time saving, how to make quality assurance things faster

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

                 reply	other threads:[~2023-02-03 10:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pmarf2y8.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.