From: André <eu@euandre.org>
To: Catonano <catonano@gmail.com>
Cc: help-guix <Help-Guix@gnu.org>
Subject: Re: Help getting started with first contribution
Date: Mon, 8 May 2017 23:32:47 -0300 [thread overview]
Message-ID: <234ccd5d-be32-dec9-682d-985c2ecd7883@euandre.org> (raw)
In-Reply-To: <CAJ98PDxoR2+WuEueOjpzpvUwe+ESfnRzCo+66U0tNMZMUR4iCA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3166 bytes --]
On 08/05/17 17:34, Catonano wrote:
> 2017-05-08 5:25 GMT+02:00 André <eu@euandre.org <mailto:eu@euandre.org>>:
>
> Hi there, fellow Geeks!
>
>
> I've been using Guix and GuixSD recently and I'd like to contribute!
>
> I do know both Common Lisp and Clojure, so using Guile shouldn't
> be a problem.
>
>
> It won't be. I also learned Clojure before Scheme
>
>
> I'd like to start with small tasks, like adding a few simple
> packages, then move to bigger packages, then write some services,
> and so on.
>
>
> Good plan. That's what I thought for me too.
>
>
> However, I'm not familiar at all with mailing list workflows
> (this is the first mailing list I actually subscribed to), so I
> may need some guidance with that.
>
>
> Wow, you must be quite young !
>
Not that much, actually. I've been programming for 3-4 years, but mostly
in a GitHub-centric world.
>
>
> I thought about starting by creating a Guix package for
> git-remote-gcrypt
> (https://spwhitton.name/tech/code/git-remote-gcrypt/
> <https://spwhitton.name/tech/code/git-remote-gcrypt/>). The
> package definition should be fairly simple, since the main program
> is just a shell script with no compilation dependencies.
>
> I've read the section 8.5 "Submitting Patches" of the manual, so I
> think I'm good to go.
>
> Is there any specific example of a similar simple package that I
> should base mine on? Is there anything else that I should be aware of?
>
>
> An immediate reccomendation is to use the guix-patches@gnu.org
> <mailto:guix-patches@gnu.org> mailing list
>
> That's the mailing list for patches
>
> guix-devel is ust for discussions
>
> You might want to use git send-mail instead o your usual email client.
> It's not required, but it helps you to make your submission more
> conformant to expected formats
Thanks for the tip.
>
> Especially if you want to submit a patches series and not a single
> patch, that can be very useful.
>
> If your first package is a siingle patch, you can just attach the
> patch to an email message to the guix-patches mailing list.
>
> Pay attention to the ormat if the log message (take a look at other
> log messages in the git log, here iis a web version
> https://git.savannah.gnu.org/cgit/guix.git/log/ )
>
> Configuring git send-email and possibly GNUs is a whole topic and it
> probably beyond my strength right now
>
Thanks, I'll figure out how to configure it properly.
> When your message (with the attached patch) will be received, someone
> will review it and likely suggest modifications
>
> You will reply with a new version (as an attached patch as usual)
>
> When your patch will be ready, someone with committ permission will
> commit it for you
>
> When your patch will be committed, you will see it in the git log as
> authored by you and signed by the committer who committed it or you
>
> Hope this helps !
>
>
> I'm looking forward to being part of this community.
>
> Thanks in advance,
> André.
>
>
> Welcome !
Thanks :)
[-- Attachment #2: Type: text/html, Size: 7506 bytes --]
next prev parent reply other threads:[~2017-05-09 2:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 3:25 Help getting started with first contribution André
2017-05-08 20:34 ` Catonano
2017-05-09 2:32 ` André [this message]
2017-05-12 5:52 ` Ricardo Wurmus
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=234ccd5d-be32-dec9-682d-985c2ecd7883@euandre.org \
--to=eu@euandre.org \
--cc=Help-Guix@gnu.org \
--cc=catonano@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).