From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Cc: Tom Geller <tom@tomgeller.com>
Subject: Re: [Bitcoin-development] Procedure for non-tech contributions
Date: Mon, 3 Mar 2014 06:04:44 +0000 [thread overview]
Message-ID: <201403030604.46324.luke@dashjr.org> (raw)
In-Reply-To: <E2C84BD6-CA8D-41D3-8C1E-BCCF67087F7F@tomgeller.com>
On Sunday, March 02, 2014 11:02:14 PM Tom Geller wrote:
> 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. :(
We've been working on moving the wiki to new hosting, but it isn't a very high
priority (at least for MtGox). PM SomeoneWeird on IRC, as he is currently
handling manually approving new accounts for editing.
Luke
next prev parent reply other threads:[~2014-03-03 6:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.41250.1393785335.2207.bitcoin-development@lists.sourceforge.net>
2014-03-02 20:10 ` [Bitcoin-development] Procedure for non-tech contributions Tom Geller
2014-03-02 20:40 ` Peter Todd
2014-03-02 22:11 ` Drak
2014-03-02 23:02 ` Tom Geller
2014-03-03 6:04 ` Luke-Jr [this message]
2014-03-03 7:56 ` Wladimir
2014-03-03 9:59 ` Odinn Cyberguerrilla
[not found] <mailman.41744.1393833438.2178.bitcoin-development@lists.sourceforge.net>
2014-03-03 18:46 ` Tom Geller
2014-03-03 19:13 ` Tom Geller
2014-03-03 19:40 ` Tom Geller
2014-03-03 21:18 ` Mike Hearn
2014-03-04 19:10 ` Tom Geller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201403030604.46324.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=tom@tomgeller.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox