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=date:from:to:subject:message-id:mail-followup-to:references
	:mime-version:content-type:content-disposition:in-reply-to
	:user-agent;
	bh=6f7q6SOmp7WEritJ2559//lXdUXH1gfZCprx2B4Qfco=;
	b=K2DC4e+iqhlDK1CYTTg17b+dC8729q7bRMKQXHCGd9Ut2n5G/lTdGwcg9ZzCgso7ZU
	zx28o2A8ausAwYiGxRvD+YokEr7kQ530UXYzKNVx5qP44SKYcPYemMeANgKZzfZ7ckAd
	+MAlO34lRYGNdxitDJ++AfepKVda2tDq3kWiIIBsAGV81/hb8Jkr7aRCrEBnx3jDIjgQ
	a7UUtFxmzFRRyxockC7Qfc/y5OZwNDIlFWEW7qXo1E8ixeGkjZU7emVZHXaPWfgRuHKK
	+B2Tes9bj2VKhUKxvaXpuylO4huTVA+9BuytJi39dqp6EpLoyBPT5/3t5cQIzyK4edHu
	uXmw==
X-Received:	by 10.112.168.100 with SMTP id zv4mr1323263lbb.117.1442016631453;
	Fri, 11 Sep 2015 17:10:31 -0700 (PDT)
Date:	Sat, 12 Sep 2015 03:10:29 +0300
From:	"Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] About reinventing the wheel, and how to avoid it
Message-ID:	<20150912001029.GG7946@localhost.localdomain>
Mail-Followup-To:	geda-user AT delorie DOT com
References:	<FC9C2933-89CE-44FD-A9EE-CA2721405ACE AT noqsi DOT com>
	<201509111941 DOT t8BJfqWl010427 AT envy DOT delorie DOT com>
	<D3D5A923-FAF9-4665-A0DB-A8D6A8BEA5A3 AT noqsi DOT com>
	<CA+uY=MS5ZOTHXDe9taav+0tCiZOqhtAJU2KO-xyRA3SrQVvLNw AT mail DOT gmail DOT com>
	<201509112020 DOT t8BKKBgI012564 AT envy DOT delorie DOT com>
	<E872F1BC-8FA7-449E-BA6D-5841AC79A465 AT noqsi DOT com>
	<201509112058 DOT t8BKwF3b013774 AT envy DOT delorie DOT com>
	<6341DF3E-543D-4E36-9B01-6B5B950208C4 AT noqsi DOT com>
	<20150911230843 DOT GE7946 AT localhost DOT localdomain>
	<201509112324 DOT t8BNOOOg019623 AT envy DOT delorie DOT com>
MIME-Version:	1.0
In-Reply-To:	<201509112324.t8BNOOOg019623@envy.delorie.com>
User-Agent:	Mutt/1.5.23 (2014-03-12)
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

On Fri, Sep 11, 2015 at 07:24:24PM -0400, DJ Delorie wrote:
> 
> > Who are those devs who decided the direction we are moving now?
> 
> Whoever's willing to do the work, gets to do the work, and those doing
> the work collectively decide direction.  Those who used to provide
> direction have left the project, for various reasons.  As the only
> remaining project admin, I've been trying to get people to take
> ownership of the abandoned projects, just ask you took over (by
> default ;) management of the wiki (and thank you :).
I'm always working on the wiki in the time constraints I have now (not
sure I understand your English thoroughly here).

> 
> > The geda-gaf moving to xorn seems to be a behind-the-scenes decision
> > of some pcb devs.
> 
> No, it was a project completely done by the xorn creator.
> 
> > Where is collaboration here? Who did ask active geda-gaf developers?
> 
> Queries to those "active geda-gaf developers" drew a blank.  In the
> absence of developers, those willing to take up the task prevail.  The
> project was discussed on the mailing list.  Did you volunteer to
> collaborate when it was discussed?
Brr, do you consider me an inactive developer? (I should admit my
working on the geda-gaf windows port took much more time than I thought
it would do before..., so I had less commits during those months... :)
At least there is Edward Henessy, who've made much work on gschem code
during a few last years.

> 
> > Who did ask users?
> 
> The xorn code was done by an independent person on his own time
> with his own repo.  Why should he ask anyone else's permission?
> 
> I asked him to at least use a branch on the project repo, to give his
> efforts more visibility.  Do I need permission to let folks create
> branches?

I think those TS decisions should be at least discussed first:
========================================================================
Right now, there is some code duplication between libgeda and Xorn since
I didn't update libgeda to use the new infrastructure yet.  This is on
my to-do list, though.
========================================================================

Cheers,
  Vladimir

- Raw text -