From: Mike Hearn <mike@plan99•net>
To: Tom Geller <tom@tomgeller•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Procedure for non-tech contributions
Date: Mon, 3 Mar 2014 22:18:43 +0100 [thread overview]
Message-ID: <CANEZrP0YjzUHRJfsoWeWdkOPYkTekEOKtW+sOaU110-q1b8xxg@mail.gmail.com> (raw)
In-Reply-To: <D7CC04BF-5FCE-4525-AAAB-FDE30F8FE66D@tomgeller.com>
[-- Attachment #1: Type: text/plain, Size: 2159 bytes --]
Hey Tom,
Thanks for getting involved! It's great to see someone who would like to
focus on docs.
One project I've been thinking about recently is a "Bitcoin Developer
Network" subsection of our website. Right now bitcoin.org is entirely
consumer focused. And as you noted, the wiki is undergoing some kind of
heart attack - it's not an ideal medium for professional docs anyway.
So it's too hard to learn how to work with Bitcoin as a developer, and we
could really benefit from professionally curated web content. We have a
great web dev in the form of Saivann, who recently got some sponsorship
from the Foundation to spend time on the website, so I'm hoping that if we
find people to produce the content then he can with the visual design and
we could create something really special.
If you're interested in this let me know.
On Mon, Mar 3, 2014 at 8:40 PM, Tom Geller <tom@tomgeller•com> wrote:
> On Mar 3, 2014, at 2:13 PM, Tom Geller wrote:
>
> > FYI, I made my edits to the release notes of 0.9.0rc2; the pull request
> is at https://github.com/bitcoin/bitcoin/pull/3787. I gladly welcome
> corrections as needed.
>
> It failed testing. I assume I'll get emails as others add comments; please
> contact me privately if it doesn't, and you're willing to help this n00b.
> Thanks,
>
> ---
> Tom Geller * Oberlin, Ohio * 415-317-1805
> Writer/Presenter * http://www.tomgeller.com
> articles, marketing, videos, user guides, books
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries. Built-in WAN optimization and
> the
> freedom to use Git, Perforce or both. Make the move to Perforce.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 3209 bytes --]
next prev parent reply other threads:[~2014-03-03 21:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2014-03-04 19:10 ` Tom Geller
[not found] <mailman.41250.1393785335.2207.bitcoin-development@lists.sourceforge.net>
2014-03-02 20:10 ` 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
2014-03-03 7:56 ` Wladimir
2014-03-03 9:59 ` Odinn Cyberguerrilla
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=CANEZrP0YjzUHRJfsoWeWdkOPYkTekEOKtW+sOaU110-q1b8xxg@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=tom@tomgeller$(echo .)com \
/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