Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <laanwj@gmail.com>) id 1Y1ADz-0004ia-MV
	for bitcoin-development@lists.sourceforge.net;
	Wed, 17 Dec 2014 08:44:51 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.181 as permitted sender)
	client-ip=209.85.223.181; envelope-from=laanwj@gmail.com;
	helo=mail-ie0-f181.google.com; 
Received: from mail-ie0-f181.google.com ([209.85.223.181])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Y1ADy-0007OK-Pt
	for bitcoin-development@lists.sourceforge.net;
	Wed, 17 Dec 2014 08:44:51 +0000
Received: by mail-ie0-f181.google.com with SMTP id tp5so14491197ieb.12
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 17 Dec 2014 00:44:45 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.107.156.67 with SMTP id f64mr19239094ioe.9.1418805885475;
	Wed, 17 Dec 2014 00:44:45 -0800 (PST)
Received: by 10.64.195.225 with HTTP; Wed, 17 Dec 2014 00:44:45 -0800 (PST)
In-Reply-To: <48E6B6DA-F977-409C-AEDD-53572986438D@gmail.com>
References: <54876653.4020403@certimix.com> <548769FA.5040406@bluematt.me>
	<CA+s+GJAe9MeO+Sr0+2BRwu3q-Be5JQt_s_xdnBBEcquXqOyxcA@mail.gmail.com>
	<CA+s+GJA0BDMaa2+A7QJdz08Ck4PFQcXs2dg22hi5PCMsGu7dqw@mail.gmail.com>
	<48E6B6DA-F977-409C-AEDD-53572986438D@gmail.com>
Date: Wed, 17 Dec 2014 08:44:45 +0000
Message-ID: <CA+s+GJCpApaQuv6GQc2E-hGdKXM_csADUHa7UcWvYmrXJ0p=NQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Austin Walne <austin.walne@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(laanwj[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Y1ADy-0007OK-Pt
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] ACK NACK utACK "Concept ACK"
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 08:44:51 -0000

On Wed, Dec 10, 2014 at 3:45 PM, Austin Walne <austin.walne@gmail.com> wrote:
> I've had these same questions myself. I'm happy to write up some documentation this afternoon. I can draft something based on this thread. What other key terminology should be included?

Fanquake already started on that (but didn't even mention it here!)
https://github.com/bitcoin/bitcoin/pull/5468

Wladimir