public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed

From: Rusty Russell <rusty@rustcorp•com.au>
To: "Bitcoin Dev" <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Three Month bitcoin-dev Moderation Review
Date: Thu, 21 Jan 2016 11:20:46 +1030	[thread overview]
Message-ID: <87si1rycux.fsf@rustcorp.com.au> (raw)

Hi all!

        As planned, this is the three month review[1]: discussion of how
moderation should change is encouraged in this thread.

        First, thanks to everyone for the restraint shown in sending
(and responding to!) inflammatory or sand-in-the-gears mails, and being
tolerant with our mistakes and variances in moderation.

The only changes we made to the plan so far:
1) We've stopped clearing the "needs mod" bit after first posts, and
2) Trivially answerable emails or proposals have been answered in the
   reject message itself.

You can see almost all (there was some lossage) rejects at:
        https://lists.ozlabs.org/pipermail/bitcoin-dev-moderation/

So, what should moderation look like from now on?
- Stop moderating altogether?
- Moderate <topic> more/less harshly?
- Use a different method/criteria for moderation?
- Add/remove moderators?
- Other improvements?

Thanks,
Rusty.
[1] http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-October/011591.html

next             reply	other threads:[~2016-01-21  0:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  0:50 Rusty Russell [this message]
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
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=87si1rycux.fsf@rustcorp.com.au \
    --to=rusty@rustcorp$(echo .)com.au \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox