public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tom Geller <tom@tomgeller.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Procedure for non-tech contributions
Date: Tue, 4 Mar 2014 14:10:08 -0500	[thread overview]
Message-ID: <05F49C13-FDBC-47D9-BEA6-DD3BA0CA5179@tomgeller.com> (raw)
In-Reply-To: <CANEZrP0YjzUHRJfsoWeWdkOPYkTekEOKtW+sOaU110-q1b8xxg@mail.gmail.com>

I'm taking this private. Thanks again to all for your help getting me involved!

---
         Tom Geller  *  Oberlin, Ohio  *  415-317-1805
          Writer/Presenter * http://www.tomgeller.com
        articles, marketing, videos, user guides, books





On Mar 3, 2014, at 4:18 PM, Mike Hearn wrote:

> 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.

[snip remainder of thread]


  reply	other threads:[~2014-03-04 19:10 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 ` [Bitcoin-development] Procedure for non-tech contributions 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 [this message]
     [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=05F49C13-FDBC-47D9-BEA6-DD3BA0CA5179@tomgeller.com \
    --to=tom@tomgeller.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=mike@plan99.net \
    /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