X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=ArOW+2hSF9GkupJWuwKEYqsU2IsVhGfIjRM1axAh0ng=;
        b=TXk0HOh1prtnpgJjUVbpdJClVcJJbEdCXy2X4GGxZb9xo0rOio8nhpjYwzQKEwslsY
         h7XmTDPecV/vOHyP38PAL+h4qdO5GBWGtrVHP/m+NHCsMMB6k5Sx2mdkVrg6u9EXTGVM
         6KIFCcg0dqMB/fAi1vVtlmw9YSXpEmZSHSDszLGra3A+5LUutcemE1r2yDtOlsMMVUep
         o3TjdotGqxqDaFHyZYmBLf0j6yiQFR5u4fOhZg6szvFmUz5aRfUAT6U4sCZxeNlDcSpZ
         PNxE1U5HSbFGVJo1VYSFRuYQr01Jg+aNoT2t9o7Dplf5GY5AjxBLsPOaZUPHt6QgsOIl
         8z2Q==
MIME-Version: 1.0
In-Reply-To: <508AF21E.2090400@xs4all.nl>
References: <CANqhZFxYH+Y5U1ai7ey-s+4nz6eYDM2vx3aMDb7WuigNXmi4AQ AT mail DOT gmail DOT com>
	<50892DC8 DOT 6080308 AT laserlinc DOT com>
	<201210251629 DOT q9PGTfes029100 AT envy DOT delorie DOT com>
	<50897B77 DOT 1030401 AT laserlinc DOT com>
	<201210251859 DOT q9PIxw7n004895 AT envy DOT delorie DOT com>
	<F720A597-665F-40D1-B1A4-E02506EE5D09 AT jump-ing DOT de>
	<CAGde_xNNrA-QMcXiNQJEkPSfFGeZWLyULAqh0pZfkPAV898NQQ AT mail DOT gmail DOT com>
	<8CD82772-DF1C-4C82-852C-B9F6A094CBAA AT jump-ing DOT de>
	<CAGde_xNtp8tb82kiggdzbq-3X7zMY5sHu5TS7dLxJooX3K-pFA AT mail DOT gmail DOT com>
	<F3B81D9B-82F1-4F13-8DED-93BD106C5414 AT jump-ing DOT de>
	<CAGde_xM=x5P5yiSMQ0wTGaCATdToY-TcYbcoNTxh1E_m4Ky9tg AT mail DOT gmail DOT com>
	<508AF21E DOT 2090400 AT xs4all DOT nl>
Date: Fri, 26 Oct 2012 23:30:35 +0200
Message-ID: <CAGde_xPsPO+bhr0WUfUZzboK341FiN5xY_JMzKKfVyG_drq63g@mail.gmail.com>
Subject: Re: [geda-user] The state of gEDA/gaf
From: Svenn Are Bjerkem <svenn DOT bjerkem AT googlemail DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=ISO-8859-1
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 26 October 2012 22:27, Bert Timmerman <bert DOT timmerman AT xs4all DOT nl> wrote:

> Hi Svenn,
>
> ATM I'm doing a Dutch translation of the scheme-api texi documentation for
> geda-gaf, nothing else planned yet.

I have added your github fork to my remotes so I will be able to fetch
and follow whatever you do or whatever feature branches you push to
your fork.

>
> Last time I did some work on geda-gaf it was done as described above, after
> the last commit a pull request to Peter B's Github fork, and he reviewed and
> pushed to upstream "master".
>
> IMHO the most interesting stuff is most likely to be found in topic
> branches, as the local "master" is almost always lagging behind the upstream
> "master".

I added several of the contributors known from this mailing list to my
remotes. With gitk --all it is easy to monitor the lags and the
feature branches. Watching the network on peter-b's fork on github
(clicking the little number next to fork in the upper right corner),
it is quite easy to see how the forks of peter-b's fork propagate.

In my honest opinion after this evenings work, the
git.geda-project.org base code should have been in place of peter-b's
on github. But that is just a very quick personal impression.

>
> In Git branching is too cheap and easy: just "git checkout -b <new_branch>"
> from the CLI.

Fortunately it is a bit more mentally expensive to push local branches
back to the remote repository. All the stuff about rewriting history
then applies as the branch is known to the world. (Can't protect
against ignorance, though)

>
> Another thing in Github is that one may "suffer" from "drive-by" commits and
> single contributions: one or two of them and just when you think you have a
> collaborator .... gone with the wind.

With git add remote it is possible to just pick up whatever forks is
present and on regular intervals do a git fetch on them to see if
something interesting is happening. I don't know if github manages to
create network diagrams of forks of forks of forks in the web
interface, but since all forks have plenty of common SHAs, gitk can
line them up.

I added a bit on git add remote on geda:scm in the wiki. I happened to
use your fork among others in the example.

-- 
Svenn