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
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <g.rowe.froot@gmail.com>) id 1Vofs3-0006D4-U0
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Dec 2013 20:50:03 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.175 as permitted sender)
client-ip=209.85.220.175; envelope-from=g.rowe.froot@gmail.com;
helo=mail-vc0-f175.google.com;
Received: from mail-vc0-f175.google.com ([209.85.220.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Vofs2-0006DI-DI
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Dec 2013 20:50:03 +0000
Received: by mail-vc0-f175.google.com with SMTP id ld13so13663037vcb.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 05 Dec 2013 12:49:57 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.220.124.68 with SMTP id t4mr16549vcr.52.1386276596819; Thu,
05 Dec 2013 12:49:56 -0800 (PST)
Sender: g.rowe.froot@gmail.com
Received: by 10.220.205.71 with HTTP; Thu, 5 Dec 2013 12:49:56 -0800 (PST)
In-Reply-To: <CAJHLa0OhQn=+BpbvejqRZBv=x3Vd5BYSDERERMEYDrrQ0gRXkQ@mail.gmail.com>
References: <CA+s+GJCuWNj7LuLJy4rSkN_t0qgO3UsBS2hEBTgm6DiiQyqbVQ@mail.gmail.com>
<201312051427.44179.luke@dashjr.org>
<CAJHLa0OhQn=+BpbvejqRZBv=x3Vd5BYSDERERMEYDrrQ0gRXkQ@mail.gmail.com>
Date: Thu, 5 Dec 2013 20:49:56 +0000
X-Google-Sender-Auth: y39uCSpMeSTifhlPjuzq97yGx7Y
Message-ID: <CAKm8k+2=kSeDALJJLF9hPfuyDyHN+G9Dx6cQRPGgcKRVOW-4aA@mail.gmail.com>
From: Gary Rowe <g.rowe@froot.co.uk>
To: Bitcoin Development List <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e013a29081d5add04eccfacf4
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: doubleclick.net]
-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
(g.rowe.froot[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1Vofs2-0006DI-DI
Subject: Re: [Bitcoin-development] Move authorative source for BIPs to git
repository
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: Thu, 05 Dec 2013 20:50:04 -0000
--089e013a29081d5add04eccfacf4
Content-Type: text/plain; charset=UTF-8
Personally, I would be more inclined to submit and work on a BIP if it was
in GitHub. It's a regular home from home for me now.
On 5 December 2013 14:43, Jeff Garzik <jgarzik@bitpay.com> wrote:
> This entire discussion is recycled. Please review the previous
> discussion, before asking the same questions over again.
>
> Properly done, there are FEWER hurdles. In the previous discussion,
> there was outlined a process whereby the BIPS Editor would receive an
> email, and could take it from there. No wiki login or bitcoin payment
> required. More advanced users may submit pull requests.
>
> Compared with a hash-sealed git repo as primary source, the wiki is
> second class.
>
>
> On Thu, Dec 5, 2013 at 9:27 AM, Luke-Jr <luke@dashjr.org> wrote:
> > On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote:
> >> Hello all,
> >>
> >> A while ago after discussion on the mailing list a repository was set
> up to
> >> store the BIP documents, as this is deemed a more secure solution than
> >> having them on the wiki:
> >>
> >> https://github.com/bitcoin/bips
> >>
> >> To prevent confusion the next step should probably be to replace the
> BIPs
> >> on the wiki with links to the github documents, with a notice that
> changes
> >> should be proposed on github or mailed to the BIP editor (gmaxwell).
> >>
> >> Agreed?
> >
> > I think this would stifle active BIP draft editing. We're already having
> a
> > hard time getting some developers to write BIPs for their proposals - I
> don't
> > think we should be putting up bigger hurdles.
> >
> > Luke
> >
> >
> ------------------------------------------------------------------------------
> > Sponsored by Intel(R) XDK
> > Develop, test and display web and hybrid apps with a single code base.
> > Download it for free now!
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
>
> ------------------------------------------------------------------------------
> Sponsored by Intel(R) XDK
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
>
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--089e013a29081d5add04eccfacf4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Personally, I would be more inclined to submit and work on=
a BIP if it was in GitHub. It's a regular home from home for me now.<b=
r></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On 5 =
December 2013 14:43, Jeff Garzik <span dir=3D"ltr"><<a href=3D"mailto:jg=
arzik@bitpay.com" target=3D"_blank">jgarzik@bitpay.com</a>></span> wrote=
:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">This entire discussion is recycled. =C2=A0Pl=
ease review the previous<br>
discussion, before asking the same questions over again.<br>
<br>
Properly done, there are FEWER hurdles. =C2=A0In the previous discussion,<b=
r>
there was outlined a process whereby the BIPS Editor would receive an<br>
email, and could take it from there. =C2=A0No wiki login or bitcoin payment=
<br>
required. =C2=A0More advanced users may submit pull requests.<br>
<br>
Compared with a hash-sealed git repo as primary source, the wiki is<br>
second class.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On Thu, Dec 5, 2013 at 9:27 AM, Luke-Jr <<a href=3D"mailto:luke@dashjr.o=
rg">luke@dashjr.org</a>> wrote:<br>
> On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote:<br>
>> Hello all,<br>
>><br>
>> A while ago after discussion on the mailing list a repository was =
set up to<br>
>> store the BIP documents, as this is deemed a more secure solution =
than<br>
>> having them on the wiki:<br>
>><br>
>> <a href=3D"https://github.com/bitcoin/bips" target=3D"_blank">http=
s://github.com/bitcoin/bips</a><br>
>><br>
>> To prevent confusion the next step should probably be to replace t=
he BIPs<br>
>> on the wiki with links to the github documents, with a notice that=
changes<br>
>> should be proposed on github or mailed to the BIP editor (gmaxwell=
).<br>
>><br>
>> Agreed?<br>
><br>
> I think this would stifle active BIP draft editing. We're already =
having a<br>
> hard time getting some developers to write BIPs for their proposals - =
I don't<br>
> think we should be putting up bigger hurdles.<br>
><br>
> Luke<br>
><br>
> ----------------------------------------------------------------------=
--------<br>
> Sponsored by Intel(R) XDK<br>
> Develop, test and display web and hybrid apps with a single code base.=
<br>
> Download it for free now!<br>
> <a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D111408631&a=
mp;iu=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.ne=
t/gampad/clk?id=3D111408631&iu=3D/4140/ostg.clktrk</a><br>
> _______________________________________________<br>
> Bitcoin-development mailing list<br>
> <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-d=
evelopment@lists.sourceforge.net</a><br>
> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-develo=
pment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitco=
in-development</a><br>
<br>
<br>
<br>
</div></div><span class=3D"HOEnZb"><font color=3D"#888888">--<br>
Jeff Garzik<br>
Bitcoin core developer and open source evangelist<br>
BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" target=3D"=
_blank">https://bitpay.com/</a><br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
Sponsored by Intel(R) XDK<br>
Develop, test and display web and hybrid apps with a single code base.<br>
Download it for free now!<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D111408631&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D111408631&iu=3D/4140/ostg.clktrk</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>
--089e013a29081d5add04eccfacf4--
|
