unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Ian Eure <ian@retrospec.tv>,  guix-devel <guix-devel@gnu.org>
Subject: Re: Reducing "You found a bug" reports
Date: Sun, 21 Jul 2024 15:16:34 +0200	[thread overview]
Message-ID: <87v80ynavh.fsf@gnu.org> (raw)
In-Reply-To: <87le1zev1r.fsf@gmail.com> (Simon Tournier's message of "Wed, 17 Jul 2024 20:24:16 +0200")

Hi,

Simon Tournier <zimon.toutoune@gmail.com> skribis:

> On Mon, 17 Jun 2024 at 14:59, Ludovic Courtès <ludo@gnu.org> wrote:
>
>>> It doesn’t feel great to tell users to report a bug for things that
>>> aren’t bugs.  They’re either closed, or never followed up on; it’s a
>>> poor experience on both ends.
>>
>> I agree, it’s pretty bad.
>>
>> I’m fine removing the “report a bug” message, maybe replacing it with
>> some clearer diagnostic and suggestion?  WDYT?
>
> Could we detect if it comes from networking?  Somehow catch the error
> and run some code that checks stuff and so report more “accurate”
> messages?

Someone™ would need to analyze some of the reports we have (some of them
have already been commented on) to determine what happened and whether
that is something we could diagnose differently.

Ludo’.


  reply	other threads:[~2024-07-21 13:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-09  3:04 Reducing "You found a bug" reports Ian Eure
2024-06-17 12:59 ` Ludovic Courtès
2024-06-17 16:09   ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-17 20:40     ` Ricardo Wurmus
2024-07-22 20:48     ` Attila Lendvai
2024-07-17 18:24   ` Simon Tournier
2024-07-21 13:16     ` Ludovic Courtès [this message]
2024-07-22 11:30       ` Simon Tournier
2024-07-22 17:43         ` Suhail Singh
2024-09-10 14:51 ` toward a plan? (was Re: Reducing "You found a bug" reports) Simon Tournier
2024-09-11  0:20   ` Suhail Singh
  -- strict thread matches above, loose matches on Subject: below --
2024-07-23 20:45 Reducing "You found a bug" reports chris

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=87v80ynavh.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ian@retrospec.tv \
    --cc=zimon.toutoune@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).