Message-ID: <4F1C643E.7080503@gmail.com>
Date: Sun, 22 Jan 2012 14:32:14 -0500
From: Darryl Gibson <n2diy2 AT gmail DOT com>
Organization: RKBA!
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111108 Thunderbird/3.1.16
MIME-Version: 1.0
To: geda-help AT delorie DOT com
Subject: Re: [geda-help] Help, how can I help?
References: <4F1A1196 DOT 20100 AT gmail DOT com> <201201210150 DOT q0L1o04r012622 AT envy DOT delorie DOT com>
In-Reply-To: <201201210150.q0L1o04r012622@envy.delorie.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Reply-To: geda-help AT delorie DOT com

On 01/20/2012 08:50 PM, DJ Delorie wrote:
> This is getter for geda-user - you're not asking for help, you're
> asking how to get involved.  But I'll answer here anyway :-)

A getter? Haven't heard that term since I was studying vacuum tubes! :)

> The gEDA project uses a couple of languages, but primarily we use C
> and guile (a scheme/lisp variant).  There are some ancillary
> languages, like Makefiles, shell scripts, M4, etc.

Ok, I think I should get acquainted with make, I've noticed folks
experiment with that fairly often.

And I'll tackle C, I've been shying away from it for years because it
looks like it has a steep learning curve.

> 
> As for git, you should at least learn how to clone and update a source
> tree so you can stay up to date, and generate a diff to pass
> "upstream".

Ok. I just did a clone Saturday night, do I need to update too?

And I'll hit the books to learn the terminology and concepts of git.

> To learn the *sources* however, your best bet is to dig into the bug
> list, pick something that you think might be easy to fix, and see if
> you can fix it.

Roger that.
-- 
Darryl Gibson N2DIY
Linux, free software, for the people, by the people.