unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Blake Shaw <blake@nonconstructivism.com>,
	Taylan Kammer <taylan.kammer@gmail.com>
Cc: "Olivier Dion" <olivier.dion@polymtl.ca>,
	"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: Sun, 19 Dec 2021 20:41:52 +0000	[thread overview]
Message-ID: <008e8b4adc8557148d0b9b68c6ea2277e514c492.camel@telenet.be> (raw)
In-Reply-To: <87r1a8icmd.fsf@nonconstructivism.com>

Hi,

Blake Shaw schreef op ma 20-12-2021 om 03:05 [+0700]:
> personally I've been programming for about 15 years now but my career
> has been entirely in new media (video, graphics, audio), so while
> I've
> worked with plenty of lower-level libraries over the years, I didn't
> start to get an itch for compilers until covid happened. I was also
> doing a PhD in philosophy of mathematics at the time (which I've
> postponed indefinitely to prevent being separated from my partner
> during 
> covid travel craziness) so I definitely think I have the *potential*
> to
> contribute to a project like Guile, its just a matter of finding the
> time to read some compiler books (which usually are neither short nor
> easy!).

I want to note that, while definitely the compiler part is an important
part of Guile, there's plenty of non-compiler and non-language things
in Guile as well, so reading compiler books should be unnecessary to
contribute to Guile.

E.g., things like getopt
(https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32154),
the HTTP API (https://debbugs.gnu.org/cgi/bugreport.cgi?bug=43711),
a bug fix in the test suite
(https://debbugs.gnu.org/cgi/bugreport.cgi?bug=43521) (verified to
work, for almost a year!).

Anyway, I would like to help when I get back to hacking, although I'd
have a (non-Guile) backlog to work through first, and there would be
some other projects I'd be working on as well.

Greetings,
Maxime.




  reply	other threads:[~2021-12-19 20:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-19 20:05 Maintenance and future of Guile Blake Shaw
2021-12-19 20:41 ` Maxime Devos [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2021-12-29 21:05 Blake Shaw
2021-12-29 21:57 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
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-15 13:35 Blake Shaw
2021-12-15 14:07 ` Ludovic Courtès
2021-12-13 22:18 Maintenance and future of Guile (was: [patch] Add instructions for sending patches) Jean Abou Samra
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

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=008e8b4adc8557148d0b9b68c6ea2277e514c492.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=blake@nonconstructivism.com \
    --cc=guile-devel@gnu.org \
    --cc=jean@abou-samra.fr \
    --cc=ludo@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    --cc=taylan.kammer@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).