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=lEm1+111p2E1GvCgeM9MoNfCJpylubbyRLogiR/gtUI=;
	b=VYoPAH6224r/k7RpfiHkYSFRkhnLeVWH+Wyvj7AhxpsxC8dB2F3AOnwphvh8xt5bfh
	yWfpKkrwrz5Thy0OGcblXR74pUy8diTm7RFTJjN8OiN+9dEapFF8Ve42tflSZfisPXv2
	5ZvrAiOVXb4oUWqPct1hCn6Xz7FrFe2vc8hU/O1UpgxELICDxbBtnJ0ddjc44+tjoHQE
	aDxyq3unCbO/MMAOMqo8L37M/uBxhTvcqJzPmwircNmK+zo6XooV2+MswxrQDM/X/a1e
	9vFHUgHVeyAt5NBxDzAzArTx/tYz/ITBYEWcIfwaGIsgT60fbGKQciLOa6duOB/KbRst
	a2Rw==
MIME-Version:	1.0
In-Reply-To:	<k6tu8g$f3n$1@ger.gmane.org>
References:	<CANqhZFxYH+Y5U1ai7ey-s+4nz6eYDM2vx3aMDb7WuigNXmi4AQ AT mail DOT gmail DOT com>
	<1511E63C-F435-44B1-9734-C7AF7AF49A92 AT sbcglobal DOT net>
	<20121030132922 DOT GY32696 AT fi DOT muni DOT cz>
	<k6tu8g$f3n$1 AT ger DOT gmane DOT org>
Date:	Fri, 2 Nov 2012 14:16:37 -0800
Message-ID:	<CAC4O8c_buDm3vo+OJrY5SjTuqU1ssV53yGWu49t5QLGg_1kyDw@mail.gmail.com>
Subject:	Re: [geda-user] The state of gEDA/gaf (Was gEDA/PCBs diversity, Was:
	Pin hole size)
From:	Britton Kerin <britton DOT kerin AT gmail DOT com>
To:	geda-user AT delorie DOT com
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 Thu, Nov 1, 2012 at 5:42 AM, Kai-Martin Knaak
<knaak AT iqo DOT uni-hannover DOT de> wrote:

>> and with devel
>> list with occasional end-user questions.
>
> There was a developers list for a long time: geda-devel AT seul DOT org
> Originally, this list was open to everyone. Over time, it developed into a
> sibling of geda-user AT seul DOT org with discussions spanning both lists. In

This always happens eventually.  Why don't we just have one list?  Separate
devel lists are usually a weird idea IMO (your essentially telling your users
to bug off and not bother you) and for gEDA they make no sense at all since
to use the beast successfully you're almost certain to have to at least write
scripts/Makefiles and learn something about the interconnecting guts anyway.

If we want separate lists they should be topical (gschem, pcb, ngspice, etc.)
but I think even this is probably bad since many question are likely to be
related to getting the pieces to talk.

Example of how not to do it: arduino forums.  About 30 of them and
they yell at you if you cross-post.

Example of how to do it: beagleboard.  One list which the devels actually read.

>> Again, as a newcomer, I find the documentation of geda to be
>> one of the weakest points.

As you or someone else pointed out the problem is more that its spread out
in 10 different spots, than that it doesn't exist.  I know its a toolbox
not an IDE etc. etc. but even how to do things in the individual tools is
spread out everywhere.  I don't think more documentation is likely to solve
this (special cases like the topo router aside).  What's really needed is
someone who wants to take responsibility for consolidating and organizing
the existing documentation.

Britton

- Raw text -