Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.182 as permitted sender)
	client-ip=209.85.223.182; envelope-from=saivann@gmail.com;
	helo=mail-ie0-f182.google.com; 
Message-ID: <51A2C854.2050100@gmail.com>
Date: Sun, 26 May 2013 22:43:32 -0400
From: =?ISO-8859-1?Q?Sa=EFvann?= <saivann@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CAM_a8Jwo_7NJJoaKYUYo6T7U8AsDfT5=MZSXjmdYU4330OHNmw@mail.gmail.com>
	<CA+s+GJD0xoudWUiko4epSXYz+ytU0SvrdAKR-sAnh89rUhKLkw@mail.gmail.com>
In-Reply-To: <CA+s+GJD0xoudWUiko4epSXYz+ytU0SvrdAKR-sAnh89rUhKLkw@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------080205060802070304050704"
Subject: [Bitcoin-development] Handling alerts & communication on bitcoin.org
Precedence: list

This is a multi-part message in MIME format.
--------------080205060802070304050704
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Hi,

There is currently 5 alerts pages on bitcoin.org concerning past network
events (vulnerabilities, hard fork, etc.). Those don't have any
visibility and cannot be listed or followed easily.

I've created a setup to improve this and allow developers to easily
communicate about any kind of network event worth mentionning. Code,
screenshot, live demo, instructions and details are in the pull request :
https://github.com/bitcoin/bitcoin.org/pull/194

Any comment is welcome. And since it is ultimately a tool for
developers, only you can define if it makes sense to merge it. Or if you
would like it to be done differently.

Best,

Saīvann

--------------080205060802070304050704
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi,<br>
      <br>
      There is currently 5 alerts pages on bitcoin.org concerning past
      network events (vulnerabilities, hard fork, etc.). Those don't
      have any visibility and cannot be listed or followed easily.<br>
      <br>
      I've created a setup to improve this and allow developers to
      easily communicate about any kind of network event worth
      mentionning. Code, screenshot, live demo, instructions and details
      are in the pull request :<br>
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      <a href="https://github.com/bitcoin/bitcoin.org/pull/194">https://github.com/bitcoin/bitcoin.org/pull/194</a><br>
      <br>
      Any comment is welcome. And since it is ultimately a tool for
      developers, only you can define if it makes sense to merge it. Or
      if you would like it to be done differently.<br>
      <br>
      Best,<br>
      <br>
      <div class="moz-signature">Sa&iuml;vann<br>
      </div>
    </div>
  </body>
</html>

--------------080205060802070304050704--