From: "Jorge Timón" <jtimon@jtimon•cc>
To: Btc Drak <btcdrak@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:21:57 +0200 [thread overview]
Message-ID: <CABm2gDq0FEji=cx9gEjoB3zuT8Vykxw6GgqdDv6GyOJjnd6m2w@mail.gmail.com> (raw)
In-Reply-To: <CADJgMzsPT7n+favkjHSuWh1YGQPZQAFLyOgxu4wDNwXSa_-3og@mail.gmail.com>
On Wed, Aug 19, 2015 at 11:58 AM, Btc Drak <btcdrak@gmail•com> wrote:
> On Wed, Aug 19, 2015 at 9:59 AM, Jorge Timón <jtimon@jtimon•cc> 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.
>
>
> Regarding disruptors, if there are clear rules about what is acceptable on
> -dev, one can simply moderate out offenders. It's absolutely necessary we
> have a forum where we can share and discuss purely academic and technical
> matters. No-one can accuse censorship because all moderation would say would
> be to "take it to the other list". It's essential for all people who are
> developing and maintaining Bitcoin protocol software, or services that rely
> on it. The mailing list used to be very low volume.
I don't disagree with anything you have said. But I think that having
a list specific to Bitcoin Core development will make defining the
"clear rules" easier.
> While we are at it, we should also think about a bitcoin-announce read only
> list which consumers of Bitcoin Core can subscribe for announcements about
> new versions of Bitcoin Core, and any critical warnings. Miners and service
> providers would particularly benefit from this. The list is moderated so
> only say Bitcoin Core commit engineers are allowed to post.
Not sure if necessary but not opposed to this either.
>> One thing that I would like though, is separating Bitcoin
>> Core-specific development from general bips and consensus discussions.
>
>
> The potential downside is too much separation becomes confusing although I
> would not oppose such a change. My own suggestion would be try just a -dev
> and -discuss list and see how that goes first. It used to work well.
> Whatever the case I am very confident we need a general discussion mailing
> list.
As said, that list already exists, it's just that nobody uses it:
http://sourceforge.net/p/bitcoin/mailman/bitcoin-list/
next prev parent reply other threads:[~2015-08-19 10: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 [this message]
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
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='CABm2gDq0FEji=cx9gEjoB3zuT8Vykxw6GgqdDv6GyOJjnd6m2w@mail.gmail.com' \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=btcdrak@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