Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <pete@petertodd.org>) id 1WKDCk-0004eU-FR
	for bitcoin-development@lists.sourceforge.net;
	Sun, 02 Mar 2014 20:41:46 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.149.95 as permitted sender)
	client-ip=62.13.149.95; envelope-from=pete@petertodd.org;
	helo=outmail149095.authsmtp.com; 
Received: from outmail149095.authsmtp.com ([62.13.149.95])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1WKDCj-00060l-6a for bitcoin-development@lists.sourceforge.net;
	Sun, 02 Mar 2014 20:41:46 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
	by punt15.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s22Kfd3X078190;
	Sun, 2 Mar 2014 20:41:39 GMT
Received: from tilt ([65.48.240.32]) (authenticated bits=128)
	by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s22KfJ28088236
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
	Sun, 2 Mar 2014 20:41:31 GMT
Date: Sun, 2 Mar 2014 15:40:29 -0500
From: Peter Todd <pete@petertodd.org>
To: Tom Geller <tom@tomgeller.com>
Message-ID: <20140302204029.GA21339@tilt>
References: <mailman.41250.1393785335.2207.bitcoin-development@lists.sourceforge.net>
	<BCF42CA2-D68C-452C-9D98-E410E71B66EF@tomgeller.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV"
Content-Disposition: inline
In-Reply-To: <BCF42CA2-D68C-452C-9D98-E410E71B66EF@tomgeller.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 0d5adca4-a24b-11e3-b802-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
	http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
	aAdMdgAUFVQGAgsB AmIbWVReVFx7Wms7 bQ9PaQ1DYE5OQQZo
	T01BRU1TWkZqA2dX fBwWUhF6dQZANnZ3 Z0EsXiReDRApJEJg
	E0xQR3AHZDJjdTIX UEJFdwNWdQpKLx5A PgF4GhFYa3VsFCMk
	FAgyOXU9MCtSLCNN RwwLMWdaeVwMFTMw WgoPVTsoBwUDQCN2
	MxEtKhYXG0ANKEQ4 LEcgXlQDWwA8
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 65.48.240.32/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
	anti-virus system.
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	-0.0 SPF_PASS               SPF: sender matches SPF record
X-Headers-End: 1WKDCj-00060l-6a
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Procedure for non-tech contributions
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sun, 02 Mar 2014 20:41:46 -0000


--HcAYCG3uE/tztfnV
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Mar 02, 2014 at 03:10:09PM -0500, Tom Geller wrote:
> Hey, folks. Sorry if this is documented somewhere -- if so, just point me=
 at it. I couldn't find it, though.
>=20
> I'm a (non-developer) writer with experience in open-source communities, =
and I'd like to contribute with writing/editing/marketing. What's the proce=
dure? Is there someone in charge of that area?
>=20
> Two examples:
>=20
> 1) Gavin recently asked for proofreading of 0.9.0rc2, but it was unclear =
how to send the changes. (There are many possibilities, some better than ot=
hers. Git? Google Docs with revisioning? Microsoft Word with Track Changes?=
 The Bitcoin wiki?)

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.


> 2) The page at https://en.bitcoin.it/wiki/BitcoinPayment says that "the w=
iki receiving wallet (for the wiki itself) is also MtGox". Umm, I rather do=
ubt that. :-P But I'm not sure what the current info is, or whom to alert.

MtGox does host the bitcoin wiki, so yes, the funds probably do go to a
wallet held by MtGox in some fashion.

--=20
'peter'[:-1]@petertodd.org
000000000000000f9102d27cfd61ea9e8bb324593593ca3ce6ba53153ff251b3

--HcAYCG3uE/tztfnV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBCAAGBQJTE5c9AAoJECSBQD2l8JH7eGAIAJu9Iwsx9YXehGNKK5EJ9YiZ
CKpJolDLNI5sgO1noQrVEx5Fxe5htjopCGQL22sGFP/1vRtRFUAPqJMog6j2aSRO
leiaCTuXWbHqas0ExOZ4NT0qw//D8QqDEFUcMYGDRqbwgpxsP0oPCEBtk1ee13PQ
AnSjG7Z6n1jvanFgoN7zemwSyUMxTe6TuS+5ck+ulIP4io22TFVcFk0cnetAVx+L
7e8rdG6sSuNzHAKue32YBmZy/HnijCxGgmqK/mqRSXtipTXCpEp/qUJUyG7qDBdV
0+3XcXWIIyWx5kEt6bAj/UA3UTrLJm9GmcLaxa659cDA3pBcgC92tEZX3MzSVUA=
=1e6Z
-----END PGP SIGNATURE-----

--HcAYCG3uE/tztfnV--