public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <hearn@vinumeris.com>
To: Mark Friedenbach <mark@friedenbach.org>
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] On bitcoin-dev list admin and list noise
Date: Tue, 29 Sep 2015 19:29:01 +0200	[thread overview]
Message-ID: <CA+w+GKR3CYGZEJ9c9uwuuPvYgQEOH=gUVP_SN4Edfx7-m_p1cA@mail.gmail.com> (raw)
In-Reply-To: <CAOG=w-tDo+87xkB3w=22tZQADi18rbAB0N6m+H5ouwu_pg_+Xg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

There's a simple way to cut down on "noise" that doesn't involve people
shouting OFFTOPIC at each other: the maintainer needs to resolve
discussions by making decisions and saying, this is how Core does it. If
you disagree, go make/join a fork because there's no point in discussing
this any further here. People would get the picture pretty fast.

Wladimir doesn't do this. That is something he should fix. Clearly ending
debates so they don't run in circles forever is a basic management
technique.

Allowing random people to give each other red cards is merely a great way
to piss off users even further, because anyone who objects to a clearly
bone-headed decision will be told they're discussing philosophy and to go
away (this is meaningless).

[-- Attachment #2: Type: text/html, Size: 966 bytes --]

  reply	other threads:[~2015-09-29 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29 15:44 [bitcoin-dev] On bitcoin-dev list admin and list noise Jeff Garzik
2015-09-29 16:38 ` Santino Napolitano
2015-09-29 17:07   ` Mark Friedenbach
2015-09-29 17:29     ` Mike Hearn [this message]
2015-09-29 17:59       ` Pavel Janík

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='CA+w+GKR3CYGZEJ9c9uwuuPvYgQEOH=gUVP_SN4Edfx7-m_p1cA@mail.gmail.com' \
    --to=hearn@vinumeris.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=mark@friedenbach.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