From: Jeff Garzik <jgarzik@gmail.com>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] On bitcoin-dev list admin and list noise
Date: Tue, 29 Sep 2015 11:44:57 -0400 [thread overview]
Message-ID: <CADm_Wcbf+p=ShdfQqKzbWPvVWJ6WMxR2dF4Y4M5N+yzoqZtTCw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
This was discussed in IRC, but (did I miss it?) never made it to the list
outside of being buried in a longer summary.
There is a common complain that bitcoin-dev is too noisy. The response
plan is to narrow the focus of the list to near term technical changes to
the bitcoin protocol and its implementations (bitcoin core, btcd, ...)
Debates over bitcoin philosophy, broader context, etc. will start seeing
grumpy list admins squawk about "off-topic!"
It is a fair criticism, though, that "take it elsewhere!" needs to have
some place as a suggested destination. The proposal is to create a second
list, bitcoin-tech-discuss or perhaps just 'bitcoin', with a more general
rubric. This split has served IRC well and generally manages to keep the
noise down to a productive level. We want this list to achieve that same
goal; if bitcoin-dev is not productive then it's not useful.
[-- Attachment #2: Type: text/html, Size: 1047 bytes --]
next reply other threads:[~2015-09-29 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 15:44 Jeff Garzik [this message]
2015-09-29 16:38 ` [bitcoin-dev] On bitcoin-dev list admin and list noise Santino Napolitano
2015-09-29 17:07 ` Mark Friedenbach
2015-09-29 17:29 ` Mike Hearn
2015-09-29 17:59 ` Pavel Janík
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='CADm_Wcbf+p=ShdfQqKzbWPvVWJ6WMxR2dF4Y4M5N+yzoqZtTCw@mail.gmail.com' \
--to=jgarzik@gmail.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