Re: [Usability] UI Review

[Gregory Merchan <merchan phys lsu edu>]

On Fri, May 30, 2003 at 01:11:09PM +0200, Murray Cumming Comneon com wrote:
> I'm thinking of taking over or encouraging the UI Review process. I don't
> have access to IRC, and have very little hacking time, so I would just try
> to organise things a bit.
> 
> I guess we need to at least know the ui-review status of each module. So, to
> start with, are there any modules that do _not_ need any more UI Review?

GEdit. As I recall, Paolo was great about participating in UI review and
that is very good. However, at least when I was online, GEdit tweaking
seemed to take the most time. I feel other important modules did not
get enough time and may have been missed entirely. I don't seem to recall
any other module maintainers being online for UI review. It should not 
be surprising if review is more extensive for a module with a participating
maintainer.

> Does anyone have any particular ideas for the UI review process? Please keep
> it simple and concise.

Keep track of the kinds of errors corrected. (Or distill that from logs.)
If an error is common, then the HIG may need revision.
Also, common errors may be reparable by tools like `sed`.

Specify the program version before review. Screenshots were often used
because not everyone had an up-to-date version. Announce this in advance
so people have time to get the correct version.

Cheers,
Greg