Return-Path: Delivered-To: apmail-cassandra-dev-archive@www.apache.org Received: (qmail 68848 invoked from network); 25 Mar 2010 20:57:45 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 25 Mar 2010 20:57:45 -0000 Received: (qmail 96281 invoked by uid 500); 25 Mar 2010 20:57:45 -0000 Delivered-To: apmail-cassandra-dev-archive@cassandra.apache.org Received: (qmail 96268 invoked by uid 500); 25 Mar 2010 20:57:45 -0000 Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list dev@cassandra.apache.org Received: (qmail 96260 invoked by uid 99); 25 Mar 2010 20:57:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Mar 2010 20:57:45 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ryan@twitter.com designates 74.125.92.26 as permitted sender) Received: from [74.125.92.26] (HELO qw-out-2122.google.com) (74.125.92.26) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Mar 2010 20:57:40 +0000 Received: by qw-out-2122.google.com with SMTP id 8so2484313qwh.61 for ; Thu, 25 Mar 2010 13:57:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.235.193 with SMTP id kh1mr645801qcb.77.1269550639150; Thu, 25 Mar 2010 13:57:19 -0700 (PDT) In-Reply-To: References: <1269537390.2545.200.camel@erebus.lan> Date: Thu, 25 Mar 2010 13:57:19 -0700 Message-ID: <7c5131fa1003251357j6c80fbf3q25fd4e3729a369c6@mail.gmail.com> Subject: Re: IRC channel(s) From: Ryan King To: dev@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Awesome. -ryan On Thu, Mar 25, 2010 at 10:25 AM, Chris Goffinet wrote: > Eric, > > Great. I fully support this as well, it has been getting a bit noisy :) > > On Thu, Mar 25, 2010 at 10:16 AM, Eric Evans wrote: > >> >> Those of you who participate on IRC have probably noticed that we are >> pretty regularly topping 200 users of late. That is an awesome indicator >> of the projects vitality, but at some point increased traffic results in >> decreased usefulness (at least for some). >> >> As a result, there is a new channel, #cassandra-dev (also on Freenode). >> The idea is that this channel will be restricted to discussion of >> cassandra development only, while the existing channel will continue to >> be the place for support and development *against* cassandra. >> >> In order to make the new channel useful (and to prevent it from >> diminishing #cassandra), I propose the following guidelines: >> >> 1. Anyone is free to join; there are no technological restrictions (i.e. >> it's not moderated or invite-only). >> >> 2. On-topic is limited to the development *of* cassandra. Support >> questions (and basically anything else) are off-topic. >> >> 3. If you are found to be off-topic, you'll be kindly redirected to >> #cassandra (which in IMO is already an awesome resource for this). >> >> 4. Answering an off-topic question is considered off-topic. Goto #3 :) >> >> 5. The Cassandra community is an awesome bunch so I can't imagine that >> one or two iterations of #3 wouldn't be enough, but... >> >> 5a. Repeated violation of the on-topic rule may result in additional >> guidelines that specify decreasing levels of kindness and more forceful >> forms of redirection. :) >> >> The rationale for (1) is that this isn't about exclusivity, we're merely >> trying to increase usability. The rationale for (2) through (5a) is that >> there is no value in having two channels unless some distinction is >> enforced. >> >> Comments? Questions? >> >> -- >> Eric Evans >> eevans@rackspace.com >> >> > > > -- > Chris Goffinet >