summaryrefslogtreecommitdiff
path: root/23/749f38e027adeef8d728ca2b2dda2051d419b3
blob: fc8054a875f3f6b02e4f6c22d3a9bdb1cfd8daa2 (plain)
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
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 4BBB9F1A
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu,  3 Sep 2015 23:45:35 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com
	[209.85.212.180])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9DF591BF
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu,  3 Sep 2015 23:45:34 +0000 (UTC)
Received: by wicge5 with SMTP id ge5so1156510wic.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 03 Sep 2015 16:45:33 -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:content-type;
	bh=lQA3W0CCCKpk81cEjjPFa1k5j7bgJXLW/65SJgsFgaw=;
	b=scRRn9ANhtQ18N0GUYXWkYYCriH2JCxkfa+3fZcpmsPLUUxmsvRyOg7cLxp3QaI91N
	ZG48nTeAYFrbPevVeIWelvGCBUHzo5nIRXoKsiKE0bQkxhT7uC2v0oEn6RPnqFPBOAAS
	G1OMC18FAyEBak322NKMQDoiOjFxU//e9s++kdnqADX2KDT/purKUstuZqJEJJf0d172
	KN8eKGKC5ZxkDpSccA8WQMl36kRgpniE8B+y7GO+lWs0xuzfxVYpgbobgxhBQp+OyZH3
	dE4DXz8jgiAzNn0FacOOqJiflZfvxGw3i8dCm32Nb2xc40g7OKpi7ra3P90ZU0yu5EO4
	ENPA==
X-Received: by 10.194.191.164 with SMTP id gz4mr1122278wjc.21.1441323933259;
	Thu, 03 Sep 2015 16:45:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.211.16 with HTTP; Thu, 3 Sep 2015 16:45:13 -0700 (PDT)
In-Reply-To: <CAAS2fgR4iGshOgsammWQ93yD0GsckUgroX-sb7mDE7XuQb5k3g@mail.gmail.com>
References: <CAAS2fgR4iGshOgsammWQ93yD0GsckUgroX-sb7mDE7XuQb5k3g@mail.gmail.com>
From: Btc Drak <btcdrak@gmail.com>
Date: Fri, 4 Sep 2015 00:45:13 +0100
Message-ID: <CADJgMzvQ2g7Sr3w3_iDCY4WhZ3RuMWdmYOwib6+b4FSbB5LguA@mail.gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: text/plain; charset=UTF-8
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, 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
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposed minor change to BIP 01 to use a PR for
 request assignment
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: Thu, 03 Sep 2015 23:45:35 -0000

It's a good idea. It would remove friction from the process and
assignment is auditable to boot, something I've had difficulty with in
the past. Almost every time I see a BIP number I would wonder, is that
self-assigned (and thus invalid) or has it been assigned by the BIP
editor.

On Fri, Sep 4, 2015 at 12:18 AM, Gregory Maxwell via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> The process in BIP01 was written when we used a different solution for
> storing and presenting BIPs.
>
> I'm thinking of suggesting that the number request process be changed
> to opening a pull req with BIP text with no number (e.g. just using
> the authors name and an index as the number) as the mechenism to
> request number assignment.
>
> Is there any reason that anyone would find this objectionable?
>
> (Please do not respond to this message with anything but a strictly
> directed answer to that question, start a new thread for a different
> subject. Thanks!)
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev