unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Charlie Sale <softwaresale01@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Personal Introduction
Date: Tue, 12 Dec 2017 09:56:32 -0500	[thread overview]
Message-ID: <CAG0TemRXc_gLxBOCm2o52uHb9Pa1Tq8vCQJB4mZjSvpcc=sAGA@mail.gmail.com> (raw)
In-Reply-To: <87fu8gqfe1.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

Awesome, thanks! I'll take a look at packaging.

On Dec 12, 2017 7:50 AM, "Ludovic Courtès" <ludo@gnu.org> wrote:

> Hello Charlie,
>
> Charlie Sale <softwaresale01@gmail.com> skribis:
>
> > My name is Charlie, and I am interested in joining the Guix
> > development community. I was wondering if there are any small tasks or
> > projects that I could start with to learn about the project's
> > source. I would like to add that I am pretty new to Guile, but I do
> > have a base understanding on how Scheme and Lisp work.
>
> A good way to get started is of course to start using Guix(SD), and then
> to contribute new packages.  The “Defining Packages” section of the
> manual should help get you started, and then people on #guix on IRC and
> on the help-guix@gnu.org mailing list will be happy to help.
>
> Our bug tracker at <https://bugs.gnu.org/guix> has some items explicitly
> marked as “easy” (though probably too few of them), which you might
> later want to look at.
>
> Welcome, and happy hacking!  :-)
>
> Ludo’.
>

[-- Attachment #2: Type: text/html, Size: 1581 bytes --]

      reply	other threads:[~2017-12-12 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12  3:22 Personal Introduction Charlie Sale
2017-12-12 12:50 ` Ludovic Courtès
2017-12-12 14:56   ` Charlie Sale [this message]

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAG0TemRXc_gLxBOCm2o52uHb9Pa1Tq8vCQJB4mZjSvpcc=sAGA@mail.gmail.com' \
    --to=softwaresale01@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).