GNU bug report logs - #64151
[PATCH] etc: Stop making sendemail behave strangely.

Previous Next

Full log

Message #20 received at 64151 <at> debbugs.gnu.org (full text, mbox):

From: Liliana Marie Prikler <liliana.prikler <at> gmail.com>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: Ludovic Courtès <ludo <at> gnu.org>,
 Christopher Baines <mail <at> cbaines.net>, 64151 <at> debbugs.gnu.org
Subject: Re: bug#64151: [PATCH] etc: Stop making sendemail behave strangely.
Date: Wed, 28 Jun 2023 06:30:15 +0200

Am Dienstag, dem 27.06.2023 um 21:14 -0400 schrieb Maxim Cournoyer:
> Hi Liliana,
> 
> Liliana Marie Prikler <liliana.prikler <at> gmail.com> writes:
> > Funny that you'd mention that because for me, debbugs notifications
> > are pretty hit or miss.  A lot of them end up filtered by our
> > benevolent overlords without me having ever read them.
> 
> Maybe you are mistaken about what X-Debbugs-CC does; it doesn't cause
> someone to be subscribed to a specific issue; it's only a CC
> alternative that is a bit nicer in that it will reply with the issue
> number in the reply path, which is mostly useful for new issues that
> haven't gotten a Debbugs number yet.  So I don't think we should
> think of it as a "notification" mechanism, simply a smarter CC for
> Debbugs.
I am not.  Debbugs-CC'd mail simply ends up in the spam folder because
Google sees that

> > 
> > I'd argue that it is wrong to magically install this configuration
> > without any user interaction.  The current setup also causes quite
> > a number of false positives, like a package rename also causing
> > changes in some other scope and hence notifying like five different
> > teams all at once.
> 
> I personally prefer the zero-config approach that maximizes the
> potential of etc/teams.scm and reduces the documentation burden, but
> of course I'm biased :-).  I find the contribution process of Guix
> already complicated enough to not want to add more to it, and welcome
> automation.
There's nothing wrong with automation per se, but you are confusing
automating your own process knowingly with automating someone else's
process without their knowledge or permission.  I'd also argue that
your approach doesn't maximize etc/teams.scm, but rather makes it
exhibit the weirdest behaviours imaginable by applying it blindly.

Cheers

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.