From: Btc Drak <btcdrak@gmail•com>
To: Nicolas Dorier <nicolas.dorier@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 10:09:06 +0100 [thread overview]
Message-ID: <CADJgMzsPkGTtTuTd0AFCeGz9u1A8+fx4+TMS34O-mNsExBkfRA@mail.gmail.com> (raw)
In-Reply-To: <CA+1nnr=35TPycf3=0xn0gbkx=KfEZ36uY3nWEdK986n=dftSHA@mail.gmail.com>
On Fri, Aug 21, 2015 at 6:10 AM, Nicolas Dorier via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> 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.
The most important part that developers should complete is the
"Technical Opinion" column section where they can explain their
general worldview, what their concerns are, how those concerns would
be alleviated. If one is undecided or does not have enough information
regarding each BIP then dont fill it out. That also helps signal the
level of consensus for a proposal.
As it stands at the moment, it's almost impossible to direct someone
at the opinion of a specific developer other than hunting down a few
gems scattered to the four corners of the universe. I tried recently
and it was simply impossible. At least with this system, specific BIPs
aside, we can easily see the view of each developer. I think most of
us can comment on BIP101 since the BIP appears non-negotiable.
The XT faction are easily winning the media war by obscuring rational
debate by high signal to noise ratio. Nicolas' solution means the most
important views expressed by each heavyweight will not get lost and
serve as a good reference point for everyone, including the media.
The site could be extended to include major stakeholders too like
major service providers (think exchanges, wallet providers etc) and
mining pools.
next prev parent reply other threads:[~2015-08-21 9:09 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
2015-08-21 9:09 ` Btc Drak [this message]
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=CADJgMzsPkGTtTuTd0AFCeGz9u1A8+fx4+TMS34O-mNsExBkfRA@mail.gmail.com \
--to=btcdrak@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=nicolas.dorier@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