From dev-return-3700-apmail-bloodhound-dev-archive=bloodhound.apache.org@bloodhound.apache.org Wed Nov 6 16:55:26 2013 Return-Path: X-Original-To: apmail-bloodhound-dev-archive@www.apache.org Delivered-To: apmail-bloodhound-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 2026610E28 for ; Wed, 6 Nov 2013 16:55:26 +0000 (UTC) Received: (qmail 74148 invoked by uid 500); 6 Nov 2013 16:55:25 -0000 Delivered-To: apmail-bloodhound-dev-archive@bloodhound.apache.org Received: (qmail 74022 invoked by uid 500); 6 Nov 2013 16:55:21 -0000 Mailing-List: contact dev-help@bloodhound.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@bloodhound.apache.org Delivered-To: mailing list dev@bloodhound.apache.org Received: (qmail 73998 invoked by uid 99); 6 Nov 2013 16:55:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Nov 2013 16:55:20 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [95.130.13.75] (HELO smtp.core-hosting.net) (95.130.13.75) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Nov 2013 16:55:14 +0000 Received: from mail.core-hosting.net (unknown [10.0.0.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.core-hosting.net (Postfix) with ESMTPSA id 05BC1AA5834 for ; Wed, 6 Nov 2013 17:54:53 +0100 (CET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_5a60104d17239e764c853348f611fc6e" Date: Wed, 06 Nov 2013 18:54:52 +0200 From: Olivier Mauras To: Subject: Re: First installation... my humble review Reply-To: Mail-Reply-To: In-Reply-To: References: <4dc2728247a98909ac85ae26528ab7bc@core-hosting.net> Message-ID: <41c243299b9ec059fa3be6c083fd9dc3@core-hosting.net> X-Sender: olivier@mauras.ch User-Agent: Roundcube Webmail/0.7.2 X-Virus-Checked: Checked by ClamAV on apache.org --=_5a60104d17239e764c853348f611fc6e Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=UTF-8 On 2013-11-06 18:43, Ryan Ollos wrote: > On Wed, Nov 6, 2013 at 7:06 AM, Olivier Mauras wrote: > >> Hello, I met Gary Martin this morning on #trac and discussing quickly about the look & feel of Bloodhound i ended up installing it on a test server. Here's a compilation of the points that i find "lacking": 1/ Blocking points for a production adoption - indeed that's only my opinion * Product owner should automatically have admin rights to this product. I plan on using Bloodhound in a multi product / multi users setup. I can't imagine it working without delegating the product admin rights to their owners * Products should be able to have their own source repo If rights are delegated, I don't see any valid reason for owners to not be able to add their own repos 2/ Confusing points * Tickets tab being the dashboard Being a new user, I find it really confusing for the "Tickets" tab for being the dashboard and consequently the only access to products list. It would be way more intuitive - and faster - to keep the products list dropdown at the left of the breadcrumb. * Not knowing where you are This is indeed linked to the previous point, wiki and source pages don't show the product in breadcrumb 3/ Eye candy * Source browser CSS may not be the easiest to read All lines to the same color make it difficult to catch things Age color highlight is too light and/or too close in colors * There's place on the mainnav tabs As there's place available and that one can enable timeline and roadmap from base.ini why not add them to mainnav() to not have then in "More" tab? 4/ Graphic glitch https://bh-demo1.apache.org/products/%40/roadmap [1] As you can see here milestone bars are not displaying correctly. I think that's all I have for now, thanks for taking time to read me. Olivier > > Thank you for the feedback. > * Your points about the navigation being confusing are relate-able. We > need to improve in this area. > * You say that all lines in the source browser are the same color. This > could be due to Pygments not being installed correctly. Do you have a > "Syntax Highlighting" tab on the prefs page (/prefs/pygments)? It could > also be due to the mimetype on a file being set to text/plain. The mimetype > should be autodiscovered for common file extensions if not set on the file. > * I agree that we should offer more flexibility for users to customize the > mainnav. This will be improved in #636. > * The roadmap needs a Bootstrap template, which is why it is not visually > appealing. Some would say that the Roadmap is replaced by the Dashboard, > but I think we should make the Roadmap usable for those that choose to use > it. > > https://issues.apache.org/bloodhound/ticket/636 Syntax highlighting is ok, i'm talking about the "inside directory" browsing. Having all lines to the same colors makes it less easier to catch things when browsing a big file/directory list. http://trac.edgewall.org/browser [2] for example default trac alternate line colors. Links: ------ [1] https://bh-demo1.apache.org/products/%40/roadmap [2] http://trac.edgewall.org/browser --=_5a60104d17239e764c853348f611fc6e--