unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Daniel Tornabene <d.t.peters777@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: new maintainers for guile libs
Date: Wed, 4 Aug 2021 13:20:42 -0500	[thread overview]
Message-ID: <CAMo=-SCELG7-Xjb2EBOz4M9EyVT3D7XYksT0ngXWBL2qZZF1yw@mail.gmail.com> (raw)
In-Reply-To: <87zgtxpggk.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2200 bytes --]

I can't take more than one, but I would be happy to take guile-ncurses if
I'm deemed up to snuff, I've got a project I'm working on with it and when
that gets out in the world (next couple of weeks) I'll be happy to talk
about the commitments.

On Wed, Aug 4, 2021 at 7:02 AM Ludovic Courtès <ludo@gnu.org> wrote:

> Hi Mike,
>
> (Catching up on email…)
>
> Mike Gran <spk121@yahoo.com> skribis:
>
> > Well 2021 has been a strange time for me as it has been for many.  At
> > the beginning of 2021, I had the free time and the good health that
> > allowed me to imagine being a real contributer again, but, stuff has
> > changed.
>
> I’m sad to read this; I hope you’ll recover soon and feel energized,
> including to hack the good hack.
>
> > So there are a few libraries in the Guile ecosystem I've worked on,
> > and I'm hoping someone else might be interested in owning them
> > henceforth.
> >
> > Roughly in order of maintainability, from simple to complex, these are
> >
> > - guile-aspell: a very simple binding to the Aspell spellcheck
> >   library. This would be an easy task, since it is a Guile-only
> >   binding with no C, and aspell rarely changes
> > - guile-curl: a C-based but straight-forward binding the the cURL API.
> > - guile-ncurses: a C-based binding for NCurses, libpanel, and libmenu.
> It
> >   is a bit convoluted bcause the memory model for ncurses it iself
> >   quite strange.
> >
> > Then there a couple of very obscure and little used libraries that I
> could
> > punt on, but, I don't really expect any interest
> >
> > - guile-plotutils: draw plots in Guile using the plotutils backend
> > - zile-on-guile: a version of the zile editor, replacing its tiny LISP
> >   interpreter with Guile.
> >
> > Guile-GI is a special case because at this point, I'm probably not the
> > prinmary contributor. But it could use more contributers and could use
> > a discussion about how to move it forward. I still hope to contribute
> > as I can.
>
> I won’t commit to anything (I’d do a poor job), but these are all useful
> pieces of software and I hope someone picks them up!
>
> Thanks,
> Ludo’.
>
>
>

[-- Attachment #2: Type: text/html, Size: 2762 bytes --]

  reply	other threads:[~2021-08-04 18:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210630045758.GA121598.ref@spikycactus.com>
2021-06-30  4:57 ` new maintainers for guile libs Mike Gran
2021-07-01 10:58   ` Zelphir Kaltstahl
2021-08-04 12:00   ` Ludovic Courtès
2021-08-04 18:20     ` Daniel Tornabene [this message]
2021-08-05 15:19       ` Mike Gran

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='CAMo=-SCELG7-Xjb2EBOz4M9EyVT3D7XYksT0ngXWBL2qZZF1yw@mail.gmail.com' \
    --to=d.t.peters777@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=ludo@gnu.org \
    /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).