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=tlR4PpFl620Hcxg9h9XiaO5lDDJTREk7HL1t0vQSjO4=;
	b=Al6s1zD+lgm+8nVltQdIktgXPOLp2y3ec6OpO0sdoqJzI9apb5yIaJKr+E4ty7AexH
	YCm5IKSGcm2W5aJfxCTGTpPuIeaDl7Ot41urUnftlSTDnEYKXFzsHeyayMZ3gW5ronER
	tcf9OmCvqfqO69DA2HVxaGxMZcDUZfnde7sQr81ACKJE3VoVuPRj7Y80expLqnXeI/SE
	BDQNMNi6CkPXXYprdkfAhqhglrXmIttWDFCKUHYb3fPjkNuccrM3ASnKhL/psgIuvvPT
	EpoRAmoza3MXDKc091vUy7fFoF7Ts19aoPXVgfzdtoy5sP/BHuteZ30OEu55X53miHFS
	92GQ==
MIME-Version:	1.0
In-Reply-To:	<CAGde_xOu96b1jxN1n2km3_OAkX9umshs9FQF+Gdjgsbw_Mt4qQ@mail.gmail.com>
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>
	<201210312340 DOT q9VNe3VW012697 AT envy DOT delorie DOT com>
	<CAC4O8c-xvCH8j2h3K3+ymO0Zgbru_JqDavqojY81iT_C=-zPrw AT mail DOT gmail DOT com>
	<CAGde_xOu96b1jxN1n2km3_OAkX9umshs9FQF+Gdjgsbw_Mt4qQ AT mail DOT gmail DOT com>
Date:	Sat, 3 Nov 2012 14:10:23 -0800
Message-ID:	<CAC4O8c8BiPJSJyvTDs337ix2e==+bLwzz3TgqD8rV+B4TPkSxw@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 Sat, Nov 3, 2012 at 6:16 AM, Svenn Are Bjerkem
<svenn DOT bjerkem AT googlemail DOT com> wrote:
> On 2 November 2012 23:49, Britton Kerin <britton DOT kerin AT gmail DOT com> wrote:
>> But as fair warning let me give an example what I think: all the how-to-use-git
>> stuff from http://wiki.geda-project.org/geda:scm should go away, as there are
>> a dozen web sites that cover that better.  Maybe just the
>> 'how-to-not-scew-up-the-repository' could stay.
>
> You have had objections to this statement already, and I'll add mine, too.
> Leave the page as it is, and add links to the pages you think replace
> the contents of geda:scm. We can then look at them and judge before
> deciding what goes away and what stays. The page is not intended to
> teach git, just give devs and dev-wannabes enough to get a local
> repository. We also need to catch-up with some loose threads from
> remote forks and clones initialized by drive-by-devs.

I think this page replaces most of it:

  http://www.kernel.org/pub/software/scm/git/docs/everyday.html

I'd also keep these sections:

  git clone git://git.geda-project.org/geda-gaf.git
  (gets them the code if thats all they want)

  git diff >name_of_patch
  (lets them submit simple fix, but need to add where to send it)

  And mention the preferred rebase policy and add the standard warning
  to not use rebase on shared repositories, or DJ could just tell them
  this when they ask for commit access.

Its not that the rest is bad information it just lards the docs and I doubt
its going to give people without any git knowledge enough comfort to do
anything besides get a copy of the code and maybe mail in a patch.

The home page also has lard:

     The gEDA project was started because of the lack of free EDA tools for
     POSIX systems with the primary purpose of advancing the state of free
     hardware or open source hardware. The suite is mainly being developed
     on the GNU/Linux platform with some development effort going into making
     sure the tools run on other platforms as well.

Users have said they find the docs painful so getting rid of anything useless
in them is worthwhile.

Britton

- Raw text -