From: Nicolas Dorier <nicolas.dorier@gmail•com>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Core Devs : can you share your thoughts about all BIPs on this website ?
Date: Fri, 21 Aug 2015 14:10:50 +0900 [thread overview]
Message-ID: <CA+1nnr=35TPycf3=0xn0gbkx=KfEZ36uY3nWEdK986n=dftSHA@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgR4bsJtC99-fK1L+FsQT7vOfOpz9FOVqvAnqbpkaRJHLQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1908 bytes --]
Decision making is not the goal of this site, it is only a way to see
various pros and cons of various devs on various proposals in a single
place.
This is for the community to have a coherent view about what you are
talking about now spread into reddit/mailing/forums.
If you did not analyzed a proposal yet, you don't have to fill out your
opinion veto or approval.
It is only to show what you would you "approve" and what you would "veto",
after your analysis.
Then point out all the discussions in the opinion section that lead you to
your conclusion.
You can change edit your position as you progress into your analysis and as
new BIP get redacted.
I'm eager to include the new proposals.
On Fri, Aug 21, 2015 at 1:45 PM, Gregory Maxwell <gmaxwell@gmail•com> wrote:
> On Wed, Aug 19, 2015 at 4:57 AM, Nicolas Dorier via bitcoin-dev
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
> > I created a small website which show a chart of your approvals about
> various
> > BIPs (which you must fill by yourself with a signed pgp message)
> > For each BIP, you can fill if you approve or not, and give comments.
> (HTML
> > accepted, so you can link stuff you your posts)
> > It would help the community a lot, so I hope you will do it !
> > I'm open to add other important devs, big miners, or other proposal that
> I
> > missed.
>
>
> I think this is a bit well, sad, at the moment-- a basic principle in
> sound decision making is that one should try to withhold judgement
> until after the analysis and options are laid out to avoid prematurely
> laying down "battle lines" which then they're socially and politically
> committed to a particular answer.
>
>
> There are several other BIPs in the works right now that aren't out
> there yet, as well (as presumably) new insight from the workshop. It
> would be a shame if these things would be for naught because of being
> decided prematurely.
>
[-- Attachment #2: Type: text/html, Size: 2570 bytes --]
next prev parent reply other threads:[~2015-08-21 5:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 4:57 Nicolas Dorier
2015-08-21 3:10 ` Btc Drak
2015-08-21 4:45 ` Gregory Maxwell
2015-08-21 5:10 ` Nicolas Dorier [this message]
2015-08-21 9:09 ` Btc Drak
2015-08-21 9:32 ` Peter Todd
2015-08-21 9:29 ` Peter Todd
2015-08-21 9:31 ` Btc Drak
2015-08-21 9:35 ` Peter Todd
2015-08-21 10:55 ` Yifu Guo
2015-08-21 11:28 ` Btc Drak
2015-08-21 12:28 ` Yifu Guo
2015-08-21 13:18 ` Oliver Egginger
2015-08-21 13:34 ` Will Madden
2015-08-21 17:31 ` Oliver Egginger
2015-08-21 18:07 ` Will Madden
2015-08-22 3:02 ` odinn
2015-08-21 16:58 ` Nicolas Dorier
2015-08-21 3:38 Nicolas Dorier
2015-08-21 3:45 ` Eric Lombrozo
2015-08-21 3:54 ` Nicolas Dorier
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='CA+1nnr=35TPycf3=0xn0gbkx=KfEZ36uY3nWEdK986n=dftSHA@mail.gmail.com' \
--to=nicolas.dorier@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=gmaxwell@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