public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: xor@freenetproject.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Three Month bitcoin-dev Moderation Review
Date: Sat, 23 Jan 2016 15:59:53 -0500	[thread overview]
Message-ID: <20160123205953.GA22494@muck> (raw)
In-Reply-To: <1736759.DT0dcscznj@1337h4x0r>

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

On Sat, Jan 23, 2016 at 06:33:56AM +0100, xor--- via bitcoin-dev wrote:
> So "+1"ing is OK as long as I provide a technical explanation of why I agree?
> While I still think that this is too much of a restriction because it prevents 
> peer-review, I would say that I could live with it as a last resort if you 
> don't plan to abolish this rule altogether.
> 
> So in that case, to foster peer review, I would recommend you amend the rules 
> to clarify this.
> Example: "+1s are not allowed unless you provide an explanation of why you 
> agree with something".

I would extend this to say that the technical explanation also should
contribute uniquely to the conversation; a +1 with an explanation
the last +1 gave isn't useful.

-- 
'peter'[:-1]@petertodd.org
000000000000000007e2005be0ce25b3f3de67b2dc35fd810b0ccd77b33eb7be

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]

  reply	other threads:[~2016-01-23 21:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  0:50 [bitcoin-dev] Three Month bitcoin-dev Moderation Review Rusty Russell
2016-01-21  2:25 ` xor
2016-01-21  4:35   ` Dave Scotese
2016-01-21  5:00     ` Rusty Russell
2016-01-21  4:44   ` Rusty Russell
2016-01-23  5:33     ` xor
2016-01-23 20:59       ` Peter Todd [this message]
2016-01-23 21:38         ` Gavin
2016-01-24  1:06           ` Dave Scotese
2016-02-09 23:24             ` David Vorick

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=20160123205953.GA22494@muck \
    --to=pete@petertodd.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=xor@freenetproject.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