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

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

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?
It's very strange that this is not allowed - especially if we consider that 
the Bitcoin community is in a state of constant dissent currently.
The effect is likely that you push the actual decision-making to IRC, which 
less people have access to (since it's difficult to bear the high traffic), 
and thus form some kind of "inner circle" - which makes decisions seem even 
more as if they're being dictated.

So please consider allowing people to say whether they agree with something 
something or don't.


Other than that, thanks for the good latency of moderation, I guess you're 
doing hard work there :)

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

  reply	other threads:[~2016-01-21  2:25 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 [this message]
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
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=2998879.R5sQRbxZRv@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