From: Arun Isaac <arunisaac@systemreboot.net>
To: Paul Jewell <paul@teulu.org>
Cc: zimoun <zimon.toutoune@gmail.com>,
"Giovanni Biscuolo" <g@xelera.eu>,
"Ludovic Courtès" <ludo@gnu.org>,
"Guix Devel" <guix-devel@gnu.org>,
"GNU Guix maintainers" <guix-maintainers@gnu.org>
Subject: Re: On commit access, patch review, and remaining healthy
Date: Mon, 20 Jun 2022 17:41:12 +0530 [thread overview]
Message-ID: <878rprr0v3.fsf@systemreboot.net> (raw)
In-Reply-To: <E18B6594-BAF2-48DF-86D1-D29ABF3D1CA8@teulu.org>
>> Also, should we remove old/broken/unused/rarely-used packages from Guix?
>> In the past, I have packaged and contributed very niche packages which
>> probably no one else uses, and sometimes even I don't use anymore. But,
>> these packages continue to stay in Guix and add to the maintenance
>> burden. Should we have some policy to phase out such packages,
>> especially if such packages break often? I mean, that there is no need
>> to phase out an elisp package that builds trivially all the time, but
>> what about more complex packages that take many many hours to maintain?
>
> I think they should be removed. This could link to the maintainer
> comment above. If a package is identified as old or broken, then users
> could be notified, and after a “cooling off” period they are
> removed. This could allow for discussion about whether removal is
> appropriate, or whether someone else would step up and update the
> package. Under Gentoo (the distro I know well, having used it since
> 2004), obsolete and problematic packages are hard masked, and users
> notified why, and when removal from the repository will occur. The
> hard masking prevents new installations (almost - you can make some
> additional configuration changes to enable installation). Users then
> have a choice - support the resolution of the issues leading to hard
> masking, or move the package definition to a personal repository so it
> can continue to be used (at their own risk). Regarding rarely used
> packages - I wouldn’t remove these if there is a maintainer for them
> and they are still being kept up to date. If this no longer happens,
> then they are in the old/broken category.
I like this idea. We already have a way to mark packages as
deprecated. The Gentoo method seems like a way to mark packages that are
"about to be deprecated". I like the way it notifies the user of the
impending deprecation without the user having to subscribe to the
mailing list or the issue tracker.
> I guess the big question for me is “could this be automated in some
> way?”
Indeed, it's all a matter of somebody implementing the tooling! ;-) Like
Ludo mentioned, Cuirass and the Guix data service may be involved in
determining which packages are frequently broken.
>> I don't have strong opinions on these questions. I would love to hear
>> what others think.
>>
>
> I hope my comments are useful!
Definitely, thanks!
next prev parent reply other threads:[~2022-06-20 12:53 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 15:10 On commit access, patch review, and remaining healthy Ludovic Courtès
2022-06-02 20:22 ` Brian Cully via Development of GNU Guix and the GNU System distribution.
2022-06-03 19:37 ` Ludovic Courtès
2022-06-03 21:17 ` Ricardo Wurmus
2022-06-07 7:08 ` Efraim Flashner
2022-06-07 15:11 ` Ludovic Courtès
2022-06-08 11:39 ` Efraim Flashner
2022-06-08 21:10 ` Ludovic Courtès
2022-06-20 12:53 ` Hartmut Goebel
2022-06-21 15:44 ` zimoun
2022-06-22 9:19 ` Munyoki Kilyungi
2022-06-02 20:32 ` Pier-Hugues Pellerin
2022-06-03 19:42 ` Ludovic Courtès
2022-06-02 21:35 ` Luis Felipe
2022-06-03 8:22 ` Feed on specific topic (public-inbox?) zimoun
2022-06-03 10:51 ` zimoun
2022-06-06 12:11 ` On commit access, patch review, and remaining healthy Arun Isaac
2022-06-06 21:43 ` Ludovic Courtès
2022-06-07 6:44 ` zimoun
2022-06-08 9:30 ` Giovanni Biscuolo
2022-06-14 12:24 ` zimoun
2022-06-15 7:01 ` Arun Isaac
2022-06-15 9:19 ` Ludovic Courtès
2022-06-19 6:55 ` Paul Jewell
2022-06-20 12:11 ` Arun Isaac [this message]
2022-06-15 15:11 ` Giovanni Biscuolo
2022-06-08 10:54 ` Giovanni Biscuolo
2022-06-09 19:55 ` Arun Isaac
2022-06-08 9:49 ` Giovanni Biscuolo
2022-06-09 19:50 ` Arun Isaac
2022-06-10 12:27 ` Giovanni Biscuolo
2022-06-10 15:03 ` Efraim Flashner
2022-06-10 16:10 ` Giovanni Biscuolo
2022-06-10 16:26 ` Giovanni Biscuolo
2022-06-10 15:03 ` Maxime Devos
2022-06-11 4:13 ` Thiago Jung Bauermann
2022-06-11 9:37 ` Ludovic Courtès
2022-06-14 11:54 ` zimoun
2022-06-14 15:54 ` Maxim Cournoyer
2022-06-15 6:46 ` Arun Isaac
2022-06-13 12:19 ` Arun Isaac
[not found] <mailman.12124.1654864076.1231.guix-devel@gnu.org>
2022-06-12 8:18 ` Ricardo Wurmus
2022-06-12 9:42 ` Giovanni Biscuolo
2022-06-12 13:10 ` Maxime Devos
2022-06-13 9:34 ` Giovanni Biscuolo
2022-06-13 10:48 ` Maxime Devos
2022-06-13 14:21 ` Giovanni Biscuolo
2022-06-12 8:21 ` Ricardo Wurmus
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=878rprr0v3.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=g@xelera.eu \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=ludo@gnu.org \
--cc=paul@teulu.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 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).