diff options
| author | Rick Wesson <rick@support-intelligence.com> | 2011-08-11 11:20:23 -0700 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2011-08-11 18:20:29 +0000 |
| commit | d376d96128f2735ac38928a6b29998d93c2bd5b9 (patch) | |
| tree | b9ee467a921ef053f09682b92d82af6a0be389e5 | |
| parent | ec360fb246a68648ac77531d3f144ce129ba448d (diff) | |
| download | pi-bitcoindev-d376d96128f2735ac38928a6b29998d93c2bd5b9.tar.gz pi-bitcoindev-d376d96128f2735ac38928a6b29998d93c2bd5b9.zip | |
Re: [Bitcoin-development] Roadmap/schedules
| -rw-r--r-- | 71/8ac9dd325a0cfee35c18164aad9cfab2f7c5e8 | 108 |
1 files changed, 108 insertions, 0 deletions
diff --git a/71/8ac9dd325a0cfee35c18164aad9cfab2f7c5e8 b/71/8ac9dd325a0cfee35c18164aad9cfab2f7c5e8 new file mode 100644 index 000000000..e2b1dbb45 --- /dev/null +++ b/71/8ac9dd325a0cfee35c18164aad9cfab2f7c5e8 @@ -0,0 +1,108 @@ +Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] + helo=mx.sourceforge.net) + by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <rick.wesson@iidf.org>) id 1QrZrp-0006CS-Oc + for bitcoin-development@lists.sourceforge.net; + Thu, 11 Aug 2011 18:20:29 +0000 +X-ACL-Warn: +Received: from mail-yx0-f175.google.com ([209.85.213.175]) + by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) + (Exim 4.76) id 1QrZro-0005AI-Ok + for bitcoin-development@lists.sourceforge.net; + Thu, 11 Aug 2011 18:20:29 +0000 +Received: by yxi19 with SMTP id 19so1914969yxi.34 + for <bitcoin-development@lists.sourceforge.net>; + Thu, 11 Aug 2011 11:20:23 -0700 (PDT) +MIME-Version: 1.0 +Received: by 10.151.156.20 with SMTP id i20mr943330ybo.53.1313086823191; Thu, + 11 Aug 2011 11:20:23 -0700 (PDT) +Received: by 10.150.138.1 with HTTP; Thu, 11 Aug 2011 11:20:23 -0700 (PDT) +In-Reply-To: <CABsx9T2pTg8YG_Q09cnAvsrxquLO-6cWr1tb=fdWtLPBEyJzng@mail.gmail.com> +References: <CABsx9T2pTg8YG_Q09cnAvsrxquLO-6cWr1tb=fdWtLPBEyJzng@mail.gmail.com> +Date: Thu, 11 Aug 2011 11:20:23 -0700 +Message-ID: <CAJ1JLtu7UXz2X25iWLKUUmK=oapj8OzGRH964JY=Ppzd8rOfTg@mail.gmail.com> +From: Rick Wesson <rick@support-intelligence.com> +To: Gavin Andresen <gavinandresen@gmail.com> +Content-Type: multipart/alternative; boundary=00151750edb0a7d3b304aa3ed9af +X-Spam-Score: 2.0 (++) +X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. + See http://spamassassin.org/tag/ for more details. + 1.0 HTML_MESSAGE BODY: HTML included in message + 1.0 AWL AWL: From: address is in the auto white-list +X-Headers-End: 1QrZro-0005AI-Ok +Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] Roadmap/schedules +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Thu, 11 Aug 2011 18:20:29 -0000 + +--00151750edb0a7d3b304aa3ed9af +Content-Type: text/plain; charset=ISO-8859-1 + +On Wed, Aug 10, 2011 at 9:29 AM, Gavin Andresen <gavinandresen@gmail.com>wrote: + +> I've been wading through the pull requests and bug lists to figure out +> a roadmap for the next few months. +> +> Here are the things on my priority list: +> +> 1. Where are we at with network health? What metrics should we be +> using? Is there work to be done? +> And meta-issue: can somebody volunteer to be the Bitcoin Network +> Health Inspector to keep track of this? +> +> +I'm already on it, leveraging bitcoinj to do the work. I've added async +capabilities to bitcoinj so that I can peer with everything that will let me +with the goal of publishing quality peer lists via the DNS. Once I can build +some metrics off the network its a matter of creating the visualizations. + +I just started on this project last week. Happy to work with others on what +a healty network looks like as well as best ways to communicate status. + +also need advise on how to not be an impolite peer. + +-rick + +--00151750edb0a7d3b304aa3ed9af +Content-Type: text/html; charset=ISO-8859-1 +Content-Transfer-Encoding: quoted-printable + +<br><br><div class=3D"gmail_quote">On Wed, Aug 10, 2011 at 9:29 AM, Gavin A= +ndresen <span dir=3D"ltr"><<a href=3D"mailto:gavinandresen@gmail.com">ga= +vinandresen@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_q= +uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e= +x;"> +I've been wading through the pull requests and bug lists to figure out<= +br> +a roadmap for the next few months.<br> +<br> +Here are the things on my priority list:<br> +<br> +1. Where are we at with network health? What metrics should we be<br> +using? Is there work to be done?<br> +And meta-issue: =A0can somebody volunteer to be the Bitcoin Network<br> +Health Inspector to keep track of this?<br> +<br></blockquote><div><br></div><div>I'm already on it, leveraging bitc= +oinj to do the work. I've added async capabilities to bitcoinj so that = +I can peer with everything that will let me with the goal of publishing qua= +lity peer lists via the DNS. Once I can build some metrics off the network = +its a matter of creating the visualizations.</div> +<div><br></div><div>I just started on this project last week. Happy to work= + with others on what a healty network looks like as well as best ways to co= +mmunicate status.</div><div><br></div><div>also need advise on how to not b= +e an impolite peer.</div> +<div><br></div><div>-rick</div><div><br></div></div> + +--00151750edb0a7d3b304aa3ed9af-- + + |