From: Gregory Maxwell <gmaxwell@gmail•com>
To: Matt Whitlock <bip@mattwhitlock•name>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Prenumbered BIP naming
Date: Mon, 12 May 2014 10:11:25 -0700 [thread overview]
Message-ID: <CAAS2fgQOOLKkXbc5FiXhabbew+xrYp7Cy6sQuNPQmg9DU-iyPg@mail.gmail.com> (raw)
In-Reply-To: <1612758.yYdJV7lBXv@crushinator>
On Mon, May 12, 2014 at 10:01 AM, Matt Whitlock <bip@mattwhitlock•name> wrote:
> Why is there such a high bar to getting a number assigned to a BIP anyway? BIP 1 seems to suggest that getting a BIP number assigned is no big deal, but the reality seems to betray that casual notion. Even proposals with hours of work put into them are not getting BIP numbers. It's not exactly as though there's a shortage of integers. Are numbers assigned only to proposals that are well liked? Isn't the point of assigning numbers so that we can have organized discussions about all proposals, even ones we don't like?
It isn't a big deal, but according to the process numbers shouldn't be
assigned for things that haven't even been publically discussed. If
someone wants to create specifications that are purely the product of
they own work and not a public discussion— they should feel free to do
that, but BIP isn't the process for that. So, since things need to be
discussed, it can be useful to have something to call a proposal
before other things happen— thats all. The same kind of issue arises
elsewhere.
prev parent reply other threads:[~2014-05-12 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 16:53 Gregory Maxwell
2014-05-12 17:01 ` Matt Whitlock
2014-05-12 17:11 ` Gregory Maxwell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAS2fgQOOLKkXbc5FiXhabbew+xrYp7Cy6sQuNPQmg9DU-iyPg@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bip@mattwhitlock$(echo .)name \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox