unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>, "Leo Le Bouter" <lle-bout@zaclys.net>
Cc: guix-devel@gnu.org
Subject: Re: Leaving the GNU Guix community
Date: Fri, 30 Apr 2021 19:54:56 +0200	[thread overview]
Message-ID: <878s4zirnz.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87h7jof2o7.fsf@gnu.org>

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

Hi,

Ludovic Courtès <ludo@gnu.org> writes:

> You write that “the difference between the beginner and the experienced
> is a construction”.  I sympathize with your rejection of the
> student-professor domination.  However, I think newcomers can and should
> benefit from guidance by the experienced; that’s the only way we can
> truly blur the experienced/beginner distinction.  As an “experienced”
> person in this project, I consider it part of my work to help others.  I
> believe knowledge sharing can be achieved without it becoming a
> domination relation.  That is at least what I think most people here
> strive for.

I have been wanting to raise this issue for a while, so maybe now is the
right time! :)

On the educational level, I fully agree with Ludo.

I wonder, however, if this educational hierarchy does not transpire into
political hierarchies.

In other words, if we certainly need experienced users to teach and help
newcomers, do we need experienced users to take more executive decisions
than newcomers?

At the moment, it seems that the right to police others is reserved to a
privileged group.  Should it really be this way?  It does not seem
obvious to me that this separation benefits the community, maybe there
would be an interesting discussion to have here.

For instance, if a long-term, experienced contributor misbehaves (be it
with commits or communication), can they be policed?  The same way that
less experienced users are policed?  By whom?
Can a less experienced user police an experienced one?

There is a lot to discuss here, including transparency of communication,
class of privileges, protocols for exclusion, etc.

I don't know if these issues have been raised and addressed in the Guix
community; maybe there is room for improvement.  Anyhow, discussing more
about these things can only help organizing ourselves better and
building a stronger community! :)

Cheers!

-- 
Pierre Neidhardt
https://ambrevar.xyz/

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

  reply	other threads:[~2021-04-30 18:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 23:43 Leaving the GNU Guix community Leo Le Bouter
2021-04-30  0:31 ` Ryan Prior
2021-04-30  1:01 ` aviva
2021-04-30 11:03 ` Leo Prikler
2021-04-30 11:10 ` Ludovic Courtès
2021-04-30 17:54   ` Pierre Neidhardt [this message]
2021-05-01  2:34 ` Tobias Geerinckx-Rice
2021-05-01 14:45   ` Joshua Branson
2021-05-01 17:47   ` Léo Le Bouter
2021-05-05 14:27     ` raingloom
2021-05-01  4:51 ` Chris Marusich
2021-05-02  0:15 ` Making technology more inclusive Was: " Denis 'GNUtoo' Carikli
2021-05-05 21:11   ` raingloom

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=878s4zirnz.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=guix-devel@gnu.org \
    --cc=lle-bout@zaclys.net \
    --cc=ludo@gnu.org \
    /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).