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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1Voa96-0003Gw-By
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Dec 2013 14:43:16 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.173 as permitted sender)
client-ip=74.125.82.173; envelope-from=jgarzik@bitpay.com;
helo=mail-we0-f173.google.com;
Received: from mail-we0-f173.google.com ([74.125.82.173])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Voa95-0004Sa-94
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Dec 2013 14:43:16 +0000
Received: by mail-we0-f173.google.com with SMTP id u57so10894478wes.18
for <bitcoin-development@lists.sourceforge.net>;
Thu, 05 Dec 2013 06:43:08 -0800 (PST)
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:date
:message-id:subject:from:to:cc:content-type;
bh=y4h6TLgUANNeDGRdwzexvpZHgp6KbyxNJrVu9ieVEhw=;
b=KFQpEtWYt7n2KbDeFISiM2drStVo3bcRAwt6v+TB7mRkZDxETHyqaiV++7TqGz+yEl
MJQVZWOknLi5Ks8a2uTQv4StcbaYf4mmPBUDFteKr9iydLhS3sde3wE1E/Q24R0YZH0O
3fgR2Gj49w03YW86/LbID5GhLGMOQS3yldKnad8w/WRv0DT3kWotWedktKkQ97byPMTp
XrwNpQnhlJhFRhLnW7n7DiD/prUiMVgm7NZGp50epLJHfwIoytZ5Twgh1MEDsYxJhu2G
Svm4AaUlFd8XQ9jm+8LJU7/P/3obReyD7qIeLCoizeZnWmmUOj7EnZAaOxslP+8P/WtA
isVA==
X-Gm-Message-State: ALoCoQkmfvvJp2GLIctXXN7D/eXcrgOM0vc2eR9TGgqDnpFyy1zpZCxGmNt4RAZTfejw1KSFzsp2
MIME-Version: 1.0
X-Received: by 10.180.188.194 with SMTP id gc2mr12306796wic.53.1386254588847;
Thu, 05 Dec 2013 06:43:08 -0800 (PST)
Received: by 10.194.164.164 with HTTP; Thu, 5 Dec 2013 06:43:08 -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 09:43:08 -0500
Message-ID: <CAJHLa0OhQn=+BpbvejqRZBv=x3Vd5BYSDERERMEYDrrQ0gRXkQ@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record
-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: 1Voa95-0004Sa-94
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:43:16 -0000
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/
|
