X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
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=bxUo4BdsZst7bohzkcXhnCfwEqY35I67qKiVUGPZZjQ=;
        b=U8zt8gQI2ttfpK5OI6VQmA5OroA+hat+Tu3NN3u1x+FLwi8gRj8nxPvoIv7XFs67Be
         bakBP964WOCASmh1/Df6o64R44QLJDsiwfLwuso9NTJLAhUO6ae2TnyAsYRnJlqj/Wiy
         fis09uRN+EDNoB45VZYUHDoa3Lm6sUVs2XNsq9IGFXcTlj0O6HVu1/7tL9t02Z2a97UU
         +WEKKPSRIrQgUD9T5SdQp2+0fxUBK6tFToJISurcjLU1Fuz2xSfPuSeixhlprcuDMxtf
         TFY8Q0Us/Ch+xAv7i79JKxgm7+vO01aQAfxT32bwfbKnxuGpL0eTb1Ac1v2bPNeB/bqP
         P0NA==
MIME-Version: 1.0
In-Reply-To: <B1896514-F144-41F0-9F7F-744F77319720@jump-ing.de>
References: <0EEF0A12-8BF9-435B-9CE0-ABBF2C655879 AT jump-ing DOT de>
	<201210250104 DOT q9P14cfD020621 AT envy DOT delorie DOT com>
	<B276A77F-2426-45E6-B41D-B603DB9137EA AT jump-ing DOT de>
	<5088A0E3 DOT 40106 AT icarus DOT com>
	<B1896514-F144-41F0-9F7F-744F77319720 AT jump-ing DOT de>
Date: Thu, 25 Oct 2012 23:24:56 +0200
Message-ID: <CAGde_xMrW60ahFK5jAFc_ObSkiGpJ8DApbtqt9v9oksjaEmNhQ@mail.gmail.com>
Subject: Re: [geda-user] gEDA/PCBs diversity Was: Pin hole size
From: Svenn Are Bjerkem <svenn DOT bjerkem AT googlemail DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=ISO-8859-1
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 25 October 2012 11:37, Markus Hitter <mah AT jump-ing DOT de> wrote:
>
> Am 25.10.2012 um 04:16 schrieb Stephen Williams:
>
>
>> In the Icarus Verilog world we handle the situation by using git
>> and teaching the newbies to make patches that I (or Cary) can
>> apply with a simple "git am".
>
>
> We do the same here. As DJ said, he happily accepts new committers.

How about identifying large and small programming tasks, put them on
the wiki and strike them out as they are implemented and accepted?
List some of the major flaws with geda and provide suggestions to how
they can/could be fixed. The same could be said for documentation.
Most likely somebody needs to actually use geda to be able to write
anything, but since some features are well documented while others are
a bit more hidden, it is a bit difficult to get started. Few users
will read the whole documentation to find holes they actually could
document.

Another thing, does the wiki support xmlrpc so that it would be
possible to have a vim mode like dokuvimki or vimtrac? I find that
writing in wikies is a bit of a hassle through the web interfaces.

-- 
Svenn