Return-Path: Delivered-To: apmail-cassandra-dev-archive@www.apache.org Received: (qmail 34418 invoked from network); 3 Dec 2010 21:08:32 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Dec 2010 21:08:32 -0000 Received: (qmail 5670 invoked by uid 500); 3 Dec 2010 21:08:31 -0000 Delivered-To: apmail-cassandra-dev-archive@cassandra.apache.org Received: (qmail 5585 invoked by uid 500); 3 Dec 2010 21:08:31 -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 5576 invoked by uid 99); 3 Dec 2010 21:08:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Dec 2010 21:08:31 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.213.44] (HELO mail-yw0-f44.google.com) (209.85.213.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Dec 2010 21:08:23 +0000 Received: by ywi6 with SMTP id 6so928559ywi.31 for ; Fri, 03 Dec 2010 13:08:03 -0800 (PST) Received: by 10.100.214.11 with SMTP id m11mr1786734ang.254.1291410483091; Fri, 03 Dec 2010 13:08:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.106.7 with HTTP; Fri, 3 Dec 2010 13:07:42 -0800 (PST) X-Originating-IP: [94.254.38.150] In-Reply-To: <1291407201.7542.379.camel@erebus.lan> References: <0E70B4F9-2A9C-4BF8-B7DF-2C89E90007A8@gmail.com> <1291407201.7542.379.camel@erebus.lan> From: Daniel Lundin Date: Fri, 3 Dec 2010 22:07:42 +0100 Message-ID: Subject: Re: Reducing confusion around client libraries To: dev@cassandra.apache.org Content-Type: text/plain; charset=UTF-8 I think one issue is a lack of liveness on the web end of the project itself. The project web site doesn't feel like the natural focal point it ought to be, and client confusion might (in part) be an artifact of that. The mongodb wiki works alright without much effort because it has a clear structure, and - in all honesty - doesn't look like raw moinmoin. If the Cassandra web site and wiki was on confluence using a common theme, it'd be more coherent and also encourage participation, I think. As for client confusion, I think having a separate page on the wiki for each language/library would work (like the mongodb "language centers", but with ). "What's best for ____" will distill if there's an obvious place for the relevant people to arrive and contribute. I don't think the project itself should be responsible for endorsing or maintaining client, but highlighting/featuring favored options is probably good though - especially for newcomers. /d