X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Tue, 1 Sep 2015 19:37:16 +0200 (CEST)
X-X-Sender: igor2 AT igor2priv
To: 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] back annotation - phase 2, call for contributors
In-Reply-To: <201509011718.t81HIR58018562@envy.delorie.com>
Message-ID: <alpine.DEB.2.00.1509011933380.6924@igor2priv>
References: <alpine DOT DEB DOT 2 DOT 00 DOT 1509010447310 DOT 6924 AT igor2priv> <CAM2RGhRxevpXzeQpOV-OMtRhofjeSQxMkr0iFsutZ0a2EX9rcQ AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1509010743560 DOT 6924 AT igor2priv> <CAM2RGhSs=o0OT9AcWp9rfd=MRRxT3r5uyDa6VBcT66fXkEituw AT mail DOT gmail DOT com>
 <55E5A6BA DOT 4030606 AT jump-ing DOT de> <201509011657 DOT t81Gve9d017777 AT envy DOT delorie DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1509011913530 DOT 6924 AT igor2priv> <201509011718 DOT t81HIR58018562 AT envy DOT delorie DOT com>
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 Tue, 1 Sep 2015, DJ Delorie wrote:

>
>> For me, the important quesiton is whether the changes put in such a
>> branch gets into the next release - or is left in a feature branch
>> to bit rot.
>
> Changes put in a separate repo will surely not get into any release,
> unless they make it to the main repo first.  What ends up in the next
> release is up to the people willing to put in the work to make a
> release.
>
> Using the main repo for side projects at least keeps all the work in
> one place that everyone knows about, and thus less likely to be lost
> in the shuffle.

Thanx, these were all clear to me. Having the stuff in mainline is one of 
the local optimums. There are other local optimums, tho. And there are 
suboptimal points that combine the drawbacks of different solutions, like 
git + not having the stuff merged in mainline.

Before I make my decision, I really want to see the chances of getting an 
optimal solution vs. wasting time. This why I want to see, before I start 
in any direction, whether my ideas are backed up by mainline maintainers.

>
>> So what do you, gschem maintainers, think about the gschem-related points
>> of my proposal?
>
> For the record, I don't consider myself a gschem maintainer.  For
> not-pcb I just keep the server running.
>

Clear, I meant the "you" part in general. I am not sure who exactly are 
maintaining gschem nowdays. I have some guesses, but those guys did not 
comment any of the back annotation threads.

Regards,

Igor2