From: jbranso@dismail.de
To: "Ricardo Wurmus" <rekado@elephly.net>,
"zimoun" <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org, "GNU Guix maintainers" <guix-maintainers@gnu.org>
Subject: Re: proposal: guix-mentors@gnu.org list/alias
Date: Fri, 03 Jun 2022 10:53:13 +0000 [thread overview]
Message-ID: <5d5519fa8b9806020020c9c0de27a855@dismail.de> (raw)
In-Reply-To: <87k09zxzpp.fsf@elephly.net>
June 2, 2022 4:00 AM, "Ricardo Wurmus" <rekado@elephly.net> wrote:
> zimoun <zimon.toutoune@gmail.com> writes:
>
>> Ah sorry, I overcomplicate the discussion. :-)
>
> Hah, no worries! It’s worth discussing this before we implement a
> workflow that ends up being *more* confusing than the status quo.
>
>> To me, it could be nice to have a tiny script (or Guix extension or
>> subcommand), maybe in etc/ which simplifies the workflow; something
>> similar to ’etc/committer.scm’.
>>
>> The workflow would be:
>>
>> $ edit code
>> $ git commit
>> $ etc/mentoring.scm
>>
>> where etc/mentoring would generate the patch(es), add X-Debbugs-CC and
>> send; assuming a correct ~/.gitconfig. And maybe this script could
>> provide a simple hint for configuring git-send-email.
>>
>> Even, we could imagine that this tiny script would hint the user to run
>> “guix lint” or “guix style” before pressing yes at the send step.
>
> All good ideas, though I think setting up “git send-email” is a pretty
> big problem for many people — myself included! Would be nice if that
> could be simplified, too.
I always use this website to remind myself how to use git send-email:
https://git-send-email.io/
We could out that information in the guix manual or link to it. :)
>
>> From my experience, the most confusing is the “wait from Debbugs ID”
>> part, i.e., check your inbox or spam. And I do not know how it could be
>> simplified.
>
> Yes, on top of that comes the gray-listing, which increases the waiting
> time.
>
> Perhaps… we shouldn’t use Debbugs directly. I have a couple of
> annoyances with Debbugs, including the fact that we cannot configure the
> contents of the emails it sends out. Maybe it is time to implement a
> friendlier email-based frontend…
>
> --
> Ricardo
next prev parent reply other threads:[~2022-06-03 10:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 20:17 proposal: guix-mentors@gnu.org list/alias Ricardo Wurmus
2022-06-01 22:07 ` zimoun
2022-06-01 22:23 ` Gábor Boskovits
2022-06-02 6:17 ` Ricardo Wurmus
2022-06-02 7:44 ` zimoun
2022-06-02 7:54 ` Ricardo Wurmus
2022-06-03 10:53 ` jbranso [this message]
2022-06-09 9:16 ` Paul Jewell
2022-06-02 14:18 ` Ludovic Courtès
2022-06-02 15:36 ` Ricardo Wurmus
2022-06-02 15:12 ` Arun Isaac
2022-06-02 15:27 ` Ricardo Wurmus
2022-06-02 19:31 ` Maxim Cournoyer
2022-06-02 20:29 ` Ricardo Wurmus
2022-06-03 20:04 ` Ludovic Courtès
2022-06-03 21:09 ` Ricardo Wurmus
2022-06-06 15:34 ` Maxim Cournoyer
2022-06-03 10:32 ` Liliana Marie Prikler
2022-06-03 11:13 ` Ricardo Wurmus
2022-06-03 11:21 ` Tobias Geerinckx-Rice
2022-06-03 11:48 ` Liliana Marie Prikler
2022-06-03 11:52 ` Tobias Geerinckx-Rice
2022-06-03 15:55 ` zimoun
2022-06-22 9:22 ` zimoun
2022-06-22 9:44 ` Ricardo Wurmus
2022-06-22 12:29 ` zimoun
2022-06-22 13:26 ` Who’s in for mentoring? Ludovic Courtès
2022-06-22 13:44 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2022-06-22 15:10 ` Thiago Jung Bauermann
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=5d5519fa8b9806020020c9c0de27a855@dismail.de \
--to=jbranso@dismail.de \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=rekado@elephly.net \
--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).