public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andy Chase <theandychase@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] BIP/Motivation and deployment of consensus rule changes ([soft/hard]forks)
Date: Tue, 25 Aug 2015 16:20:28 -0700	[thread overview]
Message-ID: <CAAxp-m9R+cOJ6nn9PeKWkj7zops-8+xKzrmzZN6qUc6ZD9tQrw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]

As I understand Github is not to be used for the high-level discussion
of a draft BIP so I will post my thoughts here (is this specified
somewhere? Can we specify this in BIP-0001?).

-   I have some concerns about the structure and the wording of this
    proposal. I think both the structure and the internal wording can be
    slimmed down and simplified
    -   I also believe the "history lessons" should be trimmed out,
        mentioned at best
    -   There's separate BIP for at least one of the code forks
-   BIP-001 specifies that BIP proposals should not be given a BIP
    number until after they have been spelled checked and approved by an
    editor. Greg Maxwell: was this followed?
-   What kind of proposal is this? Informational, Process or Standards
    track?
    -   I believe it should be Standards Track. Include the proposed
        upgrade path as a patch into core as a module that hard forks
        can use in the future. This will also give us some space to work
        through some of the complexities of forks in a definite way.
    -   Alternatively maybe we can split up this BIP into a Standards
        track and a separate Informational BIP?

[-- Attachment #2: Type: text/html, Size: 1504 bytes --]

                 reply	other threads:[~2015-08-25 23:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAAxp-m9R+cOJ6nn9PeKWkj7zops-8+xKzrmzZN6qUc6ZD9tQrw@mail.gmail.com \
    --to=theandychase@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.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