X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Message-ID:	<20130115013756.9917.qmail@stuge.se>
Date:	Tue, 15 Jan 2013 02:37:56 +0100
From:	Peter Stuge <peter AT stuge DOT se>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] geda-skeleton-project: Lowering the cost of a
	starting a gEDA project
Mail-Followup-To:	geda-user AT delorie DOT com
References:	<87wqvhd4tw DOT fsf AT gmail DOT com> <kd21ao$j6j$1 AT ger DOT gmane DOT org>
MIME-Version:	1.0
In-Reply-To:	<kd21ao$j6j$1@ger.gmane.org>
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

Kai-Martin Knaak wrote:
> My take on the same subject can be found on gedasymbols.org :
> http://www.gedasymbols.org/user/kai_martin_knaak/new_geda_project.sh
> 
> This is a script I actually use to start geda projects. So it provides a  
> skeleton with a few more bones:
>   * an empty schematic file with a project name, date and developer filled 
> out in the title block.
>   * an empty layout file with my preferred layer stack.
>   * a doc directory with a lyx document that contains a number of standard 
> sections for documentation
>   * a print directory for rendered PDFs and print scripts. The print 
> scripts may be modified to match the needs of the specific project.
>   * a gerber directory for gerbers with a script that prepares the gerbers 
> from the layout file.
>   * a bom directory for the bill of materials and whatever additional 
> information the assembler needs. 
>   * a directory for files related to the enclosing. 3D CAD drawings, etc.
>   * a directory for old versions of the project

This layout is really good in many ways.

What approach does orange (the gEDA project manager) take?

Do we want to make it work with something like your layout?

Reading about your layout I had the thought that it would be quite
neat to use a git bundle as native project manager file format. :)


> >   * a Makefile for performing some common tasks (e.g. generating
> >     tragesym symbols, updating the pcb layout, and exporting gerbers)
> 
> I found, Makefiles add to the barriers perceived by newbies. Even simple 
> Makefiles like yours look like incomprehensible magic spells to the 
> uninitiated. So I stick with the less elegant bash scripts.

This is a good point. I agree with the observation, but I tend to
prefer using more powerful tools and documenting them, rather than
dumbing down the tools for simplicity's sake.


> Is there any high profile open hardware project that endorses geda?

I don't know what you mean by high profile, but Kevin who makes
SIMtrace[1] switched from using KiCAD to gEDA. :)


//Peter

[1] http://simtrace.osmocom.org/

- Raw text -