public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Milly Bitcoin <milly@bitcoins.info>
To: bitcoin-dev@lists.linuxfoundation.org, pete@petertodd.org
Subject: Re: [bitcoin-dev] [BIP/Draft] BIP Acceptance Process
Date: Fri, 4 Sep 2015 17:05:02 -0400	[thread overview]
Message-ID: <55EA077E.5090102@bitcoins.info> (raw)
In-Reply-To: <20150904203144.GB463@muck>

> IMO trying to "set up a system" in that kind of environment is silly,

The first step is to define the system that is currently in place. 
There is a system in place but it is just close to the vest and 
sometimes not discussed in public.  This works when Bitcoin has a small 
number of stakeholder but does not work well as other parties with 
diverse interests get involved.  You can't expect major players to 
invest large sums when the process is controlled by a tiny group of 
people where some of those people have rather unusual opinions about 
things and limited experience outside of technical areas within Bitcoin.

You just don't have enough experience in working on large projects to 
understand the benefits of the proposal discussed.  I suggest you look 
into into and get some experience instead of posting rants that 
highlight your inexperience.  What is silly is using a process that 
involves hyperbolic twitter and reddit posts.

Basically such a process does not replace the analysis that is done now, 
it just makes it transparent and attempts to make it consistent so there 
is not all this confusion over comparing apples and oranges.  Here is 
link that discusses some of the benefits and limitations of doing this: 
  http://www.jakeman.com.au/media/whats-right-with-risk-matrices.

Russ




  parent reply	other threads:[~2015-09-04 21:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04  0:30 [bitcoin-dev] [BIP/Draft] BIP Acceptance Process Andy Chase
2015-09-04  0:41 ` Luke Dashjr
2015-09-04  0:52   ` Andy Chase
2015-09-04  0:43 ` Bryan Bishop
2015-09-04  4:40   ` Andy Chase
2015-09-04 19:20     ` Btc Drak
2015-09-04 20:13       ` Andy Chase
2015-09-04 20:31         ` Peter Todd
2015-09-04 20:42           ` Martin Becze
2015-09-04 21:05           ` Milly Bitcoin [this message]
2015-09-04 21:01         ` Luke Dashjr
2015-09-04 21:36           ` Andy Chase
2015-09-04 21:45             ` Luke Dashjr
2015-09-05 21:19               ` Andy Chase
     [not found]                 ` <CAHv+tb5ksyZKp5jLvmzFbD2vBOUrWn6ps80ODECVRqYj8m=PZA@mail.gmail.com>
2015-09-06 20:44                   ` Andy Chase
2016-01-19  2:12                 ` Luke Dashjr
2016-01-19  4:23                   ` Andy Chase
2016-01-19  6:07                   ` Dave Scotese
2015-09-07 19:37         ` Btc Drak
2015-09-10  1:21           ` Andy Chase
2015-09-12 23:50             ` Andy Chase

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=55EA077E.5090102@bitcoins.info \
    --to=milly@bitcoins.info \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=pete@petertodd.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