From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id A7A15308 for ; Thu, 15 Oct 2015 00:18:13 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 5880510E for ; Thu, 15 Oct 2015 00:18:13 +0000 (UTC) Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:61b6:56a6:b03d:28d6]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 3DD2438A4C62; Thu, 15 Oct 2015 00:17:39 +0000 (UTC) X-Hashcash: 1:25:151015:bitcoin-dev@lists.linuxfoundation.org::8CYDD8z0jHBWwVa9:efPof X-Hashcash: 1:25:151015:jgarzik@gmail.com::jXy27WlcR5svpoMY:nWnm From: Luke Dashjr To: bitcoin-dev@lists.linuxfoundation.org, Jeff Garzik Date: Thu, 15 Oct 2015 00:17:34 +0000 User-Agent: KMail/1.13.7 (Linux/4.1.6-gentoo; KDE/4.14.8; x86_64; ; ) References: In-Reply-To: X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201510150017.37007.luke@dashjr.org> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Proposed list moderation policy and conduct X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2015 00:18:13 -0000 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=20 appropriate for the list would improve it. > 2. Conversations should remain focused and on-topic. If you must change t= he > 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= *=20 merely a reply with a changed topic (as changing the topic does not in fact= =20 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= =20 it.. :( > *Disclose potential conflicts* IMO this seems like not only a waste of time, but also futile for anyone no= t=20 exclusively associated with a single company/organization. > If you have concerns about someone=E2=80=99s 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