all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Suhail <suhail@bayesians.ca>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: August/November update on qa.guix.gnu.org and related things
Date: Thu, 02 Nov 2023 16:38:29 +0000	[thread overview]
Message-ID: <8734xohzzy.fsf@> (raw)

Christopher Baines <mail@cbaines.net> writes:

>  - The README is published at https://qa.guix.gnu.org/README

The README seems more focused on task planning and TODO items than
explaining how to use the qa.guix.gnu.org website. Could you please
provide a reference for the latter?

Specifically, I submitted a patch some while ago:
<https://qa.guix.gnu.org/issue/66644>. Its QA status is marked as
unknown with a few items highlighted in red. While the UI helps draw
attention to those items, it's not clear (to me) how to remedy them and
who is responsible for doing what. I.e., what are the next steps? I
would like to get that patch reviewed and merged in some way, but I
don't know what, if anything, I can do to help with the matter.

> I'd also really like to see some testing of the patch review feature
> in QA, since I think trying to get people without commit access
> reviewing patches will really help speed up getting things reviewed
> and merged.

Is there a document that outlines how to get started and/or
pre-requisites that one must have before reviewing certain aspects?

-- 
Suhail

This email is not an offer capable of acceptance, does not evidence an
intention to enter into an agreement, has no operative effect until a
definitive agreement is signed in writing by both parties, and that no
party should act in reliance on the email or any representations of the
sender until a definitive agreement is signed in writing by both
parties.

This email may contain information that is privileged, confidential
and/or exempt from disclosure.  No waiver whatsoever is intended by
sending this e-mail which is intended only for the named recipient(s).
Unauthorized use, dissemination or copying is prohibited.  If you
receive this email in error, please notify the sender and destroy all
copies of this email.



             reply	other threads:[~2023-11-02 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 16:38 Suhail [this message]
2023-11-02 20:19 ` August/November update on qa.guix.gnu.org and related things Christopher Baines
2023-11-03  2:48   ` Suhail
2023-11-03  8:36     ` Christopher Baines
2023-11-03 12:21 ` Tomas Volf
2023-11-03 19:45   ` Suhail
  -- strict thread matches above, loose matches on Subject: below --
2023-11-02 11:13 Christopher Baines

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=8734xohzzy.fsf@ \
    --to=suhail@bayesians.ca \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    /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.