From: "Ludovic Courtès" <ludo@gnu.org>
To: Blake Shaw <blake@nonconstructivism.com>
Cc: guile-devel@gnu.org, maximedevos@telenet.be, arne_bab@web.de,
Jean Abou Samra <jean@abou-samra.fr>,
Jonas Hahnfeld <hahnjo@hahnjo.de>,
wingo@pobox.com
Subject: Re: Maintenance and future of Guile
Date: Wed, 15 Dec 2021 15:07:04 +0100 [thread overview]
Message-ID: <874k7avu5z.fsf@gnu.org> (raw)
In-Reply-To: <87a6h22dp9.fsf@nonconstructivism.com> (Blake Shaw's message of "Wed, 15 Dec 2021 20:35:30 +0700")
Hi,
Blake Shaw <blake@nonconstructivism.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> If someone is interested, please get in touch with us!
>>
>> While Andy focuses on major improvements to the compiler and VM with a
>> long-term vision, I think it would be great to also have people on the
>> maintainer team focusing on more day-to-day operations: incremental
>> improvements, bug fixes, etc. I think we’re lucky that there’ve been a
>> number of talented contributors chiming in over the last couple of
>> years; let’s take advantage of this, at last!
>>
>
> Just want to chime in as a new Guile to say that while I'm still
> learning, I'm happy to work on any "chores" if there is guidance on how
> to do so. exploring guile has been half the fun so far.
>
> I know CHICKEN has a team of "janitors"; perhaps Guile could benefit
> from adopting a similar approach?
Surely. For my part, while I won’t pretend to do actual work myself, I
can dedicate time to mentor someone willing to step up.
Ludo’.
next prev parent reply other threads:[~2021-12-15 14:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 13:35 Maintenance and future of Guile Blake Shaw
2021-12-15 14:07 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-29 21:05 Blake Shaw
2021-12-29 21:57 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2021-12-20 18:53 Blake Shaw
2021-12-29 16:23 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2021-12-29 19:57 ` Dr. Arne Babenhauserheide
2021-12-19 20:05 Blake Shaw
2021-12-19 20:41 ` Maxime Devos
2021-12-19 21:11 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2021-12-19 21:50 ` Mike Gran
2021-12-20 14:57 ` Tim Van den Langenbergh
2021-12-13 22:18 Maintenance and future of Guile (was: [patch] Add instructions for sending patches) Jean Abou Samra
2021-12-15 10:20 ` Maintenance and future of Guile Ludovic Courtès
2021-12-16 21:15 ` Taylan Kammer
2021-12-17 14:51 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2021-12-17 15:33 ` Artem Chernyak
2021-12-17 15:37 ` Ludovic Courtès
2021-12-17 15:48 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2021-12-18 16:35 ` Taylan Kammer
2021-12-21 14:27 ` Ludovic Courtès
2022-08-19 16:49 ` Aleix Conchillo Flaqué
2022-08-19 18:46 ` zimoun
2022-08-19 19:06 ` 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://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=874k7avu5z.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=arne_bab@web.de \
--cc=blake@nonconstructivism.com \
--cc=guile-devel@gnu.org \
--cc=hahnjo@hahnjo.de \
--cc=jean@abou-samra.fr \
--cc=maximedevos@telenet.be \
--cc=wingo@pobox.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).