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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1Voa4s-0002G2-3J
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Dec 2013 14:38:54 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.45 as permitted sender)
client-ip=209.85.214.45; envelope-from=laanwj@gmail.com;
helo=mail-bk0-f45.google.com;
Received: from mail-bk0-f45.google.com ([209.85.214.45])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Voa4q-0007QC-AX
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Dec 2013 14:38:54 +0000
Received: by mail-bk0-f45.google.com with SMTP id mx13so7155094bkb.18
for <bitcoin-development@lists.sourceforge.net>;
Thu, 05 Dec 2013 06:38:45 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.205.10.132 with SMTP id pa4mr55713889bkb.15.1386254325777;
Thu, 05 Dec 2013 06:38:45 -0800 (PST)
Received: by 10.204.69.197 with HTTP; Thu, 5 Dec 2013 06:38:45 -0800 (PST)
In-Reply-To: <201312051427.44179.luke@dashjr.org>
References: <CA+s+GJCuWNj7LuLJy4rSkN_t0qgO3UsBS2hEBTgm6DiiQyqbVQ@mail.gmail.com>
<201312051427.44179.luke@dashjr.org>
Date: Thu, 5 Dec 2013 15:38:45 +0100
Message-ID: <CA+s+GJC5LB_9n9ktCby=st-2-y-6x2jQ27D9UOo6WzWrD2CQZQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=20cf30223b13a82f4104ecca7c0f
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
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
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: dashjr.org]
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: 1Voa4q-0007QC-AX
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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 14:38:54 -0000
--20cf30223b13a82f4104ecca7c0f
Content-Type: text/plain; charset=UTF-8
On Thu, Dec 5, 2013 at 3:27 PM, Luke-Jr <luke@dashjr.org> wrote:
> On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote:
>
> 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.
>
How is github a hurdle?
It's easy enough to create a fork and submit back the changes as a pull
request.
In the case of text documents, this can be completely done through the web
interface.
If anything creating a github account is a smaller hurdle than having to
pay to create a wiki account and wait for it to be activated.
Aside: my proposal is for the BIPs that are already accepted, and should
not be edited without dicussion. If people want to put their drafts in the
wiki that's a different story.
Regards,
Wladimir
--20cf30223b13a82f4104ecca7c0f
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 T=
hu, Dec 5, 2013 at 3:27 PM, Luke-Jr <span dir=3D"ltr"><<a href=3D"mailto=
:luke@dashjr.org" target=3D"_blank">luke@dashjr.org</a>></span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote:<br>
</blockquote><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think this w=
ould 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></blockquote><div><br></di=
v><div>How is github a hurdle?<br><br></div><div>It's easy enough to cr=
eate a fork and submit back the changes as a pull request.<br><br></div>
<div>In the case of text documents, this can be completely done through the=
web interface.<br><br></div><div>If anything creating a github account is =
a smaller hurdle than having to pay to create a wiki account and wait for i=
t to be activated.<br>
<br></div><div>Aside: my proposal is for the BIPs that are already accepted=
, and should not be edited without dicussion. If people want to put their d=
rafts in the wiki that's a different story.<br></div><div><br>Regards,<=
br>
</div><div>Wladimir<br></div></div></div></div>
--20cf30223b13a82f4104ecca7c0f--
|
