1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tom@tomgeller.com>) id 1WKD25-0005Ek-Ks
for bitcoin-development@lists.sourceforge.net;
Sun, 02 Mar 2014 20:30:45 +0000
X-ACL-Warn:
Received: from mail6.webfaction.com ([74.55.86.74] helo=smtp.webfaction.com)
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1WKD24-0005iu-Eh for bitcoin-development@lists.sourceforge.net;
Sun, 02 Mar 2014 20:30:45 +0000
Received: from [192.168.2.66] (ip-211-223.oberlin.net [208.66.211.223])
by smtp.webfaction.com (Postfix) with ESMTP id 73A0D225DE73
for <bitcoin-development@lists.sourceforge.net>;
Sun, 2 Mar 2014 20:10:08 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1283)
From: Tom Geller <tom@tomgeller.com>
In-Reply-To: <mailman.41250.1393785335.2207.bitcoin-development@lists.sourceforge.net>
Date: Sun, 2 Mar 2014 15:10:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BCF42CA2-D68C-452C-9D98-E410E71B66EF@tomgeller.com>
References: <mailman.41250.1393785335.2207.bitcoin-development@lists.sourceforge.net>
To: bitcoin-development@lists.sourceforge.net
X-Mailer: Apple Mail (2.1283)
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1WKD24-0005iu-Eh
Subject: [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:30:45 -0000
Hey, folks. Sorry if this is documented somewhere -- if so, just point =
me at it. I couldn't find it, though.
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 =
procedure? Is there someone in charge of that area?
Two examples:
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 =
others. Git? Google Docs with revisioning? Microsoft Word with Track =
Changes? The Bitcoin wiki?)
2) The page at https://en.bitcoin.it/wiki/BitcoinPayment says that "the =
wiki receiving wallet (for the wiki itself) is also MtGox". Umm, I =
rather doubt that. :-P But I'm not sure what the current info is, or =
whom to alert.
Off-list replies welcome. Thanks,
---
Tom Geller * Oberlin, Ohio * 415-317-1805
Writer/Presenter * http://www.tomgeller.com
articles, marketing, videos, user guides, books
|
