unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: Debbugs user tags
Date: Wed, 23 Jun 2021 21:59:00 -0700	[thread overview]
Message-ID: <87r1gramej.fsf@gmail.com> (raw)
In-Reply-To: <87wnqkwuu1.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 23 Jun 2021 15:53:42 +0200")

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

Ludovic Courtès <ludo@gnu.org> writes:

>> * doc/contributing.texi (Contributing): Update the short description of the
>> "Tracking Bugs and Patches" chapter in the menu.
>> (Tracking Bugs and Patches): Split this section into three new subsections,
>> titled "Debbugs", "Debbugs User Interfaces", and "Debbugs Usertags".  Of
>> these, only the "Debbugs Usertags" is actually new.
>
> Wonderful!

I'm glad you like it!  :-)

>> +++ b/doc/contributing.texi
>> @@ -26,7 +26,7 @@ choice.
>>  * Packaging Guidelines::        Growing the distribution.
>>  * Coding Style::                Hygiene of the contributor.
>>  * Submitting Patches::          Share your work.
>> -* Tracking Bugs and Patches::   Using Debbugs.
>> +* Tracking Bugs and Patches::   Keeping it all organized.
>
> You probably have to adjust it in a second place (yeah…).

Other references to "Tracking Bugs and Patches" do exist, but they don't
mention "Using Debbugs," so I don't think they need to be updated.

>> +@menu
>> +* Debbugs:: The official bug and patch tracker.
>> +* Debbugs User Interfaces:: Ways to interact with Debbugs.
>> +* Debbugs Usertags:: Tag reports with custom labels.
>> +@end menu
>
> ‘M-x texinfo-make-menu’ or similar should indent it for you.  :-)

You learn something new every day!

>> +@node Debbugs
>> +@subsection Debbugs
>
> Maybe rename to “The Issue Tracker”, so as to not require knowledge of
> what Debbugs is when skimming through the table of contents?

Sounds good.  I just changed the first subsection, so now it looks like
this:

--8<---------------cut here---------------start------------->8---
@menu
* The Issue Tracker::           The official bug and patch tracker.
* Debbugs User Interfaces::     Ways to interact with Debbugs.
* Debbugs Usertags::            Tag reports with custom labels.
@end menu
--8<---------------cut here---------------end--------------->8---

This seems fine, since the first subsection introduces Debbugs.

>> +Debbugs provides a feature called ``usertags'' that allows any user to
>
> @dfn{usertags}

OK.

>> +In Guix, we are experimenting with usertags to keep track of
>> +architecture-specific issues.  To facilitate collaboration, all our
>> +usertags are associated with the single user @code{guix-devel@@gnu.org}.
>> +The following usertags currently exist for that user:
>> +
>> +@table @code
>> +
>> +@item powerpc64le-linux
>> +The purpose of this usertag is to make it easy to find the issues that
>> +matter most for the @code{powerpc64le-linux} system type.  Please assign
>> +this usertag to issues or patches that affect @code{powerpc64le-linux}
>> +but not other system types.  In addition, you may use it to identify
>> +issues that for some reason are particularly important for the
>> +@code{powerpc64le-linux} system type, even if the issue affects other
>> +system types, too.
>
> Maybe we can already add ‘reproducibility’.
>
> Otherwise LGTM, thank you!
>
> Ludo’.

I added this text:

--8<---------------cut here---------------start------------->8---
@item reproducibility
For issues related to reproducibility.  For example, it would be
appropriate to assign this usertag to a bug report for a package that
fails to build reproducibly.
--8<---------------cut here---------------end--------------->8---

I've gone ahead and committed these changes in
3c86372e36cecaed1ad55675ce32a14b972406bf.  I verified that the Texinfo
manual could be built, and that when viewing it in Info, it looks as
expected.

Please let me know if you'd like any further changes; I'd be happy to
make them.

-- 
Chris

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

  reply	other threads:[~2021-06-24  4:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12  6:40 GNU Guix 1.3.0 released Maxim Cournoyer
2021-05-12 11:43 ` 宋文武
2021-05-12 12:35   ` Mathieu Othacehe
     [not found] ` <Maxim Cournoyer's message of "Wed, 12 May 2021 02:40:39 -0400">
     [not found]   ` <OSZP286MB06642FFB3BB362E2E85BE9D4A3529@OSZP286MB0664.JPNP286.PROD.OUTLOOK.CO M>
2021-05-12 12:02     ` maxxcan--- via
2021-05-15 16:42 ` Ludovic Courtès
2021-05-16 13:18   ` GNU Guix 1.4.0 in September? (was: Re: GNU Guix 1.3.0 released) Maxim Cournoyer
2021-05-16 16:02     ` Vagrant Cascadian
2021-05-16 16:47       ` Julien Lepiller
2021-05-17 12:55     ` zimoun
2021-05-17 14:43       ` Leo Famulari
2021-05-17 15:01         ` GNU Guix 1.4.0 in September? Maxim Cournoyer
2021-05-17 17:35         ` GNU Guix 1.4.0 in September? (was: Re: GNU Guix 1.3.0 released) Bengt Richter
2021-05-17 20:29           ` GNU Guix 1.4.0 in September? Maxim Cournoyer
2021-05-17 20:34       ` Maxim Cournoyer
2021-05-17 20:32     ` Ludovic Courtès
2021-06-16  7:49     ` Chris Marusich
2021-06-20 16:26       ` Debbugs user tags Ludovic Courtès
2021-06-23  2:48         ` Chris Marusich
2021-06-23 13:53           ` Ludovic Courtès
2021-06-24  4:59             ` Chris Marusich [this message]
2021-06-24 19:48       ` GNU Guix 1.4.0 in September? Maxim Cournoyer
2021-06-24 20:48         ` Debbugs Usertags - which user to use? (Was: Re: GNU Guix 1.4.0 in September?) Chris Marusich
2021-06-25  3:23           ` Debbugs Usertags - which user to use? Maxim Cournoyer
2021-07-06  4:22             ` Chris Marusich
2021-07-06 16:10               ` Maxim Cournoyer

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87r1gramej.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).