X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-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=9z8Vu1olcs54Hn7FQLgTQocM/QJt5RyvB/SFv5AAXFg=;
        b=Ye4WEj7c1evZl6lBq5+Y9WRHZufMfaytO7Tjj0iXuMnZUdjz59mOb5uoXEa/Ylqe29
         8yGor52fu0qEedo7j4N8QumUyb617+dcVi1ynyq0nDBGvnn/Ilut4IxP9d5Fa6YCn6Iy
         JEPzPNhcWCi9X4PtX+U9uGbY2lDWZz9pSGjBH42EsiP1XeKl3C7KU6BZtT9cyO90LVTP
         RDCwlTDQHJl+rESlhn6nxCO92TnuYfkyd1POEpxe2LDhYaKuDFkaU1xKbZDs0dmjDzcS
         RLgKqftSImeGQIznNFdkr/EvvkRSlBnQYWx4hRAI/RVJuXGxvb0Vxf39pWd3Tfaxvy1a
         yMvQ==
MIME-Version: 1.0
X-Received: by 10.112.160.73 with SMTP id xi9mr27561739lbb.92.1440540906545;
 Tue, 25 Aug 2015 15:15:06 -0700 (PDT)
In-Reply-To: <CAC4O8c_HdSL-3+etrvPozAZuqUX-Rqx4FGACkchttRkZsFhYPA@mail.gmail.com>
References: <55D8D8B8 DOT 7050907 AT jump-ing DOT de>
	<CAM2RGhSZ1vi_DFKqZdZYxhto4ZaXLLscBt5m5kk+PH2ZoYW_vw AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1508230609370 DOT 6924 AT igor2priv>
	<55D9BDC7 DOT 4000608 AT jump-ing DOT de>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1508231450350 DOT 6924 AT igor2priv>
	<CAM2RGhSC6UfCr8ixF5iuffmUhcdgVuz9nA+YjiZNk8-f7Q5r-A AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1508231935040 DOT 6924 AT igor2priv>
	<CAC4O8c8PyLQNgxz1SP-98ZhyH5KPDmnNpiULVvdL+TMo-DhN4w AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1508240407100 DOT 6924 AT igor2priv>
	<CAC4O8c_HdSL-3+etrvPozAZuqUX-Rqx4FGACkchttRkZsFhYPA AT mail DOT gmail DOT com>
Date: Tue, 25 Aug 2015 22:15:06 +0000
Message-ID: <CAM2RGhQMUdE_Z6OnJPTgTbkcQ4fWp6rGnrXib48S71tsGmMMSw@mail.gmail.com>
Subject: Re: [geda-user] Antifork
From: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
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 Tue, Aug 25, 2015 at 9:23 PM, Britton Kerin
(britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]
<geda-user AT delorie DOT com> wrote:
> On Sun, Aug 23, 2015 at 6:29 PM,  <gedau AT igor2 DOT repo DOT hu> wrote:
>>
>>
>> On Sun, 23 Aug 2015, Britton Kerin (britton DOT kerin AT gmail DOT com) [via
>> geda-user AT delorie DOT com] wrote:
>>
>>>
>>> Unfortunately no one is going to be nearly so well positioned to merge
>>> your
>>> stuff as you are.  Relatively, it will be painfully inefficient for
>>> them and they
>>> will feel it as they work.
>>
>>
>> Unfortunately no one is as unmotivated to invest time in this as I am. This
>> won't happen, sorry.
>
> I take it you acknowledge that no one can do it as easily as you.  But
> I guess you
> also feel that since others don't want to bother much, there's no
> reason you should
> bother or use build/vcs you dislike.

I know we would all like Igor2 to do what *we* want but isn't it
enought that he is gifting us with code that is written around our
project? The answer is no and we should respect that he does not want
to carry us. Surely someone else can look at his VCS commits, do some
diffs and make some patches. The mission for those people (including
me) who want PCB to stay around should be to figure out how to do
this, not how to control someone else's time.

> Suppose someone else did do the work to merge it this time, would you feel then
> feel more or less inclined to use common build system etc. and generally
> design-for-mergability in the future?

I don't think the build system is the real issue in mergability but a
fair point.

>>> The reason everyone is so worked up about this particular fork is that it
>>> has
>>> the most interesting new features in a long time.  I'll take another run
>>> at
>>> testing it soon.  But I agree with others that to give up on merging it is
>>> very sad, especially when the problems are things like VCS and build
>>> system,
>>> that don't even have anything to do with the core functionality.
>>
>> I didn't give up on the merge: I never intended to push it in the first
>> place. It's totally indifferent for me as I am not an user of the mainline
>> pcb. If anyone decides to merge whichever part he likes, that's fine. If he
>> has questions about why/how some parts are implemented, I'm happy to
>> explain.
>>
>> Forks may have different purposes. Some forks are created by the author in
>> hope that he can merge it back to mainline, some are not.
>
> I guess if you're correct that nothing worthwhile to you will happen
> in mainline pcb ever again, you have the right approach.  Otherwise its a loss
> for you as well as everyone else.
>
> My fantasy when I heard about ruby scripting in pcb was that perhaps Stefan's
> router might someday see the light of day afterall.  Oh well

I keep seeing mentions of this legendary router. I have been these
gEDA lists +10 years but I don't remember it. What was the big appeal
if it?

> Britton

Evan

-- 
Home
http://evanfoss.googlepages.com/
Work
http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/