unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Jean Abou Samra <jean@abou-samra.fr>
Cc: wingo@pobox.com, arne_bab@web.de,
	Jonas Hahnfeld <hahnjo@hahnjo.de>,
	maximedevos@telenet.be, guile-devel@gnu.org
Subject: Re: Maintenance and future of Guile
Date: Wed, 15 Dec 2021 11:20:55 +0100	[thread overview]
Message-ID: <8735muxj7c.fsf@gnu.org> (raw)
In-Reply-To: <979585e9-c198-69f3-928f-7c00cda5d705@abou-samra.fr> (Jean Abou Samra's message of "Mon, 13 Dec 2021 23:18:44 +0100")

Hello Guilers,

Jean Abou Samra <jean@abou-samra.fr> skribis:

> I see a number of similar cases on the mailing list.
>
> I understand the cost of reviewing and I know that
> nobody is entitled to anything in the free software
> world. However, I would like to voice the concern that
> Guile's maintenance is not scaling, and the project
> cannot attract new contributors if patches do not
> make it to the main branch. If the current maintainers
> need to drop their activity, it would be nice if
> they could share maintainership so that at least
> bug fixes can be applied.

I agree and I apologize for the unpleasant situation: it’s clear that I
haven’t been up to the task for several years already.  I’ll discuss
with Andy how I can formally leave the seat to someone with more energy,
whom I’ll be happy to help learn practices and conventions.

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!

Thanks,
Ludo’.



  parent reply	other threads:[~2021-12-15 10:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 22:18 Maintenance and future of Guile (was: [patch] Add instructions for sending patches) Jean Abou Samra
2021-12-13 22:21 ` Jean Abou Samra
2021-12-14  3:45 ` Dr. Arne Babenhauserheide
2022-02-11  7:33   ` Catonano
2021-12-15 10:20 ` Ludovic Courtès [this message]
2021-12-16 21:15   ` Maintenance and future of Guile 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
  -- strict thread matches above, loose matches on Subject: below --
2021-12-15 13:35 Blake Shaw
2021-12-15 14:07 ` Ludovic Courtès
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-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-29 21:05 Blake Shaw
2021-12-29 21:57 ` Olivier Dion via Developers list for Guile, the GNU extensibility library

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=8735muxj7c.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=arne_bab@web.de \
    --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).