From: Tobias Geerinckx-Rice <me@tobias.gr>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Matt <matt@excalamus.com>,
Vincent Legoll <vincent.legoll@gmail.com>,
guix-devel@gnu.org
Subject: Re: Guix wiki
Date: Tue, 11 Jan 2022 18:27:41 +0100 [thread overview]
Message-ID: <87ee5eqhrc.fsf@nckx> (raw)
In-Reply-To: <86tuea2nxu.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
Hi Simon, all,
I'll give your long and thoughtful reply the attention it deserves
when I have time, but there's another misleading tangent that has
bothered me (elsewhere) in this discussion:
> - cathedral, as it is today
This is revisionist. The Bazaar model perfectly describes Guix,
where everyone is free to submit changes and have them critiqued
and revised in public. Even maintainers are expected to submit.
Changes that meet $criteria are merged into a source tree
immediately available to everyone.
Guix has never used the Cathedral model, where patch submission
and discussion happen behind closed doors, to be released unto the
public as a revelation from on high.
‘People push nontrivial changes without review’ was never a
condition of the Bazaar model or what made it successful. The
book was based on LKML, for heaven's sake! :-)
We can find a cute new name for what's being proposed in this
thread (the Wailing Wall model?), but simply declaring ‘the Bazaar
is called Cathedral now, change my mind’ can't work.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-01-11 17: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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ee5eqhrc.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=matt@excalamus.com \
--cc=vincent.legoll@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.