From: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: guile-user@gnu.org
Subject: Re: guile-squee could probably use another maintainer
Date: Mon, 12 Oct 2020 10:22:04 -0400 [thread overview]
Message-ID: <87y2kb5xtf.fsf@dustycloud.org> (raw)
In-Reply-To: <875z7g75yf.fsf@dustycloud.org>
Well, cbaines now has commit access!
So maybe that helps. :)
Christopher Lemmer Webber writes:
> Hello! I just merged a couple of stale PRs in guile-squee, one of which
> had been sitting around for months. I had for some reason thought I had
> already appointed a co-maintainer.
>
> I might do a better job of stewarding it once Spritely Goblins is ported
> to Guile (sometime in the next 4 months I think) but I'm not actively
> using it at the moment. It might be a good job to give commit access or
> maintainership to someone who is.
>
> Christopher Baines submitted a sensible PR, maybe is a reasonable
> candidate.
>
> I still like the name. I'd be curious who's using it, if anyone, btw.
> - Chris
next prev parent reply other threads:[~2020-10-12 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 22:28 guile-squee could probably use another maintainer Christopher Lemmer Webber
2020-10-12 14:22 ` Christopher Lemmer Webber [this message]
2020-10-13 20:19 ` Ludovic Courtès
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=87y2kb5xtf.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guile-user@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).