UI module owner

[Benton, Kevin]

> Dennis Melentyev wrote:
> > В пт, 23/06/2006 в 20:28 +0100, Gervase Markham пишет:
> > [...]
> >> Also, for the ease-of-use goal:
> >> do we have any more specific data than
> >> "people complain Bugzilla is hard to use"?
> > Well... Trying to put some more specific data, I'd say:
> > Bugzilla UI (Search page at the first place followed closely by bug
> > entry page) are way too overloaded with controls and lots of them are
> > not intuitive.
> 
> So we ask:
> 
> - Are all the controls necessary?
> - Which controls are used more and which less?
>   (We could get such data by instrumenting bugzilla.mozilla.org)
> - Which ones do people classify as "not intuitive"?
> - Can we fix that by changing the widget used to make them work more
>   like people expect?
> 
> - Does anyone actually do complicated searches, or are 100% of Bugzilla
>   searches merely searches on Subject?
> - If we don't have a page with all the controls on somewhere, how are
>   people going to be able to do those complicated searches?
> 
> > It's getting intuitive when you getting more and more familiar with
> > Bugzilla process, but is a complete mess for a newbie.
> 
> So we ask:
> 
> - Is that page supposed to be used by newbies?
> 
> > IMO the best idea is to have a wizard-like search and bug entry pages,
> > with ability to switch back to current pages when "the wizard" will
> > start abuse you.
> 
> What, like the guided bug entry page we already have? :-)
> 
> > There are also some design/style issues. It doesn't looks
> > sexy/serious/cool/whatever word you know for a big, well-known and full
> > featured application. It looks like knee-knitted helper thingy. This
> > doesn't mean any functionality is missed. It just does not impress from
> > the very first look :)
> 
> So we ask:
> 
> - Which of our personas cares about sexiness/coolness?
> 
> (If the answer is "none", it doesn't mean we can't make it look more
> sexy. It just means that it's not a high priority.)
> 
> > Yet another idea is to have several default (pre-shipped?) skins
> > selectable by USER in his profile:
> 
> This clearly has a maintenance cost, so we ask:
> 
> - Which persona needs this feature, and why?
> 
> > 1. Just current (classic) skin
> > 2. Sexy-dumb-n-bullet-proof-wizardry (anyway, we definitely need one for
> > collecting bug reports from customers, who could not always be smart!)
> 
> We already have customisation mechanisms for this sort of thing; and
> it's not called a "skin".
> 
> > 3. wap-enabled minimalistic
> 
> Which persona needs to access Bugzilla over WAP, and why?

When Bugzilla is used as a support database for network engineers, WAP access allows those engineers to read "all about it" before they get to the site to fix issues.  If we want to cover those users better, we need to make bug displays work well in a WAP environment.  I don't have an immediate *need* for it today, though it would be helpful to me.  I wouldn't count it on a short list of current priorities, personally.

---
Kevin Benton
Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator
AMD - ECSD Software Validation and Tools
 
The opinions stated in this communication do not necessarily reflect the view of Advanced Micro Devices and have not been reviewed by management.  This communication may contain sensitive and/or confidential and/or proprietary information.  Distribution of such information is strictly prohibited without prior consent of Advanced Micro Devices.  This communication is for the intended recipient(s) only.  If you have received this communication in error, please notify the sender, then destroy any remaining copies of this communication.