public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: xor@freenetproject.org, bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Three Month bitcoin-dev Moderation Review
Date: Thu, 21 Jan 2016 15:14:47 +1030	[thread overview]
Message-ID: <87powvy20w.fsf@rustcorp.com.au> (raw)
In-Reply-To: <2998879.R5sQRbxZRv@1337h4x0r>

xor--- via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> writes:
> On Thursday, January 21, 2016 11:20:46 AM Rusty Russell via bitcoin-dev wrote:
>> So, what should moderation look like from now on?
>
> The original mail which announced moderation contains this rule:
>> - Generally discouraged: [...], +1s, [...]
>
> I assume "+1s" means statements such as "I agree with doing X".
>
> Any sane procedure of deciding something includes asking the involved people 
> whether they're for or against it.
> If there are dozens of proposals on how to solve a particular technical 
> problem, how else do you want to decide it than having a vote?

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

Hope that clarifies!
Rusty.


  parent reply	other threads:[~2016-01-21  4:44 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 [this message]
2016-01-23  5:33     ` xor
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=87powvy20w.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --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