Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of zikula.org
	designates 74.125.82.41 as permitted sender)
	client-ip=74.125.82.41; envelope-from=drak@zikula.org;
	helo=mail-wg0-f41.google.com; 
MIME-Version: 1.0
In-Reply-To: <20140302204029.GA21339@tilt>
References: <mailman.41250.1393785335.2207.bitcoin-development@lists.sourceforge.net>
	<BCF42CA2-D68C-452C-9D98-E410E71B66EF@tomgeller.com>
	<20140302204029.GA21339@tilt>
From: Drak <drak@zikula.org>
Date: Sun, 2 Mar 2014 22:11:25 +0000
Message-ID: <CANAnSg0a+1agr+L6a0WhUz1oB__3ZMFM8SLBaRZxQnuv6D9DyA@mail.gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=047d7bf0c106ef7c6a04f3a6f4b1
Cc: Tom Geller <tom@tomgeller.com>,
	Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Procedure for non-tech contributions
Precedence: list

--047d7bf0c106ef7c6a04f3a6f4b1
Content-Type: text/plain; charset=UTF-8

On 2 March 2014 20:40, Peter Todd <pete@petertodd.org> wrote:

> I proof-read rc1 and simply submitted my changes via pull-req:
>
>     https://github.com/bitcoin/bitcoin/pull/3642
>
> I'd say to encourage that method. If someone doesn't know how to use
> git, yet still wants to proof-read, just send us a text-file with all
> your corrections applied. We've got the tools to diff those changes
> ourselves; no fancy software is required.


Actually, this is unnecessary since github allows editing of files directly
on the site and the it will submit as a pull request. You can even update
by visiting your fork (it creates this automatically and a topic branch)
and make more edits and it will add to your PR. There is basically no
barrier for non techy people to contribute.

Drak

--047d7bf0c106ef7c6a04f3a6f4b1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 2=
 March 2014 20:40, Peter Todd <span dir=3D"ltr">&lt;<a href=3D"mailto:pete@=
petertodd.org" target=3D"_blank">pete@petertodd.org</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">

<div class=3D"">I proof-read rc1 and simply submitted my changes via pull-r=
eq:<br></div>
<br>
=C2=A0 =C2=A0 <a href=3D"https://github.com/bitcoin/bitcoin/pull/3642" targ=
et=3D"_blank">https://github.com/bitcoin/bitcoin/pull/3642</a><br>
<br>
I&#39;d say to encourage that method. If someone doesn&#39;t know how to us=
e<br>
git, yet still wants to proof-read, just send us a text-file with all<br>
your corrections applied. We&#39;ve got the tools to diff those changes<br>
ourselves; no fancy software is required.</blockquote><div><br></div><div>A=
ctually, this is unnecessary since github allows editing of files directly =
on the site and the it will submit as a pull request. You can even update b=
y visiting your fork (it creates this automatically and a topic branch) and=
 make more edits and it will add to your PR. There is basically no barrier =
for non techy people to contribute.</div>

<div><br></div><div>Drak=C2=A0</div></div></div></div>

--047d7bf0c106ef7c6a04f3a6f4b1--