From: Blake Shaw <blake@sweatshoppe.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: "Olivier Dion" <olivier.dion@polymtl.ca>,
"Ludovic Courtès" <ludo@gnu.org>,
"Taylan Kammer" <taylan.kammer@gmail.com>,
"Jean Abou Samra" <jean@abou-samra.fr>,
guile-devel@gnu.org
Subject: Re: Maintenance and future of Guile
Date: Sat, 20 Aug 2022 02:06:13 +0700 [thread overview]
Message-ID: <CAKjmbcC3y4yZu--CyRd+wSE8WpGeKdGhyXr_zMJtZrsUpZtWrg@mail.gmail.com> (raw)
In-Reply-To: <87pmgw5axd.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
Considering this conversation is coming back, I'd mention that I'd be happy
to become a Guile "janitor" (as discussed earlier) with some guidance, as
I've only been using Guile for a year and still learning the internals, but
have some patch series fixing some old bugs I've found.
I could also help with efforts like getting Guile's bug tracker to use
Mumi, and cleaning up various cobwebs -- noble & necessary custodial work :)
On Sat, Aug 20, 2022, 01:46 zimoun <zimon.toutoune@gmail.com> wrote:
> Hi,
>
> On ven., 17 déc. 2021 at 10:48, Olivier Dion via "Developers list for
> Guile, the GNU extensibility library" <guile-devel@gnu.org> wrote:
>
> > 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?
>
> Just to mention that Mumi (a web frontend of Debbugs) is serving all GNU
> bugs or patches managed by Debbugs. For one example about Guile,
>
> <http://issues.guix.gnu.org/issue/56665>
>
> Therefore, it could be a drop-in replacement of
> <http://bugs.gnu.org/56665> (the venerable Debbugs frontend).
>
>
> Well, Mumi is written in Guile, so maybe the Guile community could help
> to improve the situation for the whole GNU community using the GNU
> instance of Debbugs.
>
> https://git.elephly.net/software/mumi.git
>
>
> Cheers,
> simon
>
>
[-- Attachment #2: Type: text/html, Size: 2294 bytes --]
next prev parent reply other threads:[~2022-08-19 19:06 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é
2022-08-19 18:46 ` zimoun
2022-08-19 19:06 ` Blake Shaw [this message]
-- 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=CAKjmbcC3y4yZu--CyRd+wSE8WpGeKdGhyXr_zMJtZrsUpZtWrg@mail.gmail.com \
--to=blake@sweatshoppe.org \
--cc=guile-devel@gnu.org \
--cc=jean@abou-samra.fr \
--cc=ludo@gnu.org \
--cc=olivier.dion@polymtl.ca \
--cc=taylan.kammer@gmail.com \
--cc=zimon.toutoune@gmail.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).