From: Kalle Rosenbaum <kalle@rosenbaum•se>
To: bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Process for BIP number allocation
Date: Thu, 23 Jul 2015 12:21:55 +0200 [thread overview]
Message-ID: <CAPswA9yU8MkbS_7CkJBmRTTxBdZ+2fx7FetGaqeHMZGG0G=1eA@mail.gmail.com> (raw)
Hi all
I suggest that we add to the "BIP Editor Responsibilities & Workflow"
section of BIP0001 that if the BIP editor for some reason won't handle
the BIP within a week, he/she should notify the author within that
same week with an estimate on when it will be handled.
Maybe we could extend it to two weeks instead, the important thing is
that the author knows what to expect.
I'm trying to get BIP numbers allocated for Proof of Payment. I have
requested it from the BIP editor Gregory Maxwell with CC this list. I
also emailed Gregory in private about it. So far I have not seen any
reaction to my requests.
There are a number of BIP proposals floating arount right now, I don't
know the exact status of them all, but this is roughly how it looks
for some of them:
Date of request, bip#, Author, Title
july 4, -, Gregory Maxwell, Invalid Block Fork Postmortem
june 29, -, Peter Todd, Full Replace-by-Fee Deployment Schedule
june 22, 101, Gavin Andresen, Increase Maximum Block Size
june 17, 68, Mark Friedenbach, Consensus-enforced transaction
replacement signalled via sequence numbers
june 6, -,Kalle Rosenbaum, Proof of Payment
june 6, -,Kalle Rosenbaum, Proof of Payment URI scheme
june 6, 69?, Kristov Atlas, Lexicographical Indexing of Transaction
Inputs and Outputs
I think that the de facto process for BIP allocation and inclusion in
the bips repository is unclear. When a number is requested, the author
should at least get a reply from the bip editor that the request is
seen by him/her. Also, if the editor disapproves on the BIP for some
reason, the author must be notified somehow within reasonable and
predictable time.
Regards,
Kalle
next reply other threads:[~2015-07-23 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 10:21 Kalle Rosenbaum [this message]
2015-07-23 19:29 ` Peter Todd
2015-07-23 21:36 ` Kalle Rosenbaum
2015-07-24 2:26 ` Peter Todd
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='CAPswA9yU8MkbS_7CkJBmRTTxBdZ+2fx7FetGaqeHMZGG0G=1eA@mail.gmail.com' \
--to=kalle@rosenbaum$(echo .)se \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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