From: Rusty Russell <rusty@rustcorp•com.au>
To: "Bitcoin Dev" <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Mailing List Moderation Now Active.
Date: Thu, 22 Oct 2015 11:59:11 +1030 [thread overview]
Message-ID: <878u6velnc.fsf@rustcorp.com.au> (raw)
Hi all,
We aim to make the list more contentful and productive; to get devs to
resubscribe we need to maximize high-value interactions.
- Currently 5 moderators. BtcDrak, me, G1lius, Kanzure and Johnathan.
As far as I know we're entirely unconnected, and we cover Asia/Europe/US.
- Moderation will last 3 months. Then we'll have an unmoderated on-list
discussion as to whether it should continue, or change.
- Appeals for/against moderation decisions should be directed to Jeff, who
will have final say. General moderation feedback just send to me.
- All rejected posts will be forwarded to a list for public viewing:
https://lists.ozlabs.org/pipermail/bitcoin-dev-moderation/
- Everyone starts moderated, and the mod bit gets cleared as they post.
It gets set again if someone notices or reports a violation.
- Moderation rules:
- No offensive posts, no personal attacks.
- Posts must concern the near-term development of the bitcoin core
code or bitcoin protocol.
- Posts must contribute to bitcoin development.
- Generally encouraged: patches, notification of pull requests, BIP
proposals, academic paper announcements. And discussions that follow.
- Generally discouraged: shower thoughts, wild speculation, jokes, +1s,
non-technical bitcoin issues, rehashing settled topics without new
data, moderation concerns.
- Detailed patch discussion generally better on the GitHub PR.
- Meta-discussion is better on bitcoin-discuss:
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-discuss
- We will make mistakes, we are human, so please be patient.
Your friendly moderators.
next reply other threads:[~2015-10-22 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 1:29 Rusty Russell [this message]
2015-10-23 11:30 ` Mike Hearn
[not found] ` <CABsx9T32Y94cXyubaedpicH=izCEBBN662b0oTNSi5sN6hnM=w@mail.gmail.com>
2015-10-28 10:26 ` Mike Hearn
2015-10-27 15:21 ` xor
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=878u6velnc.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
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