From: Emil Engler <me@emilengler.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] [Meta] bitcoin-dev moderation
Date: Thu, 1 Aug 2019 21:47:40 +0200 [thread overview]
Message-ID: <53b75074-59ff-9890-419d-d5e6fcb44a7c@emilengler.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
In the last #bitcoin-core-dev IRC meeting, the mailing list moderation
was slightly discussed. It was decided to do this discussion mainly on
this mailing list (which makes sense).
The current situation is that the moderation is slow and takes around
>24h for a E-Mail to be on the mailing list.
Jonas Schnelli proposed: "I propose that we add more moderators to
shorten the moderation lag which has been between >24h, thus makes
debates cumbersome"
Beside this I had the idea of people who already contributed n e-mails
to the mailing list don't need an approval for any e-mail anymore (Where
n is the number of previous e-mails). Does this exists already?
Greetings,
Emil Engler
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 3199 bytes --]
next reply other threads:[~2019-08-01 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 19:47 Emil Engler [this message]
2019-08-02 11:43 ` [bitcoin-dev] [Meta] bitcoin-dev moderation Bryan Bishop
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=53b75074-59ff-9890-419d-d5e6fcb44a7c@emilengler.com \
--to=me@emilengler.com \
--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