From: "Warren Togami Jr." <wtogami@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 12:28:58 -0700 [thread overview]
Message-ID: <CAEz79PohW+Y1bOP1uaF9KWCMdW=dOq+kHxNa0h6pKz3RghDGjw@mail.gmail.com> (raw)
In-Reply-To: <CADJgMzvCdHk1uo5T3rHyvpAYP1W95h7T+uMhA8vjg2BzEPzy2g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2423 bytes --]
FYI, a few developers including Wladimir, Greg, Peter Todd, Pieter, and
Alex Morcos have been discussing what to do about improving the signal
noise ratio on bitcoin-dev list. One proposal similar to this discussion
was to split it into multiple mailing lists. It was pointed out that the
less technical Bitcoin discussion list already existed in the past and
nobody used it. Generally the discussion went away from creating yet
another mailing list and toward instituting an on-topic guidelines for
bitcoin-dev. Gavin, Wladimir, and a few of the others agreed to a simple
few paragraphs written by Alex Morcos. IIRC Wladimir agreed to post it.
Has it been posted yet?
On Wed, Aug 19, 2015 at 11:47 AM, Btc Drak via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> On Wed, Aug 19, 2015 at 3:20 PM, Jeff Garzik <jgarzik@gmail•com> wrote:
> > bitcoin-dev for protocol discussion and bitcoin-core for Bitcoin Core
> > discussion?
>
> Well -dev or both, I dont particularly see a difference at the moment,
> and establishing two lists isnt really going to make a difference so
> long as Bitcoin Core is the reference client, which it is by defacto.
> The risk of having too many lists is interested stakeholders will miss
> a discussions. Normal protocol and core discussions are usually pretty
> low volume in any case.
>
> > As Jorge notes, a general discussion list has existed for a long time
> with
> > little use.
>
> I would suggest it's only because there havent been any rules for -dev
> that would force general discussion over to the bitcoin list. On IRC
> we regularly tell people in #bitcoin-dev they are OT and ask them to
> move to #bitcoin and as a result, -dev remains quite clear of chit
> chat, #bitcoin has a steady stream of general chatter.
>
> We could reduce the OT/noise of bitcoin-dev list considerably by
> offloading the non-technical/academic debate to the bitcoin list. It
> just needs a bit of shepherding. I am more than happy to help out.
> Especially if the list already exists, we should consider making a
> decision now.
>
> Who are the moderators for that list? Do we really want to use
> sourceforge or are there alternatives, like another list on
> linuxfoundation?
>
> ping @Warren.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 3158 bytes --]
next prev parent reply other threads:[~2015-08-19 19:28 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. [this message]
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
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='CAEz79PohW+Y1bOP1uaF9KWCMdW=dOq+kHxNa0h6pKz3RghDGjw@mail.gmail.com' \
--to=wtogami@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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