public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org, Jeff Garzik <jgarzik@gmail.com>
Subject: Re: [bitcoin-dev] Proposed list moderation policy and conduct
Date: Thu, 15 Oct 2015 00:17:34 +0000	[thread overview]
Message-ID: <201510150017.37007.luke@dashjr.org> (raw)
In-Reply-To: <CADm_WcYnq5sk=wdhqx5UysyS=fu7kRUrixOJC=QfoY5np1ATmA@mail.gmail.com>

On Thursday, October 15, 2015 12:02:21 AM Jeff Garzik via bitcoin-dev wrote:
> 2. If someone asks for help it is because they need it. Politely suggest
> specific documentation or more appropriate venues where appropriate. Avoid
> aggressive or vague responses.

This could get noisy. Clarification that only *development* help is 
appropriate for the list would improve it.

> 2. Conversations should remain focused and on-topic. If you must change the
> topic, start a new thread by changing the topic line of your emails.

Probably should note that entirely new threads should be new messages, *not* 
merely a reply with a changed topic (as changing the topic does not in fact 
start a new thread).

> 4. Off-topic threads will be directed to other venues.

Threads like this one are off-topic, yet we have no obvious other venue for 
it.. :(

> *Disclose potential conflicts*

IMO this seems like not only a waste of time, but also futile for anyone not 
exclusively associated with a single company/organization.

> If you have concerns about someone’s conduct:
> * *On-list*: discussing conduct on-list, either as part of another message
> or as a standalone thread, is always acceptable.

Please no. This is off-topic noise.

Luke


  reply	other threads:[~2015-10-15  0:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15  0:02 [bitcoin-dev] Proposed list moderation policy and conduct Jeff Garzik
2015-10-15  0:17 ` Luke Dashjr [this message]
2015-10-15  0:40   ` odinn
2015-10-15  1:43 ` Justus Ranvier
2015-10-15  8:38   ` odinn

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=201510150017.37007.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=jgarzik@gmail.com \
    /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