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=o4nYtThdw+CMG9FiifueFWjhj7+ujzU2RHhzUHPCu9g=;
        b=BPlUjHaGb1u1Hm/1+b40mcnQ699LZK24YGV3duyXZPxdOx694HR/uVVZgeuIgkZtSF
         G4senLHry2CF4XqK3W2fDq16OhVFZsak77E0ZXKwebDaCvUux7HY4mm0JTNR6ok3nrRD
         YUbdIvNjAaPV555BJvvtJRYkFDLyL4OMJ8/7u3BaBNLnp0tNewl1OLHI4tfmOKtSA1OB
         sQWoKffzlQsdrUynNuvdhYuk30emvJhR4h7r/iOEQv2quS3OXrsiVPYBWRVzplntROkM
         JtHdutGFmPwfiMhcpVOLq69DiYh4WZTSco2xtC19brOJKXhrjOK1baqo++Q8neM64anZ
         xsOw==
X-Received: by 10.112.150.3 with SMTP id ue3mr1462010lbb.51.1442019150540;
        Fri, 11 Sep 2015 17:52:30 -0700 (PDT)
Date: Sat, 12 Sep 2015 03:52:28 +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: <20150912005228.GH7946@localhost.localdomain>
Mail-Followup-To: geda-user AT delorie DOT com
References: <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>
 <20150912001029 DOT GG7946 AT localhost DOT localdomain>
 <201509120021 DOT t8C0LoAD021835 AT envy DOT delorie DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <201509120021.t8C0LoAD021835@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
Precedence: bulk

On Fri, Sep 11, 2015 at 08:21:50PM -0400, DJ Delorie wrote:
> 
> > I'm always working on the wiki in the time constraints I have now (not
> > sure I understand your English thoroughly here).
> 
> Sorry, I mean "Thank you for being an example of the kind of person
> I'm looking for - someone willing to help make the project better.  I
> wish there were more who were willing to help, especially to become
> leaders."
Thank you, though speaking particularly about geda-gaf I believe
becoming a leader of an existing project requires at least an approval
of some/any other former admin(s) who could at length not agree they're
inactive, just maybe more busy. That is why I've been talking about the
project leadership a while ago.
> 
> > Brr, do you consider me an inactive developer?
> 
> There was a recent call to the gaf maintainers asking about a release
> schedule.  As far as I know, nobody has answered yet.  Lots of
> gaf-related emails to the mailing list go unanswered because there is
> no "owner" of gaf any more.
AFAIK, we had at least four geda-gaf admins before now (I mean Ales,
Stuart, Peter Brett and Peter Clifton). What does 'owner' mean in this
case?

If you have not noticed, it was me who asked the question about future
plans. And I've asked since I *want* the release to happen, just don't
know what to do to make it possible yet.

> 
> > I think those TS decisions should be at least discussed first:
> 
> So discuss them :-)
That is what I'm trying to do here :)

My point of view is as follows:
* complex changes must be presented to other devs and discussed one by
  one;
* no change should break current 'make distcheck';
* portability issues have to be born in mind.
I'm OK with other things (new languages etc.) that don't break other's
workflows.

Cheers,
  Vladimir