unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org,  GNU Guix maintainers <guix-maintainers@gnu.org>
Subject: Re: proposal: guix-mentors@gnu.org list/alias
Date: Thu, 02 Jun 2022 15:31:24 -0400	[thread overview]
Message-ID: <87a6auvp4j.fsf@gmail.com> (raw)
In-Reply-To: <875ylkyvrh.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 01 Jun 2022 22:17:07 +0200")

Hi Ricardo,

Ricardo Wurmus <rekado@elephly.net> writes:

> Hi,
>
> to help new contributors get their first contribution into Guix I think
> it would be good to do this:
>
> 1. create a new private mailing list or mailing alias guix-mentors@gnu.org
>
> 2. ask for experienced Guix contributors who are committed to helping
> new contributors to subscribe to the list
>
> 3. update the Contributing section in the manual (and the website) to
> suggest Cc-ing guix-mentors@gnu.org for a first contribution.
>
> 4. have subscribers to guix-mentors@gnu.org “claim” a contribution
> within 48 hours, to avoid dilution of responsibilit.  Every contribution
> must be acknowledged.
>
> Mentors would then not merely review the submission but shepherd it,
> making necessary modifications and push the adjusted patches as soon as
> possible.  The goal is not to do the usual review but to create
> quick successes, a great first impression.
>
> I recently contributed my first R package to CRAN, and I received an
> automatic response that a human reviewer would get back to me within x
> days.  This was a great experience, because I didn’t feel like I dropped
> off a package into the void.  Expectations were managed and a process
> outlined that set the course for the whole interaction.
>
> Our track record with regard to review is not great, and that harm first
> contributors more than anyone else.  Having dedicated mentors who agree
> to responding and claiming a contribution within 48 hours addresses this
> problem.
>
> I cannot commit to reviewing enough patches that come in on
> guix-patches, but I sure can promise to join the guix-mentors list and
> take on and shepherd first contributions.

Great initiative!  The merit of it compared to doing the same on
guix-patches seem to be to more easily notice about new contributions,
and have them in smaller volumes so to offer prompter feedback.

We'd have to define what are 'new contributors' clearly so that it
doesn't get flooded/abused though, since the "review" happens behind
closed doors (in private).

Thanks,

Maxim


  parent reply	other threads:[~2022-06-02 19:31 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 [this message]
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=87a6auvp4j.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --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).