From: Attila Lendvai <attila@lendvai.name>
To: "Sergio Pastor Pérez" <sergio.pastorperez@outlook.es>
Cc: Ian Eure <ian@retrospec.tv>, guix-devel <guix-devel@gnu.org>
Subject: Re: Request for assistance maintaining LibreWolf
Date: Sun, 18 Aug 2024 08:37:34 +0000 [thread overview]
Message-ID: <GM9ZYT1WtT4ecO6LmecjhDXtpFgzz9AjfOlPPYcLtEhqL_7uWw-j099ishR8jCT9PPTcswuduZognk3XvRQnBzEsk7StZGFRRJJZ1WANUqQ=@lendvai.name> (raw)
In-Reply-To: <PAXP251MB0348FCF488DA71284D05F70FF3822@PAXP251MB0348.EURP251.PROD.OUTLOOK.COM>
> We should try to come up with a solution that alleviates the burden on
> the maintainers. Given how often this issue arises, what if we try, as
> a collective, to suggest new mechanisms that would improve the
> situation?
IMO one thing that would help is to somehow losen the current very tight coupling (the guix monorepo).
a high level of centralization always translates to a bottleneck, and guix has reached a point where its centralized structure is seriously hindering it and frustrating away contributors.
i.e. it's much less risk to delegate the management of a hypothethical python channel to someone trusted than to give commit access to every contributor who wants to help maintaining the python related packages.
so, i think a lot of packages should be in channels. probably everything that is not essential for a minimally functional system that can bootstrap itself. part of python could be in the main guix repo, but whatever is not tightly needed could go into a channel with its own access control management.
some channels would have loser standards (god forbid some wouldn't frustrate the contributors with the ChangeLog format in the commit messages), and the users could decide whom they trust with what. and the guix maintainers could decide which channels to list on the official web page, with what comments/warnings.
but this is easier said than done, because formally expressing the dependencies between these channels is not a trivial task (think of e.g. keeping `guix time-machine` working in an environment where a patch in the official guix repo can break a package in some random channel, which is then fixed there in a new commit, etc). and even if doable, it would probably introduce extra code complexity.
but i'm sure there were countless discussions about the pros and cons of the monorepo, and i wish such a topic was captured in a wiki where the main arguments, obstacles, and ideas were collected for people like me who are late to the party.
but then guix doesn't really have an official wiki either. (and no, an afterthought in the libreplanet wiki doesn't count. and if you have an urge to argue, then just look at its current contents...) so we're pretty much stuck with the flat mailing list archive and IRC logs.
hrm, a tangential: maybe digesting the guix mailing list and IRC archive will be my first actual use-case for an LLM... modern problems require modern solutions.
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“Millions of people never analyze themselves. Mentally they are mechanical products of the factory of their environment, preoccupied with breakfast, lunch, and dinner, working and sleeping, and going here and there to be entertained. They don't know what or why they are seeking, nor why they never realize complete happiness and lasting satisfaction. By evading self-analysis, people go on being robots, conditioned by their environment. True self-analysis is the greatest art of progress.”
— Paramahansa Yogananda (1893–1952)
next prev parent reply other threads:[~2024-08-18 8:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 16:44 Request for assistance maintaining LibreWolf Ian Eure
2024-08-17 18:00 ` Sergio Pastor Pérez
2024-08-17 19:43 ` Ian Eure
2024-08-18 8:35 ` Christopher Baines
2024-08-18 16:50 ` Ian Eure
2024-08-19 1:53 ` Suhail Singh
2024-08-19 8:53 ` Christopher Baines
2024-08-19 23:14 ` Ian Eure
2024-09-12 1:01 ` Maxim Cournoyer
2024-08-19 17:01 ` Sergio Pastor Pérez
2024-08-18 8:37 ` Attila Lendvai [this message]
2024-08-18 9:07 ` Lars-Dominik Braun
2024-08-17 20:36 ` Ian Eure
2024-08-17 23:08 ` Suhail Singh
2024-08-18 4:07 ` Ian Eure
2024-08-18 21:17 ` Tomas Volf
2024-08-21 20:54 ` Ludovic Courtès
2024-08-22 15:00 ` Ian Eure
2024-08-28 20:48 ` Ludovic Courtès
2024-08-28 23:15 ` Ian Eure
2024-08-29 7:30 ` Tobias Geerinckx-Rice
2024-08-29 20:24 ` [Browser-Team] " André Batista
2024-08-30 20:14 ` Ludovic Courtès
2024-08-22 16:37 ` André Batista
2024-08-28 20:46 ` Ludovic Courtès
2024-08-30 20:18 ` Defining the role of teams Ludovic Courtès
2024-08-28 23:16 ` Request for assistance maintaining LibreWolf Ian Eure
[not found] <mailman.5970.1723926982.21382.guix-devel@gnu.org>
2024-08-18 0:11 ` Andy Tai
2024-08-18 0:48 ` Ian Eure
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='GM9ZYT1WtT4ecO6LmecjhDXtpFgzz9AjfOlPPYcLtEhqL_7uWw-j099ishR8jCT9PPTcswuduZognk3XvRQnBzEsk7StZGFRRJJZ1WANUqQ=@lendvai.name' \
--to=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=ian@retrospec.tv \
--cc=sergio.pastorperez@outlook.es \
/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.