Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C6B159CA8 for ; Tue, 17 Apr 2012 00:06:17 +0000 (UTC) Received: (qmail 47141 invoked by uid 500); 17 Apr 2012 00:06:17 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 47112 invoked by uid 500); 17 Apr 2012 00:06:17 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 47104 invoked by uid 99); 17 Apr 2012 00:06:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Apr 2012 00:06:17 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bchesneau@gmail.com designates 209.85.217.180 as permitted sender) Received: from [209.85.217.180] (HELO mail-lb0-f180.google.com) (209.85.217.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Apr 2012 00:06:11 +0000 Received: by lbbgp3 with SMTP id gp3so2914953lbb.11 for ; Mon, 16 Apr 2012 17:05:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=AFUYSOWRoEv6d8VdwdcwvJ9dbH4s3GI1n1J3a5X4Tdk=; b=IZ5ZOV5UEQgWxTiXIunfU0kkWfykB6lCGcXINuxBGAIa1cSUhPev7q3XHU5iAjCqNI sQhnujRxYDaXnrwT4X10e4JXBr0XLlPq2kjNq1DFvxyTM5LeEH1kUzGpMjVGvrp/9ScE JXyGmvAvU50RIMkFTBfM9RaMCo0gofi1gY/NSnLVH504FrvuYzUyx3/YSHO1EdEg2IYP nBOdMjCVijlerEGGbsDU1WQWx9gHhOjZkN1wK7xNws4xyvsuvCDIAzRouXQcNiZiLvK/ HXRr7KJzLR4dLfiZkOeUVVSNytxMovSMfGPs9yIJC3v5xInI2P/bqDdMxviXTW5ypWm6 0OaA== MIME-Version: 1.0 Received: by 10.112.99.41 with SMTP id en9mr5821081lbb.5.1334621150031; Mon, 16 Apr 2012 17:05:50 -0700 (PDT) Received: by 10.112.20.234 with HTTP; Mon, 16 Apr 2012 17:05:49 -0700 (PDT) In-Reply-To: References: <8A7F076D-84EC-433E-8160-EC5838E5FEBF@dionne-associates.com> <4F8C6F81.1030205@83864.com> <4F8C7DC6.1080306@meetinghouse.net> Date: Tue, 17 Apr 2012 02:05:49 +0200 Message-ID: Subject: Re: website & jira From: Benoit Chesneau To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Apr 17, 2012 at 1:07 AM, Noah Slater wrote: > Some comments. > > "I wish it could have been discussed before too." > > Sorry to jump on you here Beno=EEt, but this is not the way CouchDB works= . > > And every time I see this unhealthy attitude raise its ugly head, I am > going to stamp on it. > > CouchDB operates a culture of trust. We trust that community members are > going to act in the interests of the project. Whatever you want to do, ju= st > have at it. It is easier to ask for forgiveness than it is to get > permission. > > The only rule to that is: don't be a berk! > > This permission culture that we seem to have fostered in recent years is = a > blight on the project, and it is my hope that we can use recent events to > shake it off. But we need to start by stamping it out where ever we see i= t. > Setting an example. > > The website was not discussed prior to the launch, because I can tell you > right now, with my hand on my heart, it would never have seen the light o= f > day. We'd still be sat here, with a 5 year old site, moaning about it. > Because everyone thinks they know how to design, and everyone has an > opinion, and the thing would've been debated until it was killed. > > You can imagine how much I flinched when I read this: "Does anyone think = it > would be a good idea to list the proposed changes/issues to/with the site > and then have the community vote on them?" > > Not picking on you here Jonathan, but it's a good example of what I am > talking about. > > Voting on the design of the site is probably THE worst idea possible. > So. I never suggested that. To be honest I don't care about the color, I don't care about the font used. I don't care to have a pretty website or not. I'm not sure I like that one. It's trendy for sure. Not my problem here either. What I care on the other hand, is about the content, and the information in. What could have been discussed, and may be fixed in the future is which information is important. Who are we targeting. There was some mails about that on the ml sometimes ago without real decision on that. Again I'm not talking about a vote or whatever. At the end someone has to take a decision. The one that took the lead for any reason. I'm pretty sure the website will need some edits (and again i'm not speaking about design) in near future following recent discussions. But it wasn't the topic of my mails. What I care now, is that i'm not inclined to use the site because I don't find the information easily like I used too. And I've found the same feedback from some persons around. I listed the points previously. I'm now worried that we can't even suggest something is wrong. It looks like it for sure. Trust? `Trust` works in both way. And if you don't trust someone enough to think you can't discuss about that thing, there is a problem. I personally trust you even if we never met and others in the team. ANd pretty sure that we all know where to stop between bikesheeding and the rest. Am I right, dunno. That's it. Now to list my issues with the website: - easy access to the support (tickets) - reading the text is difficult - making some links more obvious: mailing list web browsing If I'm the only one to find issues about that fine. I will try to bookmark the links I need even if I dislike to work that way. - beno=EEt