public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tom Geller <tom@tomgeller.com>
To: Drak <drak@zikula.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Procedure for non-tech contributions
Date: Sun, 2 Mar 2014 18:02:14 -0500	[thread overview]
Message-ID: <E2C84BD6-CA8D-41D3-8C1E-BCCF67087F7F@tomgeller.com> (raw)
In-Reply-To: <CANAnSg0a+1agr+L6a0WhUz1oB__3ZMFM8SLBaRZxQnuv6D9DyA@mail.gmail.com>

Peter Todd <pete@petertodd.org> wrote:
>> I proof-read rc1 and simply submitted my changes via pull-req:
>> 
>>     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









  reply	other threads:[~2014-03-02 23:02 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 [this message]
2014-03-03  6:04         ` Luke-Jr
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=E2C84BD6-CA8D-41D3-8C1E-BCCF67087F7F@tomgeller.com \
    --to=tom@tomgeller.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=drak@zikula.org \
    /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