From: Giovanni Biscuolo <g@xelera.eu>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: The already complicated (complex?) process for contributing.
Date: Sat, 16 Sep 2023 09:33:22 +0200 [thread overview]
Message-ID: <87pm2i7et9.fsf@xelera.eu> (raw)
In-Reply-To: <87msxn9ykw.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2941 bytes --]
Hi Simon,
since I already replied you offline please forgive me for any
repetitions, but later I realized a better comment to your metaphore
(see below) could be useful to other people.
Simon Tournier <zimon.toutoune@gmail.com> writes:
[...]
> On a side note, documentation is very fine but I do not read (or
> study!?) the documentation of my oven, instead I am just cooking stuff
> for fun.
On a side note, I like your metaphores!
OK but in my view the GNU Guix project is not a personal kitchen but an
international food company [1], with a complex /distributed/ production
process involving tools (ovens, etc.) and recipes (code) ranging from
trivial to very complex; not to forget **legal requirements**, a
challenging supply chain management and a very _peculiar_ process called
"change integration management" from "customers" proposals. Am I
exaggerating?
Now, given the above context is a valid analogy, is it a fair
expectation you can contribute to the company [1] with the food you cook
just for fun with your oven?
The food GNU Guix company [1] supplies is boostrappable and reproducible
binary code, largerly "baked" using third-party recipes, with a
progressively shrinking binary seed: yeah! :-D
Well, to be honest the food analogy does not fit very well: Guix
supplies /peculiar/ tools that users can use for a variety of
activities, ranging from cooking just for fun to complex infrastructures
management... and to effectively use /that/ tools users should better
study its documentation (ungrateful job the documentation writer!) ;-)
[...]
> If a project needs really lengthy documentation for just contributing,
> either it is a more-than-thousand contributors project, as the Linux
> kernel
I disagree this is a valid metric to measure the complexity of the
process called "change integration management", it could even be _one_
customer asking to change the recipe for his preferred cake.
> either something is wrong. Maybe both. ;-)
...or maybe it's not "just" a project but a whole food compay [1].
Oh, oh, oh: wait! Are we going into /that/ famous essay [2] and its
sequel [3] ?!? (very interesting readings!)
...OK, I surrender, unconditionally! :-D
Happy cooking! :-) Gio'
[1] with a very peculiar vision, mission and business model; but please
concede the analogy
[2] "On Management and the Maginot Line"
http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s12.html
[3] "Project Structures and Ownership"
http://catb.org/~esr/writings/homesteading/homesteading/ar01s16.html
P.S.: on a side note, I think that part (all?) of the problems discussed
in [2] and [3] are rooted in the anthropological set of questions known
as «Phenomenon of Bullshit Jobs»
https://davidgraeber.org/articles/on-the-phenomenon-of-bullshit-jobs-a-work-rant/
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2023-09-16 7:34 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 8:28 [workflow] Automatically close bug report when a patch is committed Giovanni Biscuolo
2023-09-06 9:45 ` Christopher Baines
2023-09-07 9:38 ` [workflow] Triaging issues (was Automatically close bug report when a patch is committed) Giovanni Biscuolo
2023-09-07 15:41 ` Vagrant Cascadian
2023-09-11 7:37 ` Giovanni Biscuolo
2023-09-11 15:29 ` Simon Tournier
2023-09-11 17:08 ` Giovanni Biscuolo
2023-09-06 16:14 ` [workflow] Automatically close bug report when a patch is committed Maxim Cournoyer
2023-09-07 0:23 ` Simon Tournier
2023-09-07 2:01 ` Maxim Cournoyer
2023-09-07 9:58 ` Simon Tournier
2023-09-09 23:43 ` Maxim Cournoyer
2023-09-07 13:11 ` Giovanni Biscuolo
2023-09-09 23:39 ` Maxim Cournoyer
2023-09-11 7:53 ` Giovanni Biscuolo
2023-09-11 14:01 ` Maxim Cournoyer
2023-09-11 17:10 ` Giovanni Biscuolo
2023-09-07 11:08 ` Giovanni Biscuolo
2023-09-07 11:58 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-09-07 13:09 ` Maxim Cournoyer
2023-09-07 15:52 ` Vagrant Cascadian
2023-09-09 23:50 ` Maxim Cournoyer
2023-09-11 11:00 ` Simon Tournier
2023-09-11 13:46 ` Maxim Cournoyer
2023-09-11 14:11 ` Simon Tournier
2023-09-11 15:33 ` Maxim Cournoyer
2023-09-13 2:46 ` Vagrant Cascadian
2023-09-13 15:49 ` Maxim Cournoyer
2023-09-14 16:30 ` Vagrant Cascadian
2023-09-14 18:02 ` Maxim Cournoyer
2023-09-07 13:19 ` Giovanni Biscuolo
2023-09-07 10:40 ` Giovanni Biscuolo
2023-09-07 13:49 ` Giovanni Biscuolo
2023-09-27 14:36 ` Christopher Baines
2023-09-07 16:12 ` Vagrant Cascadian
2023-09-07 16:28 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-09-09 23:59 ` Liliana Marie Prikler
2023-09-11 8:09 ` Giovanni Biscuolo
2023-09-11 13:59 ` Maxim Cournoyer
2023-09-11 17:55 ` Liliana Marie Prikler
2023-09-11 18:36 ` Maxim Cournoyer
2023-09-11 18:51 ` Liliana Marie Prikler
2023-09-11 20:41 ` Maxim Cournoyer
2023-09-12 13:55 ` Giovanni Biscuolo
2023-09-13 15:19 ` Maxim Cournoyer
2023-09-14 9:42 ` Giovanni Biscuolo
2023-09-14 16:58 ` Liliana Marie Prikler
2023-09-12 17:03 ` Liliana Marie Prikler
2023-09-13 9:37 ` Giovanni Biscuolo
2023-09-13 15:27 ` Maxim Cournoyer
2023-09-13 19:14 ` Liliana Marie Prikler
2023-09-13 22:12 ` Simon Tournier
2023-09-14 3:00 ` Maxim Cournoyer
2023-09-14 10:48 ` Giovanni Biscuolo
2023-09-15 21:46 ` Vagrant Cascadian
2023-09-19 16:41 ` Giovanni Biscuolo
2023-09-14 10:27 ` Giovanni Biscuolo
2023-09-14 12:25 ` Simon Tournier
2023-09-15 7:16 ` Giovanni Biscuolo
2023-09-15 9:03 ` Simon Tournier
2023-09-15 14:37 ` The already complicated (complex?) process for contributing Giovanni Biscuolo
2023-09-15 16:43 ` Simon Tournier
2023-09-16 7:33 ` Giovanni Biscuolo [this message]
2023-09-16 8:33 ` Simon Tournier
2023-09-14 7:20 ` [workflow] Automatically close bug report when a patch is committed Andreas Enge
2023-09-14 10:25 ` Giovanni Biscuolo
2023-09-14 22:51 ` Vagrant Cascadian
2023-09-15 4:23 ` Liliana Marie Prikler
2023-09-15 21:30 ` Vagrant Cascadian
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=87pm2i7et9.fsf@xelera.eu \
--to=g@xelera.eu \
--cc=guix-devel@gnu.org \
--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.