From: brettg@posteo.net
To: guile-devel@gnu.org
Cc: guile-devel <guile-devel-bounces+brettg=posteo.net@gnu.org>
Subject: Re: Where to start
Date: Wed, 27 Feb 2019 05:38:23 +0100 [thread overview]
Message-ID: <4d78ff7e640b2f12cc7b40408eb9398b@posteo.net> (raw)
In-Reply-To: <2098616274f21adf2d924a54a8a13587@posteo.net>
I guess, on some level I am asking how to go about familiarizing myself
with the code. How to approach understanding the logic behind each
directory. Is there a map that designates the differences between /lib
and /libguile? So on.
On 27.02.2019 02:22, brettg@posteo.net wrote:
> Hi there. I think some of you already know me from the Guix mailing
> lists. I come from a biosciences background, and am transitioning into
> a career in computer science. I plan on starting my masters this year.
> A large part of my interest has been in LISPs, and particularly Guile
> and other implementations of Scheme.
>
> I know that Guile 3 is right around the corner, and i'd like to be
> able to lend a hand in getting it ready for that. I have experience in
> both Scheme and C. This would be my first contribution to a C project
> though. I am curious if there is some resource that explains where I
> may focus my efforts? I know the bug tracker is available for this,
> but where else may I focus my attention?
>
> I imagine most of what we need for Guile 3 is in a feature-freeze more
> or less, so I just want to get my cards in order before I start
> throwing any patches out.
>
> Best,
> Brett Gilio
next prev parent reply other threads:[~2019-02-27 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 1:22 Where to start brettg
2019-02-27 4:38 ` brettg [this message]
2019-03-01 11:32 ` Mike Gran
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=4d78ff7e640b2f12cc7b40408eb9398b@posteo.net \
--to=brettg@posteo.net \
--cc=guile-devel-bounces+brettg=posteo.net@gnu.org \
--cc=guile-devel@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).