From: Alex Morcos <morcos@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] bitcoin-dev list etiquette
Date: Wed, 19 Aug 2015 16:08:02 -0400 [thread overview]
Message-ID: <CAPWm=eVr9CHPzTvDZC5T9k0jc6gqorXxvNB39dV5ZBcxKAugow@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
This is a message that I wrote and had hoped that all the core devs would
sign on to, but I failed to finish organizing it. So I'll just say it from
myself.
There has been a valuable discussion over the last several months regarding
a hard fork with respect to block size. However the sheer volume of email
and proportion of discussion that is more philosophical than technical has
rendered this list almost unusable for its primary purpose of technical
discussion related to Bitcoin development. Many of us share the blame for
letting the discourse run off topic to such a degree, and we hope that an
appeal for individual self restraint will allow this list to return to a
higher signal-to-noise ratio.
-Please consider the degree to which any email you send is related to
technical development before sending it.
-Please consider how many emails you are sending to this list regarding the
same topic.
This list is not appropriate for an endless back and forth debate on the
philosophical underpinnings of Bitcoin. Although such a debate may be
worthwhile it should be taken to another forum for discussion. Every email
you send is received by hundreds of developers who value their time as much
as you value yours. If your intended audience isn't really the majority of
them, perhaps private communication would be more appropriate.
Thanks,
Alex
[-- Attachment #2: Type: text/html, Size: 1805 bytes --]
next reply other threads:[~2015-08-19 20:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 20:08 Alex Morcos [this message]
2015-08-19 20:11 ` [bitcoin-dev] bitcoin-dev list etiquette Eric Lombrozo
2015-08-19 20:19 ` Eric Lombrozo
2015-08-19 21:19 ` Hector Chu
2015-08-19 21:51 ` Theo Chino
2015-08-19 21:54 ` Nelson Castillo
2015-08-19 22:12 ` Theo Chino
2015-08-19 22:25 ` Gary Mulder
2015-08-19 22:59 ` Btc Drak
2015-08-19 23:13 ` Jorge Timón
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='CAPWm=eVr9CHPzTvDZC5T9k0jc6gqorXxvNB39dV5ZBcxKAugow@mail.gmail.com' \
--to=morcos@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