public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Eric Lombrozo <elombrozo@gmail•com>
To: Alex Morcos <morcos@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] bitcoin-dev list etiquette
Date: Wed, 19 Aug 2015 13:11:24 -0700	[thread overview]
Message-ID: <E22C8A75-BE96-4BBE-8211-BD426D874846@gmail.com> (raw)
In-Reply-To: <CAPWm=eVr9CHPzTvDZC5T9k0jc6gqorXxvNB39dV5ZBcxKAugow@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2143 bytes --]

Alex,

With all due respect, right now the biggest challenge facing Bitcoin is not technical but political. I would love to see this list go back to technical discussions, but unfortunately, until this political stuff is resolved, even technical discussion is purely philosophical as there’s little chance of actually making good progress on consensus…which in a space where everything depends on consensus pretty much makes everything else moot.

> On Aug 19, 2015, at 1:08 PM, Alex Morcos via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> 
> 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
> 
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


[-- Attachment #1.2: Type: text/html, Size: 3310 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]

  reply	other threads:[~2015-08-19 20:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 20:08 Alex Morcos
2015-08-19 20:11 ` Eric Lombrozo [this message]
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=E22C8A75-BE96-4BBE-8211-BD426D874846@gmail.com \
    --to=elombrozo@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=morcos@gmail$(echo .)com \
    /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