From: Luke Dashjr <luke@dashjr•org>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Process: Status, comments, and copyright licenses
Date: Tue, 2 Feb 2016 19:08:19 +0000 [thread overview]
Message-ID: <201602021908.20547.luke@dashjr.org> (raw)
In-Reply-To: <CABsx9T2X+2Vnwd3RJJvRpNKbO2S1kY8JS2YqHEKUmAhYSNpkBg@mail.gmail.com>
On Tuesday, February 02, 2016 3:58:21 PM Gavin Andresen wrote:
> I don't like the definition of "consensus". I think the definition
> described gives too much centralized control to whoever controls the
> mailing list and the wiki.
How can I improve this? Inevitably, every medium of communications will be
controlled by someone (even if unmoderated, it becomes effectively controlled
by trolls who spam it with garbage).
I think it's important to note that this is also only for updating the status
of BIPs, and is not in any way relevant to such proposals *actually* being
accepted. So if the BIP process were to breakdown on this or any other point,
it isn't somehow controlling the actual reality. To explicitly clarify this
point, I have added to the end of the section:
"These criteria are considered objective ways to observe the de facto
adoption of the BIP, and are not to be used as reasons to oppose or
reject a BIP. Should a BIP become actually and unambiguously adopted
despite not meeting the criteria outlined here, it should still be
updated to Final status."
Does that help?
Thanks,
Luke
next prev parent reply other threads:[~2016-02-02 19:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 22:53 Luke Dashjr
2016-02-02 5:50 ` Dave Scotese
2016-02-02 7:54 ` Luke Dashjr
2016-02-02 16:00 ` Dave Scotese
2016-02-02 15:58 ` Gavin Andresen
2016-02-02 17:38 ` Jorge Timón
2016-02-02 19:41 ` Luke Dashjr
[not found] ` <CAGLBAhdFo2pXcDfvPCTpm7ufQuG8z4mHsdoidGkhB3q5SWLj=A@mail.gmail.com>
2016-02-03 0:03 ` Luke Dashjr
2016-02-03 0:59 ` Jorge Timón
2016-02-02 19:08 ` Luke Dashjr [this message]
2016-03-10 0:37 ` Mustafa Al-Bassam
2016-02-04 4:15 ` Luke Dashjr
2016-02-04 17:45 ` Ryan Grant
2016-02-04 21:17 ` Luke Dashjr
2016-02-05 0:09 ` Ryan Grant
2016-02-02 6:35 Ryan Grant
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=201602021908.20547.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=gavinandresen@gmail$(echo .)com \
/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