unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Kjartan Óli Águstsson" <kjartanoli@outlook.com>
To: Tao Hansen <worldofgeese@riseup.net>
Cc: Wilko Meyer <w@wmeyer.eu>, guix-devel@gnu.org
Subject: Re: Guix Survey (follow up on "How can we decrease the cognitive overhead for contributors?")
Date: Wed, 11 Oct 2023 06:53:05 +0000	[thread overview]
Message-ID: <GV1P193MB23104B0C058B8222D62FC09FDFCCA@GV1P193MB2310.EURP193.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <875y3h1fnm.fsf@riseup.net>

[-- Attachment #1: Type: text/plain, Size: 3063 bytes --]


Tao Hansen <worldofgeese@riseup.net> writes:

> Hello, I hope it's ok I'm replying to this email as a follow-up to
> decreasing the cognitive overhead for new users. I'm also brand new to
> the Guix community and ecosystem. I wanted to share a perspective from a
> user on a Lemmy instance who wrote why the Guix ecosystem was not
> friendly enough to meet them where they were, a person in their early
> twenties. I'd like to suggest approach their criticism with compassion
> and open-mindedness.

As a person in my early twenties, who has contributed a few (small)
patches to Guix and Emacs, I want to offer another datapoint/perspective
on this issue.

> @velox_vulnus writes at https://lemmy.ml/comment/4625080
>
>> I don’t like the vibe of ageism against young people that is
>> associated with GNU.

I'll be honest, I don't understand this point.  I've never felt any vibe
of ageism from any interaction with the GNU project.  Is this just about
using mailing lists instead of some forge and other similar complaints
of 'outdated' systems/processes?

>> What is also frustrating is their reluctance to improve their
>> infrastructure.

Purely personal anecdote here, but I've never seen a reluctance to
improve infrastructure.  I've seen a reluctance to make changes which
could negatively affect existing workflows, but I wouldn't characterise
that as refusal to improve.

>> They could choose to remove non-Libre JS from GitLab, Sourcehut or
>> Gitea, or at least come with a new source hosting platform, but they
>> choose not to. 
>
> I also have a hard time with the insistence on the "Old Ways" as somehow
> more pure, more legitimate than the new. There's some sense of the
> expression, "You kids get off my lawn!"

Having made contributions to projects using both methods.  I massively
prefer the mailing list + patch workflow of GNU to GitHub's Pull Request
model.

> And the decentralized nature of sending Git patches by email, which I
> still have not ventured to try, makes it hard to *discover* Guix
> development in a single place. A user needs to go to any one of the
> mailing lists, pull the Git repo or browse Savannah or the issue
> frontend for bugs and new features they might be interested in, and
> generally have an idea of what they want to be looking for to find
> it. Discovery by serendipity is missing.

Where does 'Discovery by serendipity occur on GitHub or the other
forges?  Personally I've never experienced more such discoveries than by
reading threads on the development mailing list of a project.

> We have the FOSS technology to tackle a lot of these critiques and bring
> in a whole new wave of contributors. We have fully open Git forges and
> modern messaging protocols to make a brand new developer-friendly Guix a
> reality.

How friendly are these Git forges and messaging protocols to the
continued use of existing email based workflows?

-- 
Kjartan Oli Agustsson
GPG Key fingerprint: 4801 0D71 49C0 1DD6 E5FD  6AC9 D757 2FE3 605E E6B0

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 691 bytes --]

      parent reply	other threads:[~2023-10-15 11:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-16 12:59 Guix Survey (follow up on "How can we decrease the cognitive overhead for contributors?") Wilko Meyer
2023-09-17 17:55 ` MSavoritias
2023-09-18 12:02 ` Peter Pronai
2023-09-20  9:37 ` Simon Tournier
2023-09-20 21:51   ` Wilko Meyer
2023-09-21 17:23     ` Katherine Cox-Buday
2023-10-02 11:24       ` Wilko Meyer
2023-10-09 18:29         ` Katherine Cox-Buday
2023-10-12 14:43           ` Simon Tournier
2023-11-06 22:46           ` Wilko Meyer
2023-10-08 12:07 ` Tao Hansen
2023-10-09 13:47   ` Lucy Coleclough
2023-10-11  6:53   ` Kjartan Óli Águstsson [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=GV1P193MB23104B0C058B8222D62FC09FDFCCA@GV1P193MB2310.EURP193.PROD.OUTLOOK.COM \
    --to=kjartanoli@outlook.com \
    --cc=guix-devel@gnu.org \
    --cc=w@wmeyer.eu \
    --cc=worldofgeese@riseup.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).