summaryrefslogtreecommitdiff
path: root/7c/db61b9594dc9d1e18a5d0cb3977367d1cdacca
blob: d7a96b9c9e15799327b41e05a25538365dbfa44d (plain)
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
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <tom@tomgeller.com>) id 1WKFOu-0001VM-LS
	for bitcoin-development@lists.sourceforge.net;
	Sun, 02 Mar 2014 23:02:28 +0000
X-ACL-Warn: 
Received: from mail6.webfaction.com ([74.55.86.74] helo=smtp.webfaction.com)
	by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1WKFOt-00039L-He for bitcoin-development@lists.sourceforge.net;
	Sun, 02 Mar 2014 23:02:28 +0000
Received: from [192.168.2.66] (ip-211-223.oberlin.net [208.66.211.223])
	by smtp.webfaction.com (Postfix) with ESMTP id ADA63225E08E;
	Sun,  2 Mar 2014 23:02:15 +0000 (UTC)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Tom Geller <tom@tomgeller.com>
In-Reply-To: <CANAnSg0a+1agr+L6a0WhUz1oB__3ZMFM8SLBaRZxQnuv6D9DyA@mail.gmail.com>
Date: Sun, 2 Mar 2014 18:02:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2C84BD6-CA8D-41D3-8C1E-BCCF67087F7F@tomgeller.com>
References: <mailman.41250.1393785335.2207.bitcoin-development@lists.sourceforge.net>
	<BCF42CA2-D68C-452C-9D98-E410E71B66EF@tomgeller.com>
	<20140302204029.GA21339@tilt>
	<CANAnSg0a+1agr+L6a0WhUz1oB__3ZMFM8SLBaRZxQnuv6D9DyA@mail.gmail.com>
To: Drak <drak@zikula.org>
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: 1WKFOt-00039L-He
Cc: Bitcoin Dev <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 23:02:28 -0000

Peter Todd <pete@petertodd.org> wrote:
>> I proof-read rc1 and simply submitted my changes via pull-req:
>>=20
>>     https://github.com/bitcoin/bitcoin/pull/3642

Drak responded:
> 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.

Ooo, I like this. I *can* use git, but would love to be able to avoid it =
-- as would most non-technical contributors.

Anyway, this particular solution doesn't appear to be possible in this =
case, as the file isn't at =
https://github.com/bitcoin/bitcoin/tree/0.9.0/doc/release-notes , and I =
don't believe I could copy it to the repository without going the whole =
git route. Suggestions welcome, here or privately.

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

The foolishness of sending a payment to a Mt. Gox-held wallet -- which =
is required to edit the wiki -- strikes me as a pressing issue. If I =
understand it correctly, this is a hard blocker that'll stop *all* new =
contributors. Further, I registered for the wiki and never got my =
confirmation email. Methinks the whole thing is broken. :(

Again, please to redirect me if this is inappropriate for this list. =
(I'm new here.) Cheers,

---
          Tom Geller  *  Oberlin, Ohio  *  415-317-1805
           Writer/Presenter * http://www.tomgeller.com
         articles, marketing, videos, user guides, books