From: "Ludovic Courtès" <ludo@gnu.org>
To: Mikael Djurfeldt <mikael@djurfeldt.com>
Cc: Maxime Devos <maximedevos@telenet.be>,
Nate Rosenbloom <nate.rosenbloom@gmail.com>,
Tom Whitcomb via General Guile related discussions
<guile-user@gnu.org>
Subject: Re: Where is the list of Guile maintainers?
Date: Thu, 26 Dec 2024 12:05:19 +0100 [thread overview]
Message-ID: <87plleyaa8.fsf@gnu.org> (raw)
In-Reply-To: <CAA2Xvw+6xRpdvNXRZhaRCSy3LSFTQOe2nN48mfPs3uSAxGFSgw@mail.gmail.com> (Mikael Djurfeldt's message of "Fri, 20 Dec 2024 18:22:49 +0100")
Hello,
Mikael Djurfeldt <mikael@djurfeldt.com> skribis:
> On Fri, Dec 20, 2024 at 4:12 PM Maxime Devos via General Guile related
> discussions <guile-user@gnu.org> wrote:
>
>> >According to the manual Ludovic Courtès and Andy Wingo are the current
>> maintainers. Although it hasn’t been updated in 5 years.
>>
>> https://www.gnu.org/software/guile/manual/html_node/A-Scheme-of-Many-Maintainers.html
>> >
>> >But I guess that would be a good place to update if it’s changed.
>>
>> I recall hearing that Ludo’ left (or intended to leave?), so I don’t trust
>> it too much, and both don’t seem active with considering Guile patches.
I did consider stepping down in recognition of my limited availability
and to leave room for others. That hasn’t happened though
(bootstrapping issue!).
To be fair, I’m one of the very few people who reviewed and applied
other people’s patches over the past few years. I do think more people
could look at Debbugs and do that work.
Ludo’.
prev parent reply other threads:[~2024-12-26 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 13:59 Where is the list of Guile maintainers? Maxime Devos via General Guile related discussions
2024-12-20 15:02 ` Nate Rosenbloom
2024-12-20 15:11 ` Maxime Devos via General Guile related discussions
2024-12-20 17:22 ` Mikael Djurfeldt
2024-12-26 11:05 ` Ludovic Courtès [this message]
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87plleyaa8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@gnu.org \
--cc=maximedevos@telenet.be \
--cc=mikael@djurfeldt.com \
--cc=nate.rosenbloom@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.
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).