From: Matt Whitlock <bip@mattwhitlock.name>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Prenumbered BIP naming
Date: Mon, 12 May 2014 13:01:43 -0400 [thread overview]
Message-ID: <1612758.yYdJV7lBXv@crushinator> (raw)
In-Reply-To: <CAAS2fgRWKWMkzqpQDXJGJYZPyb+vTnaRs3jOrzQ-zG5JJyqr1Q@mail.gmail.com>
On Monday, 12 May 2014, at 9:53 am, Gregory Maxwell wrote:
> I've noticed some folks struggling to attach labels to their yet to be
> numbered BIPs.
>
> I'd recommend people call them "draft-<main author name>-<what it
> does>" like draft-maxwell-coinburning in the style of pre-WG IETF
> drafts.
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?
next prev parent reply other threads:[~2014-05-12 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 16:53 [Bitcoin-development] Prenumbered BIP naming Gregory Maxwell
2014-05-12 17:01 ` Matt Whitlock [this message]
2014-05-12 17:11 ` Gregory Maxwell
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=1612758.yYdJV7lBXv@crushinator \
--to=bip@mattwhitlock.name \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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