GNU bug report logs - #74736
[PATCH v2 0/1] Add Request-For-Comment process.

Previous Next

Package: guix-patches;

Reported by: Noé Lopez <noe <at> xn--no-cja.eu>

Date: Sun, 8 Dec 2024 12:29:02 UTC

Severity: important

Tags: patch

Merged with 66844

Done: Noé Lopez <noe <at> xn--no-cja.eu>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Suhail Singh <suhailsingh247 <at> gmail.com>
To: Simon Tournier <zimon.toutoune <at> gmail.com>
Cc: Arun Isaac <arunisaac <at> systemreboot.net>, guix-maintainers <at> gnu.org, ludo <at> gnu.org, mail <at> cbaines.net, efraim <at> flashner.co.il, rekado <at> elephly.net, Andreas Enge <andreas <at> enge.fr>, guix-devel <at> gnu.org, 74736 <at> debbugs.gnu.org, Janneke Nieuwenhuizen <janneke <at> gnu.org>
Subject: [bug#74736] Guix Common Document process (v7)
Date: Thu, 16 Jan 2025 07:04:14 -0500
Simon Tournier <zimon.toutoune <at> gmail.com> writes:

> That’s why, I proposed (v7) to use the low traffic info-guix for
> announcing and asking for inputs.

info-guix has the following description which, I believe, makes it
well-suited to the task:

"Low-traffic mailing list for announcements to Guix users."

> However, I find better to have the discussion happens inside the bug
> tracker.

Agreed.

> And easier too; because some contributors when replying break the
> email thread (incorrect in-reply-to) then it’s very painful to follow.

Thank you for considering this failure mode.

> Later, using the bug tracker for discussing, it’s also easy to re-read
> all the comments for one willing to understand why we ended up with
> such specific GCD.

Agreed.

-- 
Suhail




This bug report was last modified 90 days ago.

Previous Next


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