unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "André A. Gomes" <andremegafone@gmail.com>
To: Attila Lendvai <attila@lendvai.name>
Cc: guix-devel@gnu.org
Subject: Re: Guix wiki
Date: Wed, 12 Jan 2022 15:00:43 +0300	[thread overview]
Message-ID: <8735lt5fkk.fsf@gmail.com> (raw)
In-Reply-To: <J7RU1Pu76SbtZFLOsPjKT9aWOS10GIbtZ4a-Vd-iPXogAuyjQAoEeXcuHLYZxzzIjPrPR5yz-oavUWhslFLDWkhSh5rOCi2eaVoyV0l0PK4=@lendvai.name> (Attila Lendvai's message of "Wed, 12 Jan 2022 11:19:31 +0000")

Attila Lendvai <attila@lendvai.name> writes:

> this sounds nice, but the reality is that nowadays reviewing and
> pushing commits can take weeks or even months without much feedback. i
> even have a fix for git-authenticate, coupled with tests that
> demonstrate a hole, and it's been open for months. i assume because of
> the lack of bandwidth from people who are in position to review and/or
> push it, but whatever the reason is, this is the case.
>
> the vision you are painting here is inspiring, but i think the Guix
> community is reaching a size where such an organizational structure is
> not facilitating the cooperation well enough. more and more random
> people will show up, with contributions of varying levels of
> quality. if it all goes through the current choke-points of the core
> (people, guix-devel, etc), then they will get overwhelmed, or at least
> will limit what could otherwise be achieved with more appropriate
> tools/processes.

You might have a point here, but I get the feeling that things are
slowly changing to address it.  Also, it's important to keep in mind
that the sporadic contributor will always be more scrutinised.

> random example: the readability of plain-text emails pouring into
> guix-patches, compared to e.g. threaded, formatted, and
> displayed-in-context comment threads in a tool like gitlab.

I don't see how gitlab would help.  Gnus, for instance, provides the
formatting you mention.


-- 
André A. Gomes
"Free Thought, Free World"


  parent reply	other threads:[~2022-01-12 13:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 21:14 Guix wiki Matt
2022-01-09 21:32 ` Vagrant Cascadian
2022-01-11 13:02   ` Matt
2022-01-11 18:29   ` Jonathan McHugh
2022-04-13 14:46   ` Aurora
2022-01-09 23:55 ` Vincent Legoll
2022-01-11 13:31   ` Matt
2022-01-11 15:17     ` Ricardo Wurmus
2022-01-12  2:52       ` Matt
2022-01-11 15:30     ` Tobias Geerinckx-Rice
2022-01-11 17:15       ` zimoun
2022-01-11 17:27         ` Tobias Geerinckx-Rice
2022-01-11 18:21           ` André A. Gomes
2022-01-11 18:50           ` zimoun
2022-01-12  2:06             ` Tobias Geerinckx-Rice
2022-01-12  8:55               ` zimoun
2022-01-12  9:22                 ` André A. Gomes
2022-01-12  3:51       ` Matt
2022-01-12 15:26         ` Luis Felipe
2022-01-11 16:48     ` Luis Felipe
2022-01-11 21:03     ` Attila Lendvai
2022-01-11 23:18       ` Ricardo Wurmus
2022-01-12  3:28         ` Matt
2022-01-18 14:34           ` Ludovic Courtès
2022-04-11  6:49             ` Attila Lendvai
2022-04-11  8:42               ` Maxime Devos
2022-04-13 15:01                 ` Attila Lendvai
2022-04-11  8:47               ` Maxime Devos
2022-01-12 11:19         ` Attila Lendvai
2022-01-12 11:52           ` Ricardo Wurmus
2022-01-12 12:00           ` André A. Gomes [this message]
2022-01-10  8:29 ` Josua Stingelin
2022-01-12  1:57   ` Matt
2022-01-12  9:19     ` Ricardo Wurmus
2024-01-10  9:55 ` Attila Lendvai
2024-01-17 19:17   ` Maxim Cournoyer

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=8735lt5fkk.fsf@gmail.com \
    --to=andremegafone@gmail.com \
    --cc=attila@lendvai.name \
    --cc=guix-devel@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).