From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Olivier Dion <olivier.dion@polymtl.ca>,
Jean Abou Samra <jean@abou-samra.fr>,
guile-devel <guile-devel@gnu.org>
Subject: Re: Maintenance and future of Guile
Date: Fri, 19 Aug 2022 09:49:01 -0700 [thread overview]
Message-ID: <CA+XASoVaLNSiXUfS3HAaxZaFrs5mPxkEGtH4dRyEJ88vA6cVWg@mail.gmail.com> (raw)
In-Reply-To: <87czlq6njt.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1759 bytes --]
I'm not sure how all this ended up.
But, I would encourage and love for Maxime Devos to be a Guile maintainer.
Always great feedback in Guile and other projects (like Fibers) and I
really feel Guile would benefit a lot from their contributions.
Just a thought.
Aleix
On Tue, Dec 21, 2021 at 6:27 AM Ludovic Courtès <ludo@gnu.org> wrote:
> Hi,
>
> Olivier Dion <olivier.dion@polymtl.ca> skribis:
>
> > On Fri, 17 Dec 2021, Ludovic Courtès <ludo@gnu.org> wrote:
> >> Hi,
> >>
> >> Olivier Dion <olivier.dion@polymtl.ca> skribis:
> >>
> >>> I would also like to contribute in some meaningful way. In what way
> >>> someone with none wizard knowledge of Scheme can contribute the most
> to the
> >>> project?
> >>
> >> Triage of bugs and patches is always welcome I guess, and communicating
> >> what needs to be applied/addressed first to whoever can actually commit
> >> it. That’s one possible way to help.
> >
> > Where can this be done? I know that Guix is using debbugs, but do Guile
> > does the same or is it all tracked on Savannah?
>
> It’s happening on debbugs.gnu.org as well. Debbugs this is easier to
> work with via Emacs debbugs.el, which is nice if you already use Emacs
> but otherwise unfortunate.
>
> > Also, any way to help on the C side?
>
> There isn’t much happening on the C side. Maxime Devos submitted
> patches adding bindings for openat(2) and friends that are unfortunately
> still pending review.
>
> Patches that add POSIX bindings and similar to libguile should in
> general be relatively easy to review (though the openat(2) one may be
> trickier because it’s a central functionality and we’d rather get the
> interface right.)
>
> Thanks,
> Ludo’.
>
>
[-- Attachment #2: Type: text/html, Size: 3123 bytes --]
next prev parent reply other threads:[~2022-08-19 16:49 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 ` 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é [this message]
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=CA+XASoVaLNSiXUfS3HAaxZaFrs5mPxkEGtH4dRyEJ88vA6cVWg@mail.gmail.com \
--to=aconchillo@gmail.com \
--cc=guile-devel@gnu.org \
--cc=jean@abou-samra.fr \
--cc=ludo@gnu.org \
--cc=olivier.dion@polymtl.ca \
/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).