From: Bryan Bishop <kanzure@gmail•com>
To: "Jorge Timón" <jtimon@jtimon•cc>, "Bryan Bishop" <kanzure@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Separated bitcoin-consensus mailing list (was Re: Bitcoin XT Fork)
Date: Wed, 19 Aug 2015 19:21:06 -0500 [thread overview]
Message-ID: <CABaSBawX26u9XJRPdoYnPpSgG85P4pr917fjUuxhmPnO8Ek5rw@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDpYdBjyCB=Dor0eE-FdPv9PbVXzWyJf0BPyQ4SDm9VznQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
On Wed, Aug 19, 2015 at 3:59 AM, Jorge Timón <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> Apparently that existed already: http://sourceforge.net/p/bitcoin/mailman/
> But technical people run away from noise while non-technical people
> chase them wherever their voices sounds more loud.
>
FWIW, and I mentioned this opinion in #bitcoin-dev on IRC, but I am
perfectly fine with receiving everything through a single mailing list. I
used to read the Wikipedia firehose of recent edits because I thought
that's how you were supposed to use the site. Edits per second eventually
reached beyond any reasonable estimate of human capacity and then I
realized what was going on. Any sort of "glorious future" for bitcoin with
hundreds of millions of users will also see this problem for future
developers, even if only 0.1% of that population are money-interested
programmers then that's 100,000 programmers to work with. I would never
want to turn off this raw feed. Having said that, I am somewhat surprise
that nobody has taken to weekly summaries of research and development
activity. Summarizing recent work is a valuable task that others can engage
in just by reading the mailing list and aggregating multiple thoughts
together, similar to release notes. I was also expecting to see something
like "individual developer's summaries of things they have found
interesting over the past 30-90 days or past year" digging up arcane
details from the mailing list archives, or more infrequent summaries of the
other smaller batched review emails. Digest mode mailing list consumption
is often recommended to those who are uninterested in dealing with low
signal-to-noise, but I suspect that summarizing activity would be more
valuable for this community, especially for the different cognitive niches
that have developed.
- Bryan
http://heybryan.org/
1 512 203 0507
[-- Attachment #2: Type: text/html, Size: 2468 bytes --]
prev parent reply other threads:[~2015-08-20 0:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 8:59 Jorge Timón
2015-08-19 9:58 ` Btc Drak
2015-08-19 10:21 ` Jorge Timón
2015-08-19 14:20 ` Jeff Garzik
2015-08-19 18:47 ` Btc Drak
2015-08-19 19:28 ` Warren Togami Jr.
2015-08-19 23:16 ` Dave Scotese
2015-08-19 23:44 ` NxtChg
2015-08-20 0:14 ` Jorge Timón
2015-08-20 0:21 ` Bryan Bishop [this message]
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=CABaSBawX26u9XJRPdoYnPpSgG85P4pr917fjUuxhmPnO8Ek5rw@mail.gmail.com \
--to=kanzure@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jtimon@jtimon$(echo .)cc \
/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