unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Ricardo Wurmus <rekado@elephly.net>,
	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 13:48:38 +0200	[thread overview]
Message-ID: <a634904e6066a83a4949c8a68a329738701214c9.camel@ist.tugraz.at> (raw)
In-Reply-To: <8735gm7zy7@nckx>

Hi Tobias,

Am Freitag, dem 03.06.2022 um 13:21 +0200 schrieb Tobias Geerinckx-
Rice:
> Hi Lily,
> 
> Liliana Marie Prikler 写道:
> > That is once it's established that a new
> > contribution is actually a contribution, the patch is forwarded
> > separately to guix-mentors (along with reply-to: for the 
> > original bug etc. set up in a way that's useful to mentors),
> > claiming takes place, and so on.
> 
> I have trouble parsing this.
> 
> Can you highlight the difference(s) with the existing Guix lists, 
> if any?
So first things first, this would only apply to guix-patches (I
believe), since that is where "contributions" as in "patches that need
review" are sent to.  My proposal is roughly as follows:
1. When a new contributor sends a mail to guix-patches, the mail gets
added to a manual approval queue. (This currently happens)
2. A human operator manually approves of the patch as in flags it as
"Not spam" (This currently happens)
3. A new issue number is claimed in debbugs, yadda yadda.
4. Since we know (from 1+2), that this is a new contributor, a separate
message is sent to guix-mentors (from debbugs or what have you)
informing mentors about this contribution.

My proposal is to have step 4 implemented in software, sitting in
debbugs, the approval queue software, or possibly both depending on how
much interaction they need, rather than reminding potential newcomers
that guix-mentors exists and that they should CC it to get faster code
review.

Alternatively to the above, which would (in theory) forward the patches
as soon as improved, we could implement this with a separate backend
such as mumi, which would basically check for new patches, check
whether any of those patches come from hitherto unknown sources, and if
so send a mail towards guix-mentors.

Does that help clear things up?

As for guix-mentors vs. other mailing lists, refer to Ricardo's initial
proposal.  Interestingly, zimoun had a similar idea, but phrased it
less wordy.

Cheers


  reply	other threads:[~2022-06-03 11:54 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
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 [this message]
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=a634904e6066a83a4949c8a68a329738701214c9.camel@ist.tugraz.at \
    --to=liliana.prikler@ist.tugraz.at \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=me@tobias.gr \
    --cc=rekado@elephly.net \
    /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).