From: Maxime Devos <maximedevos@telenet.be>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>,
jgart <jgart@dismail.de>, Guix Devel <guix-devel@gnu.org>
Subject: Re: Is Guix suitable for large monorepos?
Date: Fri, 22 Jul 2022 11:14:45 +0200 [thread overview]
Message-ID: <d25f610d-b766-9665-ed1f-d8c3424a69bb@telenet.be> (raw)
In-Reply-To: <420e1ce118b5610881e6b86c0c4863b0339ee91d.camel@ist.tugraz.at>
[-- Attachment #1.1.1: Type: text/plain, Size: 817 bytes --]
On 22-07-2022 08:58, Liliana Marie Prikler wrote:
> 15:10 "An engineering organization is not a bottom-up kind of thing"
> (X) Doubt.
> 15:18 "In a well functioning engineering team, priorities and decisions
> and effort allocation flow top-down"
> (X) Doubt.
> 15:24 "Some sort of top-down organization is required"
> (X) Doubt.
It's a bit of a stretch, but in a sense Guix is a bit top down, if you
count Guix itself (and the reviewers, committeres, etc. as a while) as
'top' and individual patch submitters as 'down'. OTOH with Guix doesn't
make decisions on what individual people should work on, only on the
rules that the results should follow and there is no effort allocation,
so possibly this is not the kind of 'top-down' that the video was
referring to.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-07-22 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 4:55 Is Guix suitable for large monorepos? jgart
2022-07-22 6:07 ` Ryan Sundberg
2022-07-22 6:58 ` Liliana Marie Prikler
2022-07-22 9:10 ` Maxime Devos
2022-07-22 9:14 ` Maxime Devos [this message]
2022-07-22 9:26 ` Liliana Marie Prikler
2022-07-22 14:25 ` Katherine Cox-Buday
2022-07-28 21:39 ` Blake Shaw
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=d25f610d-b766-9665-ed1f-d8c3424a69bb@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--cc=liliana.prikler@ist.tugraz.at \
/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).