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
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
|
Return-Path: <btcdrak@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 1B823BE6
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Mar 2016 09:42:39 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com
[209.85.215.52])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D4B17176
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Mar 2016 09:42:37 +0000 (UTC)
Received: by mail-lf0-f52.google.com with SMTP id d82so14614646lfe.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Mar 2016 02:42:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=i8THl5t8Kr6tOpBhNI8KXuvhWnKnU/NbwUrGqaFxMnk=;
b=AMmDeug8TrhVlQONC/d4ctkLSSXXrd9HQ6PzK6iDb7eUltqPu+DuTjPPW04JbmFIai
gGeEUIrTC3ORY5B7AwWJEmFC7DnyvaN4Kq+DdMFrCf45cUP6Wgj4sELWA4m97eyi2EyO
74rRm5deJ1baXmEFOK/isHMM249NeHGCdDPs//m+8uynLSMigAKg07xuXMEfigq10Rpr
5F+o559Qq2KD9GhpWd5025sbTp4OlCeE1AvN3PPTMZ9w3OxKmkortnuTI9mvSuXJPtYR
x/EIVqba32lZ4ju56B6m/b1jOZel84uEYh8vBFAxXJ2zt94i5zfjgyp7anDhURCgXwPl
v+Vg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=i8THl5t8Kr6tOpBhNI8KXuvhWnKnU/NbwUrGqaFxMnk=;
b=e17xl4THhQI0a6/gt/NSslAtKL2l2o7Kaq3O8L7YYs9+QbQbITfxOto5wEBjXgKeo8
A6EuZDpuoO8UNMK9QF0NXnTEX8KjlnALbHM65jHLSXDkDR/blHPOZss5vCC+E8rXXIRS
FGxmKvzZAjW50Okd5EcQeAN1M+9rKLhkiyvcHnEvOjvtLzngYd+dNNIaGWrTO4Mkssif
+y5F0z+B7sxKtYN5TaEq8aYJLlptXO8RGBMgWOFLyTcrkDDjXEwtfz4sqcX3MJ/zRebI
y2vyULGlWYLG7Ve3f+nhcF6haO5FmO+454uLCJeYget7Oy7roNwPXsY0ewy3Jp2qtTNt
oi3A==
X-Gm-Message-State: AD7BkJKf3pnf+Hdl0vOAULUwg/GVCZ3qLRSQsrM8N7/W30qbyAjTeFRUw2P6X9HDNK33gVOnJEdJDMQqWOOc9A==
X-Received: by 10.25.213.196 with SMTP id m187mr5486346lfg.67.1458294156163;
Fri, 18 Mar 2016 02:42:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.82.203 with HTTP; Fri, 18 Mar 2016 02:42:16 -0700 (PDT)
In-Reply-To: <201603162224.32315.luke@dashjr.org>
References: <201603081904.28687.luke@dashjr.org>
<CADJgMzt1BUHo9_tVJF-LG_kkGdR88NVeqXaz9itLN21=R763Xw@mail.gmail.com>
<201603162224.32315.luke@dashjr.org>
From: Btc Drak <btcdrak@gmail.com>
Date: Fri, 18 Mar 2016 09:42:16 +0000
Message-ID: <CADJgMzsc1znp2tXxHa+LFmeZUnHxEcD+rfexg=5rG1T4=fN07A@mail.gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=001a11420a5627ff9e052e4f9159
X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HK_RANDOM_ENVFROM,
HK_RANDOM_FROM,
HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Fri, 18 Mar 2016 20:38:56 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 2 promotion to Final
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, 18 Mar 2016 09:42:39 -0000
--001a11420a5627ff9e052e4f9159
Content-Type: text/plain; charset=UTF-8
On Wed, Mar 16, 2016 at 10:24 PM, Luke Dashjr <luke@dashjr.org> wrote:
> BIP Comments are not a part of the BIP itself, merely post-completion notes
> from various external parties. So having them external does not make the
> BIP
> any less self-contained. Right now, this information takes the form of
> reddit/forum comments, IRC chats, etc.
>
BIP2 does not state the comments section is where discussion happens for
the BIP, but for a sort of final summary.
> It is important that the forum for comments have a low barrier of use. The
> Bitcoin Wiki requires only a request for editing privileges, whereas GitHub
> wiki would require reading and agreeing to a lengthy Terms of Service
> contract.
>
Seems weak, it's much easier to sign up for a Github account and most have
one already. It's certainly easier than either paying to get edit
privileges on the Bitcoin Wiki find someone to convince you're genuine an
obscure IRC channel.
> In terms of staleness, the Wiki has been shown to stand the test of time,
> and
> is frankly less likely to move than the GitHub repository.
>
> The BIP process originated on the Wiki, and was only moved to GitHub
> because
> stronger moderation was needed (eg, to prevent random other people from
> editing someone else's BIP; number self-assignments; etc). Such moderation
> is
> not only unnecessary for BIP Comments, but would be an outright nuisance.
>
I'm not sure that is the reason why, but in any case, Github is a more
sensible place because of the collaborative features which is why they
became the centre of OSS software development for hundreds of thousands of
projects.
> I hope this addresses all your concerns and we can move forward with BIP 2
> unmodified?
>
I am sorry but it has not. I still strongly object to using the Bitcoin
Wiki or any external source source for the commentary part of BIP2. I
believe it should be done on using the Wiki feature at bitcoin/bips. If
that is not acceptable, then I would suggest a separate page in the bip
assets folder, called bip<nnnn>/comments.md. On a side note, more complex
reference implementation code should be stored in that folder too.
> (On another note, I wonder if we should recommend non-reference
> implementation
> lists/links be moved to BIP Comments rather than constantly revising the
> BIPs
> with them...)
>
Certainly those could be on the comments page.
--001a11420a5627ff9e052e4f9159
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Mar 16, 2016 at 10:24 PM, Luke Dashjr <span dir=3D"ltr"><<a href=3D"=
mailto:luke@dashjr.org" target=3D"_blank">luke@dashjr.org</a>></span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">BIP Comments are not a part of the B=
IP itself, merely post-completion notes<br>
from various external parties. So having them external does not make the BI=
P<br>
any less self-contained. Right now, this information takes the form of<br>
reddit/forum comments, IRC chats, etc.<br></blockquote><div><br></div><div>=
BIP2 does not state the comments section is where discussion happens for th=
e BIP, but for a sort of final summary.</div><div>=C2=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
It is important that the forum for comments have a low barrier of use. The<=
br>
Bitcoin Wiki requires only a request for editing privileges, whereas GitHub=
<br>
wiki would require reading and agreeing to a lengthy Terms of Service<br>
contract.<br></blockquote><div><br></div><div>Seems weak, it's much eas=
ier to sign up for a Github account and most have one already. It's cer=
tainly easier than either paying to get edit privileges on the Bitcoin Wiki=
find someone to convince you're genuine an obscure IRC channel.</div><=
div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
In terms of staleness, the Wiki has been shown to stand the test of time, a=
nd<br>
is frankly less likely to move than the GitHub repository.<br>
<br>
The BIP process originated on the Wiki, and was only moved to GitHub becaus=
e<br>
stronger moderation was needed (eg, to prevent random other people from<br>
editing someone else's BIP; number self-assignments; etc). Such moderat=
ion is<br>
not only unnecessary for BIP Comments, but would be an outright nuisance.<b=
r></blockquote><div><br></div><div>I'm not sure that is the reason why,=
but in any case, Github is a more sensible place because of the collaborat=
ive features which is why they became the centre of OSS software developmen=
t for hundreds of thousands of projects.</div><div>=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">
I hope this addresses all your concerns and we can move forward with BIP 2<=
br>
unmodified?<br></blockquote><div><br></div><div>I am sorry but it has not. =
I still strongly object to using the Bitcoin Wiki or any external source so=
urce for the commentary part of BIP2. I believe it should be done on using =
the Wiki feature at bitcoin/bips. If that is not acceptable, then I would s=
uggest a separate page in the bip assets folder, called bip<nnnn>/<a =
href=3D"http://comments.md">comments.md</a>. On a side note, more complex r=
eference implementation code should be stored in that folder too.</div><div=
>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
(On another note, I wonder if we should recommend non-reference implementat=
ion<br>
lists/links be moved to BIP Comments rather than constantly revising the BI=
Ps<br>
with them...)<br></blockquote><div><br></div><div>Certainly those could be =
on the comments page.</div></div></div></div>
--001a11420a5627ff9e052e4f9159--
|
