summaryrefslogtreecommitdiff
path: root/3a/c5d47d657a6c5439be8204558337280993d85e
blob: 5cde74b6a7b9ddd56a435afb5424ebec8f5ab163 (plain)
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
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
Return-Path: <slashene@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 8B4EB8A8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 21 Aug 2015 05:11:12 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-la0-f50.google.com (mail-la0-f50.google.com
	[209.85.215.50])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C22AA110
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 21 Aug 2015 05:11:11 +0000 (UTC)
Received: by lalv9 with SMTP id v9so34776235lal.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 20 Aug 2015 22:11:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:from:date:message-id
	:subject:to:cc:content-type;
	bh=9R06/Wpwa2xfN0VJOr+Fopq+YvoT2NQQkF0914v/tQM=;
	b=Y3mC+sC2mbhiTIRcZ8noIbUWmt/5kRknCD5TFcdm1HMCzEItJbsPJmy4Aqt/ErYdQP
	Z14frFoZ0UEEmhB1/zfjwHZAhgm0L1vB7Y1lgl/fKfEI1xfxweQWJ1ko59FBLz17U4kO
	xGfZtWi+611tqVE50BIh07NOyh+/MoO2H81EOiL3piGMtOw0WRfSJd79TMPnBAYlBdFm
	AYuCgoqPmB5vqSJS8k24ImzpnYjhEk4TX0/dR5/dcOzpPoy2N7e7Hs0grHF1LNAAOGT4
	jm+KEiT0lKHSO+uvNpyzuZH8Q+lUrDINpLX5C/GBIfKxMg63kdOlLKLMLrmVk16qlBfH
	I9bw==
X-Received: by 10.112.11.233 with SMTP id t9mr6179027lbb.104.1440133870157;
	Thu, 20 Aug 2015 22:11:10 -0700 (PDT)
MIME-Version: 1.0
Sender: slashene@gmail.com
Received: by 10.25.142.15 with HTTP; Thu, 20 Aug 2015 22:10:50 -0700 (PDT)
In-Reply-To: <CAAS2fgR4bsJtC99-fK1L+FsQT7vOfOpz9FOVqvAnqbpkaRJHLQ@mail.gmail.com>
References: <CA+1nnrk1EWd7rhwj91p1rqgGVFgOT4UYq=+Nmq41sHJYmy7YYA@mail.gmail.com>
	<CAAS2fgR4bsJtC99-fK1L+FsQT7vOfOpz9FOVqvAnqbpkaRJHLQ@mail.gmail.com>
From: Nicolas Dorier <nicolas.dorier@gmail.com>
Date: Fri, 21 Aug 2015 14:10:50 +0900
X-Google-Sender-Auth: JRI25CTJvJq_6neDxA5ux4G_7vs
Message-ID: <CA+1nnr=35TPycf3=0xn0gbkx=KfEZ36uY3nWEdK986n=dftSHA@mail.gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c3b9aac2851c051dcb4bb0
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Core Devs : can you share your thoughts about all
 BIPs on this website ?
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Aug 2015 05:11:12 -0000

--001a11c3b9aac2851c051dcb4bb0
Content-Type: text/plain; charset=UTF-8

Decision making is not the goal of this site, it is only a way to see
various pros and cons of various devs on various proposals in a single
place.
This is for the community to have a coherent view about what you are
talking about now spread into reddit/mailing/forums.

If you did not analyzed a proposal yet, you don't have to fill out your
opinion veto or approval.
It is only to show what you would you "approve" and what you would "veto",
after your analysis.
Then point out all the discussions in the opinion section that lead you to
your conclusion.

You can change edit your position as you progress into your analysis and as
new BIP get redacted.
I'm eager to include the new proposals.





On Fri, Aug 21, 2015 at 1:45 PM, Gregory Maxwell <gmaxwell@gmail.com> wrote:

> On Wed, Aug 19, 2015 at 4:57 AM, Nicolas Dorier via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> > I created a small website which show a chart of your approvals about
> various
> > BIPs (which you must fill by yourself with a signed pgp message)
> > For each BIP, you can fill if you approve or not, and give comments.
> (HTML
> > accepted, so you can link stuff you your posts)
> > It would help the community a lot, so I hope you will do it !
> > I'm open to add other important devs, big miners, or other proposal that
> I
> > missed.
>
>
> I think this is a bit well, sad, at the moment--  a basic principle in
> sound decision making is that one should try to withhold judgement
> until after the analysis and options are laid out to avoid prematurely
> laying down "battle lines" which then they're socially and politically
> committed to a particular answer.
>
>
> There are several other BIPs in the works right now that aren't out
> there yet, as well (as presumably) new insight from the workshop. It
> would be a shame if these things would be for naught because of being
> decided prematurely.
>

--001a11c3b9aac2851c051dcb4bb0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Decision making is not the goal of this site, it is o=
nly a way to see various pros and cons of various devs on various proposals=
 in a single place.</div><div>This is for the community to have a coherent =
view about what you are talking about now spread into reddit/mailing/forums=
.</div><div><br></div>If you did not analyzed a proposal yet, you don&#39;t=
 have to fill out your opinion veto or approval.<div>It is only to show wha=
t you would you &quot;approve&quot; and what you would &quot;veto&quot;, af=
ter your analysis.</div><div>Then point out all the discussions in the opin=
ion section that lead you to your conclusion.</div><div><br></div><div>You =
can change edit your position as you progress into your analysis and as new=
 BIP get redacted.</div><div>I&#39;m eager to include the new proposals.<br=
></div><div><br></div><div><br></div><div><br></div><div><br></div></div><d=
iv class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Aug 21, 201=
5 at 1:45 PM, Gregory Maxwell <span dir=3D"ltr">&lt;<a href=3D"mailto:gmaxw=
ell@gmail.com" target=3D"_blank">gmaxwell@gmail.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><span class=3D"">On Wed, Aug 19, 2015 at 4=
:57 AM, Nicolas Dorier via bitcoin-dev<br>
&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@li=
sts.linuxfoundation.org</a>&gt; wrote:<br>
&gt; I created a small website which show a chart of your approvals about v=
arious<br>
&gt; BIPs (which you must fill by yourself with a signed pgp message)<br>
&gt; For each BIP, you can fill if you approve or not, and give comments. (=
HTML<br>
&gt; accepted, so you can link stuff you your posts)<br>
&gt; It would help the community a lot, so I hope you will do it !<br>
&gt; I&#39;m open to add other important devs, big miners, or other proposa=
l that I<br>
&gt; missed.<br>
<br>
<br>
</span>I think this is a bit well, sad, at the moment--=C2=A0 a basic princ=
iple in<br>
sound decision making is that one should try to withhold judgement<br>
until after the analysis and options are laid out to avoid prematurely<br>
laying down &quot;battle lines&quot; which then they&#39;re socially and po=
litically<br>
committed to a particular answer.<br>
<br>
<br>
There are several other BIPs in the works right now that aren&#39;t out<br>
there yet, as well (as presumably) new insight from the workshop. It<br>
would be a shame if these things would be for naught because of being<br>
decided prematurely.<br>
</blockquote></div><br></div>

--001a11c3b9aac2851c051dcb4bb0--