From: Thomas Zander <thomas@thomaszander•se>
To: <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP process
Date: Thu, 16 Oct 2014 09:50:48 +0200 [thread overview]
Message-ID: <201410160950.48809.thomas@thomaszander.se> (raw)
In-Reply-To: <CA+s+GJCzBHGoBo8mcubbaavwR2HPave8GbA90+aGYgiJDKm=4g@mail.gmail.com>
On Wednesday 15. October 2014 11.36.58 Wladimir wrote:
> > We're also having problems with people failing to comment on things,
> > not even "I looked at this and have no opinion", which is really
> > obstructing things.
>
> Well - the only way to avoid that is to set a reasonable deadline,
> after which there is a default decision. You'd hope this would
> motivate people to get involved in time.
I have been part of both the OSI (NEN) and the OASIS standards committees for
a while, working on standards as a technical adviser.
There I learned a lot about how to manage this process, maybe some ideas from
such committees can be useful.
The idea that one person owns a BIP makes total sense, (s)he is the only one
that should be putting forward the BIP when its mature enough for making it
final. Note that this can be already after its been implemented once or twice.
So you have a phase where you have random people propose changes, which should
all go in the public mailinglist, and they can be accepted by the owner
without discussion.
If anyone that sees that change has an objection to the change, (s)he speaks
up and you follow group consensus. This means (and this is actually in an ISO
standard ;) that consensus is reached when nobody is left objecting to the
change.
At some point the BIP is mature enough to vote on, at the discretion of the
owner, and the owner puts it forward and requests a vote. If the above process
was handled cleanly there is a very small chance of it being down-voted so an
actual vote may not be needed (its hard to decide who gets a vote..).
You obviously need a deadline for this and afterwards you mark the proposal
final. Or you close it as "needs more work".
--
Thomas Zander
next prev parent reply other threads:[~2014-10-16 7:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 8:29 Wladimir
2014-10-15 9:22 ` Gregory Maxwell
2014-10-15 9:36 ` Wladimir
2014-10-15 18:58 ` Cory Fields
2014-10-16 7:50 ` Thomas Zander [this message]
2014-10-15 15:37 ` Gavin Andresen
2014-10-15 15:46 ` Mike Hearn
2014-10-15 15:54 ` Adam Back
2014-10-15 16:47 ` Peter Todd
2014-10-15 18:13 ` Mike Hearn
2014-10-16 7:38 ` Thomas Zander
2014-10-16 14:19 ` Oliver Egginger
2014-10-15 19:00 ` Btc Drak
2014-10-15 19:40 ` Peter Todd
2014-10-16 4:41 ` Luke Dashjr
2014-10-19 7:17 ` xor
2014-10-19 9:42 ` Btc Drak
2014-10-19 9:49 ` Wladimir
2014-10-19 18:58 ` Thomas Zander
2014-10-20 0:33 ` odinn
-- strict thread matches above, loose matches on Subject: below --
2011-10-18 19:17 Gavin Andresen
2011-10-18 21:26 ` Nils Schneider
2011-10-20 5:02 ` Alex Waters
2011-10-20 11:27 ` Christian Decker
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=201410160950.48809.thomas@thomaszander.se \
--to=thomas@thomaszander$(echo .)se \
--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