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 ) 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 In-Reply-To: Date: Sun, 2 Mar 2014 18:02:14 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20140302204029.GA21339@tilt> To: Drak 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Mar 2014 23:02:28 -0000 Peter Todd 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