[Usability] Re: Proposal + RFC: Improving the Bugzilla layout

[Ryan McDougall <ryan mcdougall telusplanet net>]

On Sat, 2004-03-13 at 16:12 -0700, Elijah Newren wrote:
> I'm not sure which lists to reply to.  I'll include them all this time,
> but can we have all future discussion of this specific topic on
> usability gnome org?  I think that list would make the most sense of the
> 3.  In general, I really like your suggestions.  I have a couple
> comments.

Done!

> 
> On Sat, 2004-03-13 at 14:59, Ryan McDougall wrote:
> <snip>
> > GNOME Software Quality System is the name of the system used to track
> > issues regarding the quality of GNOME software, and should be used in
> > place of "bugzilla".
> <snip>
> > An Item is an entry in the database corresponding to any of the above
> > three cases, previously called a "bug".
> 
> Bugzilla has the ability to automatically convert text such as "bug
> xxxxxx" in reports into a hyperlink to the appropriate bug.  There are a
> couple other places where "bug xxxxx" comes up (an irc bot in #bugs, the
> script name to view bugs is close "...show_bug.cgi?id=xxxxxx", and a few
> others I'm probably forgetting).  In a few of those contexts, 'item'
> seems a little awkward.  Perhaps 'issue'?

As I said to Danilo, I don't propose we kill the word entirely, I just
think it needs to go from the main avenue for reporting bugs. Part of
the problem is the word is too loaded, thats why I broke it up into
three other terms.

> 
> > system with a valid email address, and confidential password. To
>                                          ^^^^^^^^^^^^
> We use http for bugzilla.  Therefore, passwords are sent in plaintext. 
> I'm worried about pretending that things are more secure than they are.

You are correct there. All I was trying to get across is that new users
may be afraid GNOME is somehow a for profit company that might sell
their email address, so assure them that the address is needed for
tracking reasons only.

> 
> > Would you like to register with the software quality system a:
> > 
> > 1. Program Malfunction
> > -To find out what a Program Malfunction is considered a valid
> > malfunction, please click here.
> 
> That parses weirdly.  Did you mean "To find out is considered a Program
> Malfunction..."?  Same for the others below...
> 

Yeah, I wrote that all in one sitting, and I guess I missed that.


> > 2.4. Search Item Database Interaction
> > 
> > To search the GNOME Software Quality System database for current or
> > previous items, please click here.
> 
> I would really like to have a Google-like search interface here.  Just a
> simple box where the user can type in a bunch of terms (e.g. the product
> name and an error message) and bugzilla launches its search.  Also, note
> the link to http://slashdot.org/comments.pl?sid=36557&cid=3935217 from
> http://bugzilla-test.gnome.org/gnome-docs/TODO.docs .  Maybe info like
> this could be put in an How-to-improve-your-search (while using the
> simple interface) kind of page.

I agree with you, but it would likely represent a much greater coding
burden, so I was sticking with simply tidying it up a little.

> 
> There could also be links to obtaining other kinds of searches, such as
> the ones you suggest.
> 
> However, the current query method *must* remain as an option somewhere. 
> It really, really sucks from a UI standpoint but, like emacs or vi, are
> indispensable tools to those that have learned them.

As I mentioned to Danilo, we could link off the main page. Perhaps an
"advanced" section.

> 
> No comments on the editing/showing bug page (i.e. show_bug.cgi)?

I got tired or writing! I wanted to go shopping for dinner. ;)

> 
> Note that we (where we=="Andrew Sobala", for the most part) are really
> close to being able to upgrade GNOME's bugzilla.  Most of this stuff, of
> course, would have to wait until some future upgrade.  However, if you
> see any simple changes that would provide large benefits for the rapidly
> approaching upgrade, we'd love to hear them.  You can take a look at
> http://bugzilla-test.gnome.org .

I'm no web-coding god, but I'd be happy to write the plain-text part of
a new UI. Let me know if I can help.

> 
> Elijah

Cheers,
Ryan