From: Saïvann <saivann@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Handling alerts & communication on bitcoin.org
Date: Sun, 26 May 2013 22:43:32 -0400 [thread overview]
Message-ID: <51A2C854.2050100@gmail.com> (raw)
In-Reply-To: <CA+s+GJD0xoudWUiko4epSXYz+ytU0SvrdAKR-sAnh89rUhKLkw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1207 bytes --]
next prev parent reply other threads:[~2013-05-27 2:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 5:46 [Bitcoin-development] (no subject) Zooko Wilcox-OHearn
2013-05-25 8:09 ` Wladimir
2013-05-27 2:43 ` Saïvann [this message]
2013-05-25 8:25 ` Melvin Carvalho
2013-05-25 8:53 ` Luke-Jr
2013-05-25 9:23 ` Melvin Carvalho
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=51A2C854.2050100@gmail.com \
--to=saivann@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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