X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <5618C616.7050502@xs4all.nl>
Date: Sat, 10 Oct 2015 10:02:30 +0200
From: "Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.19) Gecko/20110429 Fedora/2.0.14-1.fc13 SeaMonkey/2.0.14
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] GTK3, Glade interface designer (router, auto?)
References: <20151003210701 DOT de392b925f54dadb0a5fedd8 AT gmail DOT com> <1443975731 DOT 671 DOT 52 DOT camel AT ssalewski DOT de> <20151004191717 DOT bf8223417541a9306bfbd9ea AT gmail DOT com> <CAC4O8c9Bi5HJfcW6wUgm_+4O2gs4vDdBMbS2hF_0dCqnBuJahQ AT mail DOT gmail DOT com> <1443997480 DOT 2068 DOT 32 DOT camel AT ssalewski DOT de> <CAC4O8c-bnGky=Nab59-pOTJkB8Q9Tc5t5hqE+dnEF-777hUjMg AT mail DOT gmail DOT com> <1444070851 DOT 1014 DOT 20 DOT camel AT ssalewski DOT de> <muv4ua$hat$1 AT ger DOT gmane DOT org> <alpine DOT DEB DOT 2 DOT 00 DOT 1510060356440 DOT 7137 AT igor2priv> <56133047 DOT 7030402 AT neurotica DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1510060433080 DOT 7137 AT igor2priv> <56133CC4 DOT 7000306 AT neurotica DOT com> <56137585 DOT 2030004 AT jump-ing DOT de> <CAM2RGhRZoQSJ-kUQfBTngGktreLbrM6=gbr=-+cUO4hx=2RavA AT mail DOT gmail DOT com> <201510061806 DOT t96I6tUG026305 AT envy DOT delorie DOT com> <56142095 DOT 8030800 AT jump-ing DOT de> <alpine DOT DEB DOT 2 DOT 00 DOT 1510070535130 DOT 7137 AT igor2priv> <mv2u4p$7a2$1 AT ger DOT gmane DOT org> <alpine.DEB.2.00.1510071314110.7137! !@igor2priv> <mv4k4c$tip$1 AT ger DOT gmane DOT org> <201510080301 DOT t9831weq018628 AT envy DOT delorie DOT com> <mv9veh$l8j$1 AT ger DOT gmane DOT org>
In-Reply-To: <mv9veh$l8j$1@ger.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com

Kai-Martin Knaak wrote:
> DJ Delorie wrote:
>
>    
>> Arguing over how forky a fork is is, well, petty.  Igor2 is doing
>> something different with the code, fine.  He's also still involved
>> with us, fine.  Why is this a problem?
>>      
> He presented his project as "a _proper_ fork" (underline in the
> original).
>
>
>    
>> It's no different than every
>> git branch we create being a "fork" that may or may not get merged,
>> other than irrelevent mechanics and probabilities.
>>      
> Igor consistently declares to have no intentions to merge his changes
> back to main line geda. Creators of feature branches typically are
> motivated by the prospect to have their feature merged. To me this
> represents the difference between a fork and a temporary side step.
>
> ---<)kaimartin(>---
>
>
>    
Hi Kai-Martin and list members,

I think everyone should scratch their own itch first, before rubbing others.

A quote from a US president comes to mind: "Lead, follow or get out of 
the way".

At the time gEDA/pcb didn't lead (properly), nor followed upon Igor2's 
plans, so Igor2 started a fork.

Given the history on this one I think it's OK for Igor2 to branch/fork 
and then wait for the others (gEDA/pcb developers)to make a first step: 
and that would be committing branched/forked code snippets into the 
gEDA/pcb repository.

So far I see no efforts being made to incorporate his forked code.

Not even a Launchpad (LP) bug report is filed or a single topic branch 
started, so patches can't be included for testing.

All of us gEDA/pcb developers are busy doing other things and have 
prioritized them higher.

I for one would like to delve into this, make an implementation plan and 
start committing.

It's just that I have only a hand full of spare cycles every day (yeah, 
that's a lame excuse ;-).

Getting people motivated for a monthly effort to work on indentified 
bugs is a higher priority for me --> more developers ==> more spare 
cycles available ==> more bugs squashed.

For users/consumers it's easy: file a bug report and wait see what 
happens, give a few reminders if things take too long and move on to 
other software if it isn't solved within a year or so.

And as you may have noticed: *we* (few) developers have a massive backlog.

Another issue (pet project) that has a higher priority for me, is 
getting pcb Doxygenated, as to give a better and easier understanding of 
what is going on inside pcb, for current and future developers --> more 
spare cycles better used ==> more efficiency.

And third: every *team* needs a common goal, so first of all *we* need a 
good plan to get the efforts of *us* developers aligned (team == 1 
common goal, group of "N" people == "N" individual goals).

Launchpad Blueprints (https://blueprints.launchpad.net/pcb) are a good 
place to write up plans, some examples are provided for, see it as a 
"Facebook" for developers if you will.

These Blueprints can be linked against bug reports.

It's available and editable to *everyone* having a LP account, and as a 
side effect all subscribers get a notification by e-mail if something 
changes, just to keep them informed.

So to summarize: lots of work to be done --> no time for infights --> 
let's all take a first constructive step today ;-)

Kind regards,

Bert Timmerman.

BTW: maybe some of this should go into the wiki.