X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Sun, 23 Aug 2015 17:12:12 +0200 (CEST)
X-X-Sender: igor2 AT igor2priv
To: "Markus Hitter (mah AT jump-ing DOT de) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From: gedau AT igor2 DOT repo DOT hu
Subject: Re: [geda-user] Antifork
In-Reply-To: <55D9D8C2.8070200@jump-ing.de>
Message-ID: <alpine.DEB.2.00.1508231704490.6924@igor2priv>
References: <55D8D8B8 DOT 7050907 AT jump-ing DOT de> <20150822230549 DOT 3750 DOT qmail AT stuge DOT se> <55D9A5AE DOT 9090604 AT jump-ing DOT de> <20150823134609 DOT 2918 DOT qmail AT stuge DOT se> <55D9D8C2 DOT 8070200 AT jump-ing DOT de>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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 Sun, 23 Aug 2015, Markus Hitter (mah AT jump-ing DOT de) [via geda-user AT delorie DOT com] wrote:




While we disagree in most things, I'm happy to see we agree at least in 
these:

>
> Now, if you think there are goals neccessary for collaboration, why not formulate them? My own goals are currently:
>
> - Collect (or mark as unsuitable) all the bug fixes in all the forks.

Great! Make it a long lasting practice!

If you somehow bump into the long-dead git copy of pcb-rnd, you could 
consider merging the flagcomp patches (those are really small and would 
help a lot in file format compatibility between random forks).

I also suggest if an occasional user drops in with a bugreport or even a 
patch, collect it and put it in the repo instead of directing him to 
repeat the bugreport in more formal ways (e.g. launchpad). Get the fixes 
in mainline as fast as possible and send him a notification about his fix 
got merged. Without this, he won't bother to file his second bugreport.

> - Gain visible activity by doing the above.

I recommend maintaining a status report on bugfixes merged and bugs still 
standing and mailing the results to the list from time to time.

Regards,

Igor2