From: Gavin <gavinandresen@gmail•com>
To: Peter Todd <pete@petertodd•org>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Three Month bitcoin-dev Moderation Review
Date: Sat, 23 Jan 2016 16:38:44 -0500 [thread overview]
Message-ID: <3B18134A-3E3A-4A98-ADD3-9F5E8600047E@gmail.com> (raw)
In-Reply-To: <20160123205953.GA22494@muck>
> On Jan 23, 2016, at 3:59 PM, Peter Todd via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> I would extend this to say that the technical explanation also should
> contribute uniquely to the conversation; a +1 with an explanation
> the last +1 gave isn't useful.
Yes, comments should contribute to the discussion, with either technical discussion or additional relevant data. I think a +1 like the following should be encouraged:
"+1: we had eleven customer support tickets in just the last week that would have been prevented if XYZ.
Jane Doe, CTO CoinBitChainBasely.com"
next prev parent reply other threads:[~2016-01-23 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 0:50 Rusty Russell
2016-01-21 2:25 ` xor
2016-01-21 4:35 ` Dave Scotese
2016-01-21 5:00 ` Rusty Russell
2016-01-21 4:44 ` Rusty Russell
2016-01-23 5:33 ` xor
2016-01-23 20:59 ` Peter Todd
2016-01-23 21:38 ` Gavin [this message]
2016-01-24 1:06 ` Dave Scotese
2016-02-09 23:24 ` David Vorick
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=3B18134A-3E3A-4A98-ADD3-9F5E8600047E@gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=pete@petertodd$(echo .)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