unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Jookia <166291@gmail.com>
Cc: help-guix@gnu.org, t3sserakt <t3sserakt@posteo.de>
Subject: Re: GuixSD on arm
Date: Tue, 05 Jul 2016 22:46:08 +0200	[thread overview]
Message-ID: <87poqrlsof.fsf@elephly.net> (raw)
In-Reply-To: <20160704221828.GA15580@novena-choice-citizen.lan>


Jookia <166291@gmail.com> writes:

> - Patches would get lost regularly.

Yeah, this is still a problem for me.  Many patches slip by because I
have no capacity to review them in time.  I have settled on reviewing
things that I feel I’m a little more qualified to review than others,
such as R packages, scientific software, audio software.  But it’s
really tough to review things *well* and in time.

In my opinion, patchwork hasn’t improved this, unfortunately, because
patch management requires too much effort (patches aren’t reliably
marked as merged, no email control, etc).

> I'm not cut out to what feels like nagging people when I don't know the reasons
> why they haven't replied. Perhaps this is how things work in other systems, but
> as someone that suffers from social anxiety and finds it hard enough to even
> send patches I can't deal with this, and Guix seems to be doing fine without me.

I’m sad to hear that this makes it hard for you to continue to
contribute to Guix.

In my case a lack of a response is usually just a result of having too
many other things to work on.  Sometimes it’s because I really don’t
feel qualified to answer (as in the case of LUKS+Libreboot because at
that time I didn’t have any experience with Libreboot).

> As patches were lost and most discussion was done on the mail list, there was
> basically no discussion on patches or design problems. After getting Guix to
> boot on my Libreboot machine I went to work on fixing issues with the boot
> system, such as adding support for legacy Libreboot systems and encrypted
> bootloaders. This was lost.
>
> I also did some work to get LVM+LUKS working on Guix and tried to spark a
> discussion in to fixing the design issues in system configuration. I think there
> was about one reply, and it was lost.

Now that my laptop is running Libreboot I’m actually looking at the
discussions you started to see how we can move forward there.  Thank you
for your experimentation and documenting your work on the mailing list!
I can assure you that it’s not lost (just not used in the moment).

> This experience has put me off of Guix, GNU and free software development. I
> don't blame any one, but more a system that doesn't incorporate people like me.

That’s sad and I hope you will be able to reconsider some time in the
future as the project matures.

~~ Ricardo

      parent reply	other threads:[~2016-07-05 20:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04 14:02 GuixSD on arm t3sserakt
2016-07-04 15:33 ` Ludovic Courtès
2016-07-04 16:13   ` t3sserakt
2016-07-04 17:14     ` ng0
2016-07-04 22:18       ` Jookia
2016-07-05  8:21         ` Alex Sassmannshausen
2016-07-05  8:23         ` Ludovic Courtès
2016-07-05 15:44           ` Jookia
2016-07-11 11:47             ` Ludovic Courtès
2016-07-05  8:53         ` t3sserakt
2016-07-05 21:49           ` Jookia
2016-07-11 11:49             ` Ludovic Courtès
2016-07-05 12:08         ` ng0
2016-07-05 20:46         ` Ricardo Wurmus [this message]

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=87poqrlsof.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=166291@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=t3sserakt@posteo.de \
    /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.
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).