From: Ricardo Wurmus <rekado@elephly.net>
To: André <eu@euandre.org>
Cc: help-guix <Help-Guix@gnu.org>
Subject: Re: Help getting started with first contribution
Date: Fri, 12 May 2017 07:52:37 +0200 [thread overview]
Message-ID: <87o9uysjtm.fsf@elephly.net> (raw)
In-Reply-To: <80214a83-9c17-e9a3-a3be-1f4babb7a459@euandre.org>
Hi André,
> I've been using Guix and GuixSD recently and I'd like to contribute!
Excellent!
> 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.
It’s pretty simple: you send an email to guix-patches@gnu.org (you will
get an automated reply with a bug identifier) and wait for someone to
comment. If you need to make changes you just send email to the bug
address.
> I thought about starting by creating a Guix package for
> 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.
Sounds good. You may find that programmes using the GNU build system
are usually the easiest to package. Sometimes simple shell scripts or
custom build systems make unrealistic assumptions about the system that
they are installed on, which makes the package definition a little more
complicated.
In the case of git-remote-gcrypt, for example, you will need to delete
the “configure” and “build” phases, set the “prefix” in a make-flag, and
create the target directories in an extra build phase.
> I'm looking forward to being part of this community.
We’d be happy to see you join us!
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
prev parent reply other threads:[~2017-05-12 5:52 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é
2017-05-12 5:52 ` Ricardo Wurmus [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=87o9uysjtm.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=Help-Guix@gnu.org \
--cc=eu@euandre.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).