unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Artem Chernyak <artemchernyak@gmail.com>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Jean Abou Samra" <jean@abou-samra.fr>,
	guile-devel@gnu.org
Subject: Re: Maintenance and future of Guile
Date: Fri, 17 Dec 2021 09:33:01 -0600	[thread overview]
Message-ID: <CALP7HJsDbKYQvnEJbv2Vk8J5yOAdtd=f5LRKvDHdtJGufNCMmA@mail.gmail.com> (raw)
In-Reply-To: <87lf0jmgid.fsf@laura>

I am in the same boat as Taylan and Olivier. My knowledge isn't up to
snuff to be a full fledged maintainer, but I would love to contribute
more.

I'm able to give 5-10 hours per week to whatever tasks we need to keep
things running smoothly.

On Fri, Dec 17, 2021 at 9:19 AM Olivier Dion via Developers list for
Guile, the GNU extensibility library <guile-devel@gnu.org> wrote:
>
> On Thu, 16 Dec 2021, Taylan Kammer <taylan.kammer@gmail.com> wrote:
> > On 15.12.2021 11:20, Ludovic Courtès wrote:
> > I won't apply because I don't feel like I'd be up to the task on a
> > technical level (my C skills in particular suck, my knowledge of Guile
> > internals is also quite limited) and I have way too many unfinished
> > projects plus a somewhat stressful 40h/week job...
> >
> > But I would definitely like to contribute some small patches every now
> > and then if I know I'll get feedback / have them applied.
>
> 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?
>
> --
> Olivier Dion
> Polymtl
>



  reply	other threads:[~2021-12-17 15:33 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 [this message]
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
  -- 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='CALP7HJsDbKYQvnEJbv2Vk8J5yOAdtd=f5LRKvDHdtJGufNCMmA@mail.gmail.com' \
    --to=artemchernyak@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).