From: Taylan Kammer <taylan.kammer@gmail.com>
To: "Olivier Dion" <olivier.dion@polymtl.ca>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: Jean Abou Samra <jean@abou-samra.fr>, guile-devel@gnu.org
Subject: Re: Maintenance and future of Guile
Date: Sat, 18 Dec 2021 17:35:23 +0100 [thread overview]
Message-ID: <36193fea-e186-a4d0-abc4-2353cf4d7824@gmail.com> (raw)
In-Reply-To: <87ilvnmdv9.fsf@laura>
On 17.12.2021 16:48, Olivier Dion wrote:
> 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?
>
> Also, any way to help on the C side?
>
Guile also uses Debbugs:
https://bugs.gnu.org/guile
--
Taylan
next prev parent reply other threads:[~2021-12-18 16:35 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 [this message]
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=36193fea-e186-a4d0-abc4-2353cf4d7824@gmail.com \
--to=taylan.kammer@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).