public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: xor@freenetproject.org
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Three Month bitcoin-dev Moderation Review
Date: Sat, 23 Jan 2016 06:33:56 +0100	[thread overview]
Message-ID: <1736759.DT0dcscznj@1337h4x0r> (raw)
In-Reply-To: <87powvy20w.fsf@rustcorp.com.au>

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

On Thursday, January 21, 2016 03:14:47 PM Rusty Russell wrote:
> +1s here means simpling say "+1" or "me too" that carries no additional
> information.  ie. if you like an idea, that's great, but it's not worth
> interruping the entire list for.
> 
> If you say "I prefer proposal X over Y because <reasons>" that's
> different.  As is "I dislike X because <reasons>" or "I need X because
> <reasons>".

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".

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2016-01-23  5:34 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 [this message]
2016-01-23 20:59       ` Peter Todd
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=1736759.DT0dcscznj@1337h4x0r \
    --to=xor@freenetproject.org \
    --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