From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?QW5kcsOp?= Subject: Re: Help getting started with first contribution Date: Mon, 8 May 2017 23:32:47 -0300 Message-ID: <234ccd5d-be32-dec9-682d-985c2ecd7883@euandre.org> References: <80214a83-9c17-e9a3-a3be-1f4babb7a459@euandre.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------61444F335B70251DA0CE6A7C" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46012) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d7uxM-0002HM-Uc for Help-Guix@gnu.org; Mon, 08 May 2017 22:32:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d7uxJ-0000oB-QI for Help-Guix@gnu.org; Mon, 08 May 2017 22:32:56 -0400 Received: from box.euandre.org ([162.243.185.39]:44167) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1d7uxJ-0000nk-Kp for Help-Guix@gnu.org; Mon, 08 May 2017 22:32:53 -0400 In-Reply-To: Content-Language: en-US List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Catonano Cc: help-guix This is a multi-part message in MIME format. --------------61444F335B70251DA0CE6A7C Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 08/05/17 17:34, Catonano wrote: > 2017-05-08 5:25 GMT+02:00 Andr=C3=A9 >: > > 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 > =20 > > 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. > =20 > > 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 ! > =20 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/ > ). 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 > 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. > =20 > 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=C3=A9. > > > Welcome ! Thanks :) --------------61444F335B70251DA0CE6A7C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable



On 08/05/17 17:34, Catonano wrote:
2017-05-08 5:25 GMT+02:00 Andr=C3=A9 <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
=C2=A0
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.
=C2=A0
However, I'm not familiar=C2=A0 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 !
=C2=A0
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/). 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 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.
=C2=A0
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/cgi= t/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=C3=A9.


Welcome !
Thanks :)
--------------61444F335B70251DA0CE6A7C--