public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] BIP 2 promotion to Final
Date: Tue, 8 Mar 2016 19:04:27 +0000	[thread overview]
Message-ID: <201603081904.28687.luke@dashjr.org> (raw)

It has been about 1 month since BIP 2 finished receiving comments, so I 
believe it is an appropriate time to begin the process of moving it to Final 
Status. Toward this end, I have opened a pull request:

    https://github.com/bitcoin/bips/pull/350

The current requirement for this is that "the reference implementation is 
complete and accepted by the community". Given the vagueness of this criteria, 
I intend to move forward applying BIP 2's more specific criteria to itself:

> A process BIP may change status from Draft to Active when it achieves rough
> consensus on the mailing list. Such a proposal is said to have rough
> consensus if it has been open to discussion on the development mailing list
> for at least one month, and no person maintains any unaddressed
> substantiated objections to it. Addressed or obstructive objections may be
> ignored/overruled by general agreement that they have been sufficiently
> addressed, but clear reasoning must be given in such circumstances.

Furthermore, there is a reference implementation in the mentioned PR.

Please review the latest draft BIP and provide any objections ASAP.
If there are no outstanding objections on 2016 April 9th, I will consider the 
current draft to have reached rough consensus and update its Status to Final 
by merging the PR.

Thanks,

Luke


             reply	other threads:[~2016-03-08 19:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 19:04 Luke Dashjr [this message]
2016-03-10  0:36 ` [bitcoin-dev] BIP 2 promotion to Final Mustafa Al-Bassam
2016-03-10 15:46   ` Jorge Timón
     [not found] ` <56E0BFDC.5070604@musalbas.com>
     [not found]   ` <201603100053.43822.luke@dashjr.org>
2016-03-10 14:02     ` Mustafa Al-Bassam
2016-03-10 15:59       ` Jorge Timón
2016-03-10 16:28         ` Mustafa Al-Bassam
2016-03-10 16:33           ` Mustafa Al-Bassam
2016-03-10 18:30           ` Jorge Timón
2016-03-10 16:43       ` Luke Dashjr
2016-03-16 20:43 ` Btc Drak
2016-03-16 22:24   ` Luke Dashjr
2016-03-18  9:42     ` Btc Drak
2016-03-18 19:34       ` Luke Dashjr
2016-03-18 22:52         ` David A. Harding
2016-03-18 11:59     ` Tom

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=201603081904.28687.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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