Hi Chris,
Chris Marusich <cmmarus...@gmail.com> skribis:
> From f640132745b26b19bd163bc67482e8aea041881b Mon Sep 17 00:00:00 2001
> From: Chris Marusich <cmmarus...@gmail.com>
> Date: Tue, 22 Jun 2021 19:44:18 -0700
> Subject: [PATCH] Document the use of Debbugs usertags.
>
> * 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!
> +++ 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…).
> +@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. :-)
> +@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?
> +Debbugs provides a feature called ``usertags'' that allows any user to
@dfn{usertags}
> +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’.
