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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <benjamin.l.cordes@gmail.com>) id 1VYMZZ-0007in-KC
for bitcoin-development@lists.sourceforge.net;
Mon, 21 Oct 2013 20:59:33 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.44 as permitted sender)
client-ip=209.85.219.44;
envelope-from=benjamin.l.cordes@gmail.com;
helo=mail-oa0-f44.google.com;
Received: from mail-oa0-f44.google.com ([209.85.219.44])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VYMZY-0006r6-3a
for bitcoin-development@lists.sourceforge.net;
Mon, 21 Oct 2013 20:59:33 +0000
Received: by mail-oa0-f44.google.com with SMTP id l20so5730613oag.17
for <bitcoin-development@lists.sourceforge.net>;
Mon, 21 Oct 2013 13:59:26 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.73.231 with SMTP id o7mr22640814obv.34.1382389166498;
Mon, 21 Oct 2013 13:59:26 -0700 (PDT)
Received: by 10.182.5.198 with HTTP; Mon, 21 Oct 2013 13:59:26 -0700 (PDT)
In-Reply-To: <201310211947.59640.luke@dashjr.org>
References: <791a727f-2188-4848-bd77-ea733c8c5c2c@me.com>
<201310211947.59640.luke@dashjr.org>
Date: Mon, 21 Oct 2013 22:59:26 +0200
Message-ID: <CAOoPuRbNUQ6rxbHw3hTPVDh5KfT1JLfEaFORwYxAphEuRpLP=Q@mail.gmail.com>
From: Benjamin Cordes <benjamin.l.cordes@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=047d7bfe93fe35ea2704e9468f35
X-Spam-Score: -0.6 (/)
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
(benjamin.l.cordes[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: 1VYMZY-0006r6-3a
Subject: Re: [Bitcoin-development] Revisiting the BIPS process, a proposal
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, 21 Oct 2013 20:59:33 -0000
--047d7bfe93fe35ea2704e9468f35
Content-Type: text/plain; charset=ISO-8859-1
I believe a better solution would to use a github clone such as gitlab,
which sits on top of the git repo, and allows for custom code around the
BIP process. Potentially one could even build Bitcoin into such a BIP
system. If somebody wants to support a BIP he donates Bitcoins to that
proposal. Somebody who actually implements the BIP can receive some percent
of the bounty, while some percentage goes to the Bitcoin foundation. Via
such a platform one could create assurance contracts to kickstart BIP
developments or Bitcoin extensions (public infrastructure which is not part
of the core, such as opensourced exchanges).
On Mon, Oct 21, 2013 at 9:47 PM, Luke-Jr <luke@dashjr.org> wrote:
> On Monday, October 21, 2013 7:38:37 PM Jean-Paul Kogelman wrote:
> > 1) Should the protocol specification page also be codified into BIP(s)?
>
> Probably wouldn't hurt, but it'd likely need a rewrite in a more modular
> and
> formal form.
>
> > 2) Should the current wiki pages be taken down / forwarded to the git
> repo
> > or be auto updated from the git repo?
>
> Since it's the same format, I'd keep it up there, maybe with a link to the
> git
> repo on the main BIP index wiki page.
>
> > 3) Even though the information in BIP 50 is valuable, should it really be
> > considered a BIP?
>
> It's a hardforking protocol change, so IMO yes.
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7bfe93fe35ea2704e9468f35
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><span style=3D"font-family:arial,sans-serif;font-size:13px=
">I believe a better solution would to use a github clone such as gitlab, w=
hich sits on top of the git repo, and allows for custom code around the BIP=
process. Potentially one could even build Bitcoin into such a BIP system. =
If somebody wants to support a BIP he donates Bitcoins to that proposal. So=
mebody who actually implements the BIP can receive some percent of the boun=
ty, while some percentage goes to the Bitcoin foundation. Via such a platfo=
rm one could create assurance contracts to kickstart BIP developments or Bi=
tcoin extensions (public infrastructure which is not part of the core, such=
as opensourced exchanges).</span><br>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon,=
Oct 21, 2013 at 9:47 PM, Luke-Jr <span dir=3D"ltr"><<a href=3D"mailto:l=
uke@dashjr.org" target=3D"_blank">luke@dashjr.org</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">
<div class=3D"im">On Monday, October 21, 2013 7:38:37 PM Jean-Paul Kogelman=
wrote:<br>
> 1) Should the protocol specification page also be codified into BIP(s)=
?<br>
<br>
</div>Probably wouldn't hurt, but it'd likely need a rewrite in a m=
ore modular and<br>
formal form.<br>
<div class=3D"im"><br>
> 2) Should the current wiki pages be taken down / forwarded to the git =
repo<br>
> or be auto updated from the git repo?<br>
<br>
</div>Since it's the same format, I'd keep it up there, maybe with =
a link to the git<br>
repo on the main BIP index wiki page.<br>
<div class=3D"im"><br>
> 3) Even though the information in BIP 50 is valuable, should it really=
be<br>
> considered a BIP?<br>
<br>
</div>It's a hardforking protocol change, so IMO yes.<br>
<div class=3D"im"><br>
---------------------------------------------------------------------------=
---<br>
October Webinars: Code for Performance<br>
Free Intel webinars can help you accelerate application performance.<br>
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most fr=
om<br>
the latest Intel processors and coprocessors. See abstracts and register &g=
t;<br>
</div><a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D60135991&a=
mp;iu=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.ne=
t/gampad/clk?id=3D60135991&iu=3D/4140/ostg.clktrk</a><br>
<div class=3D"HOEnZb"><div class=3D"h5">___________________________________=
____________<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>
--047d7bfe93fe35ea2704e9468f35--
|
