public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Saïvann Carignan" <saivann@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Developer documentation on bitcoin.org
Date: Mon, 19 May 2014 18:22:48 -0400	[thread overview]
Message-ID: <537A8438.9010708@gmail.com> (raw)
In-Reply-To: <536EDBA5.2010700@gmail.com>

A quick update on the project:

More reviews and feedback on the pull request are very welcome:
https://github.com/bitcoin/bitcoin.org/pull/393

This pull request will be merged on May 24th and hopefully will be
accurate as much as possible. Reporting any inaccuracy / mistake on the
pull request is very appreciated.

Saïvann


Le 2014-05-10 22:08, Saïvann Carignan a écrit :
> A new "Developer Documentation" section should be soon merged on
> bitcoin.org .
> 
> Live Preview:
> http://bitcoindev.us.to/en/developer-documentation
> 
> GitHub Pull Request:
> https://github.com/bitcoin/bitcoin.org/pull/393
> 
> Bitcointalk Thread:
> https://bitcointalk.org/index.php?topic=511876.0
> 
> We've worked hard to come up with good quality documentation and general
> feedback has been positive. Reviews from experienced Bitcoin developers
> would now be much appreciated. You are cordially invited to help
> proofread the documentation so it can be published soon!
> 
> *Please avoid commenting on the mailing list* to not spam everyone. See
> the pull request for instructions. Comments should go on the pull
> request or bitcoin-documentation mailing list
> https://groups.google.com/forum/#!forum/bitcoin-documentation .
> 



      parent reply	other threads:[~2014-05-19 22:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11  2:08 [Bitcoin-development] Developer documentation on bitcoin.org Saïvann Carignan
2014-05-12  6:15 ` Wladimir
2014-05-19 22:22 ` Saïvann Carignan [this message]

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=537A8438.9010708@gmail.com \
    --to=saivann@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.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