From: Tom Geller <tom@tomgeller•com>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Procedure for non-tech contributions
Date: Sun, 2 Mar 2014 15:10:09 -0500 [thread overview]
Message-ID: <BCF42CA2-D68C-452C-9D98-E410E71B66EF@tomgeller.com> (raw)
In-Reply-To: <mailman.41250.1393785335.2207.bitcoin-development@lists.sourceforge.net>
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
next parent reply other threads:[~2014-03-02 20:30 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 ` Tom Geller [this message]
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
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=BCF42CA2-D68C-452C-9D98-E410E71B66EF@tomgeller.com \
--to=tom@tomgeller$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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