From: Thomas Danckaert <post@thomasdanckaert.be>
To: pjotr.public12@thebird.nl
Cc: guix-devel@gnu.org
Subject: Re: gnu-patches back log
Date: Wed, 01 Mar 2017 13:48:55 +0100 (CET) [thread overview]
Message-ID: <20170301.134855.1978548551800956096.post@thomasdanckaert.be> (raw)
In-Reply-To: <20170301111715.GA11182@mail.thebird.nl>
From: Pjotr Prins <pjotr.public12@thebird.nl>
Subject: Re: gnu-patches back log
Date: Wed, 1 Mar 2017 11:17:15 +0000
> This is the first thing I am trying :). The main difference with the
> existing approach is that I want to have more engagement from fresh
> contributors who can also peer review. Review is an excellent way of
> learning. How exactly we are going to do this is not clear yet. But
> that is what I am thinking.
Speaking for myself as a new/beginning contributor: there is a finite
amount of time I can (want to) spend on Guix, and a large number of
things I want to fix/improve/experiment for myself. I now try to
review some patches occasionally, but of course that takes away from
the time I have to work on the issues I care most about myself. (And
for other contributors: time that cannot be spent on the many other
important things that need to be done.)
I understand that in the long term, time spent supporting new
contributors (i.e. helping the community grow) will probably benefit
Guix (and therefore also me) more than trying to do everything
myself, but it takes some effort to adopt this mindset.
> Meanwhile I want to know what limits people actually have. I think 2
> weeks is not acceptable (but that should be obvious).
Of course this is personal, but for me it is acceptable. I assume
that, when a patch is good, it will eventually make it in, and accept
that, sometimes, I have to be patient (of course faster is always
better). I see a lot of dedication and effort from everybody here,
and accept that a patch I submit might not be on the top of anyone's
priority list.
So, I hear your call to slightly reconsider priorities for my
Guix-time, and try to spend more time mentoring (and will try to do
that, as far as I can :) ), but also think contributors should assume
everybody here is doing their best, and have some patience.
Thomas
next prev parent reply other threads:[~2017-03-01 12:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 14:21 How to M-x debbugs-gnu with new guix-patches Christopher Allan Webber
2017-02-22 17:26 ` Catonano
2017-02-26 11:10 ` Pjotr Prins
2017-02-26 19:02 ` Christopher Allan Webber
2017-02-28 6:25 ` gnu-patches back log Pjotr Prins
2017-02-28 11:14 ` Hartmut Goebel
2017-03-01 5:23 ` Pjotr Prins
2017-03-01 6:16 ` Leo Famulari
2017-03-01 8:17 ` Pjotr Prins
2017-03-01 10:42 ` Andy Wingo
2017-03-01 11:17 ` Pjotr Prins
2017-03-01 12:48 ` Thomas Danckaert [this message]
2017-03-01 15:06 ` Pjotr Prins
2017-03-01 13:14 ` Leo Famulari
2017-03-01 14:45 ` Pjotr Prins
2017-03-01 15:51 ` Leo Famulari
2017-03-01 16:07 ` Pjotr Prins
2017-03-01 23:08 ` Catonano
2017-03-07 12:09 ` Ricardo Wurmus
2017-03-13 17:37 ` Catonano
2017-03-01 14:16 ` ng0
2017-03-01 13:14 ` John Darrington
2017-03-06 16:14 ` Ludovic Courtès
2017-03-07 11:44 ` Hartmut Goebel
2017-03-11 21:30 ` Ludovic Courtès
2017-03-25 12:37 ` How to M-x debbugs-gnu with new guix-patches Catonano
2017-03-25 21:45 ` Ludovic Courtès
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=20170301.134855.1978548551800956096.post@thomasdanckaert.be \
--to=post@thomasdanckaert.be \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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).