Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WSVfv-0005IG-Ff for bitcoin-development@lists.sourceforge.net; Tue, 25 Mar 2014 18:02:11 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.128.172 as permitted sender) client-ip=209.85.128.172; envelope-from=etotheipi@gmail.com; helo=mail-ve0-f172.google.com; Received: from mail-ve0-f172.google.com ([209.85.128.172]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WSVfu-0003Vn-N6 for bitcoin-development@lists.sourceforge.net; Tue, 25 Mar 2014 18:02:11 +0000 Received: by mail-ve0-f172.google.com with SMTP id jx11so984238veb.17 for ; Tue, 25 Mar 2014 11:02:05 -0700 (PDT) X-Received: by 10.220.161.8 with SMTP id p8mr56323452vcx.4.1395770525180; Tue, 25 Mar 2014 11:02:05 -0700 (PDT) Received: from [192.168.1.85] (c-76-111-96-126.hsd1.md.comcast.net. [76.111.96.126]) by mx.google.com with ESMTPSA id ga9sm33572595vdc.22.2014.03.25.11.02.04 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Mar 2014 11:02:04 -0700 (PDT) Message-ID: <5331C49B.2000709@gmail.com> Date: Tue, 25 Mar 2014 14:02:03 -0400 From: Alan Reiner User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <20140322084702.GA13436@savin> <20140322150836.GG3180@nl.grid.coop> <20140322190825.GB6047@savin> <532DE7E6.4050304@monetize.io> <20140325122851.GA9818@savin> <20140325134918.GB7929@savin> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (etotheipi[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WSVfu-0003Vn-N6 Subject: Re: [Bitcoin-development] Tree-chains preliminary summary X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Mar 2014 18:02:11 -0000 I would echo the need for some kind of moderation. I believe Peter Todd is an extremely intelligent individual, who has a lot to offer the Bitcoin community. He has a firm grasp of a lot of really deep Bitcoin concepts and his *technical* insight is generally positive. Technically. But the way he communicates on this list is *extremely* corrosive and breeds hostility. It makes it a scary place to discuss things, with frequent, public ridicule of everything posted. I agree that I would rather have a friendly environment to discuss technicals, even if it means losing additional technical insight. People who would explicitly insult other contributors intelligence and character on a public list should be subject to some kind of negative reinforcement. Maybe there's solutions other than outright banning. -Alan On 03/25/2014 01:37 PM, Jeff Garzik wrote: > On Tue, Mar 25, 2014 at 9:49 AM, Peter Todd wrote: >> For someone with 'Chief Scientist' as their job title, I'm surprised you >> think so little of hard evidence and so much of idol worshipping. > Peter, take this unprofessional, personal crap off-list. > > Mike's anecdote of hostility is not an isolated one. Just today, a > bitcore developer commented on "Peter Todd's ..apocalyptic vision > and... negative view on bitcoin" which turned off some other > developers from participating more interactively. > > As I commented on IRC, open source projects are no strangers to people > who simultaneously (a) make useful contributions and (b) turn > potential contributors away with an abrasive or hostile attitude > toward others. It's an unsolved problem in OSS, that I saw for 15+ > years in the Linux kernel community. > > For this list, as Mike suggested on IRC, introducing an openly stated > moderation policy may be the one route. >