1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <saivann@gmail.com>) id 1UgnPU-0008S1-AM
for bitcoin-development@lists.sourceforge.net;
Mon, 27 May 2013 02:43:44 +0000
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;
Received: from mail-ie0-f182.google.com ([209.85.223.182])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UgnPS-0000sh-5a
for bitcoin-development@lists.sourceforge.net;
Mon, 27 May 2013 02:43:44 +0000
Received: by mail-ie0-f182.google.com with SMTP id a14so17141224iee.41
for <bitcoin-development@lists.sourceforge.net>;
Sun, 26 May 2013 19:43:36 -0700 (PDT)
X-Received: by 10.50.67.10 with SMTP id j10mr3969631igt.70.1369622616877;
Sun, 26 May 2013 19:43:36 -0700 (PDT)
Received: from [192.168.1.100] (ip-50-21-136-249.dsl.netrevolution.com.
[50.21.136.249])
by mx.google.com with ESMTPSA id ji5sm15638133igb.0.2013.05.26.19.43.35
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Sun, 26 May 2013 19:43:35 -0700 (PDT)
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>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/alternative;
boundary="------------080205060802070304050704"
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(saivann[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UgnPS-0000sh-5a
Subject: [Bitcoin-development] Handling alerts & communication on bitcoin.org
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: Mon, 27 May 2013 02:43:44 -0000
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ïvann<br>
</div>
</div>
</body>
</html>
--------------080205060802070304050704--
|
