public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Ryan Grant <bitcoin-dev@rgrant•org>
To: Luke Dashjr <luke@dashjr•org>,
	Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Process: Status, comments, and copyright licenses
Date: Tue, 2 Feb 2016 02:35:07 -0400	[thread overview]
Message-ID: <CAMnpzfoOMMbZEwh3gxdRZvGHs41oRU4ueZ=xqa1R6Eog2b6UmQ@mail.gmail.com> (raw)

On Mon, Feb 1, 2016 at 6:53 PM, Luke Dashjr via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> Please provide any
> objections now, so I can try to address them now and enable consensus to be
> reached.

For section "Formally defining consensus",

Where objections were not deemed substantiated by the community, clear
reasoning must be offered.

For section "BIP Comments",

Comments should be solicited on the bitcoin-dev mailing list, and
summarized fairly in the wiki; with notice of summarization and time
for suggesting edits on the mailing list.  Wiki registration and
monitoring should not be a required hurdle to participation.


             reply	other threads:[~2016-02-02  6:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02  6:35 Ryan Grant [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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

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='CAMnpzfoOMMbZEwh3gxdRZvGHs41oRU4ueZ=xqa1R6Eog2b6UmQ@mail.gmail.com' \
    --to=bitcoin-dev@rgrant$(echo .)org \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=luke@dashjr$(echo .)org \
    /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