AMO: Difference between revisions

2,125 bytes added ,  21 April 2005
Line 330: Line 330:
* '''Works''' - Does the extension do its job as the author describes?
* '''Works''' - Does the extension do its job as the author describes?


If testing a theme, don't forget to check that the author has included a suitable preview image. If not, check that the other requirements are fulfilled (the theme and the application work as required and the theme installs/uninstalls properly). Add a comment to the effect that previews are required for all themes on umo and then deny the approval request, asking them to resubmit their theme complete with a preview.
=== Testing Themes ===
The procedure to start testing a theme is the same as the one for extensions. Testing themes usually (but not necessarily) takes lesser time.
 
While testing a theme, don't forget to check that the author has included a suitable preview image ('''a preview image is mandatory'''). If not, check that the other requirements are fulfilled (the theme and the application work as required and the theme installs/uninstalls properly). Add a comment to the effect that previews are required for all themes on umo and then deny the approval request, asking them to resubmit their theme complete with a preview.
 
'''Things to look for'''
* ''Completeness:'' Examine **all** the toolbars, menus, menu options, throbber, icons etc. to make sure that nothing is missed out.
* ''Look:'' While looking for completeness, also look at the color combinations and the contrast. Commend the author for the choice of colors/contrast and the visual elements.
* ''Consistency:'' A theme is, well, a theme! See if the visual elements are consistent across menus and toolbars. Do the colors, dialogs and menus look the same across different UI options? This is the most important aspect of a theme. Without consistency, it wouldn't be a theme!
* ''Fit:'' By fit, I mean the display of all elements within specific boundaries. This is relevant for menus and dialogs - check to make sure that all the UI elements fit within the default boundaries and do not appear "clipped". If anything's clipped and/or if resizing is required to see it completely, make a note of it and request the author to change it - clipped dialogs/menus are an annoyance to users and could lower the impression of quality that the theme makes on the user - in such cases, it's better to deny the theme and request the author to correct these.
* ''Install/Uninstall:'' This is the same as the check done for extensions.
 
== Approval, Denial and Comments ==
* ''Approving a theme/extension:'' Thank the author for the time and effort they have put in. Remember that they're enhancing the usefulness and the appeal of the products!
* ''Denying a theme/extension:'' Be polite in pointing out the flaws. Provide suggestions as to what they could or should do before re-submitting it and request them to re-submit it. It's also a good idea to tell the author what you liked about the extension/theme even though you've denied it.
* ''Comments:'' Your comments to the author go to a *real person* - keep that in mind while you go about reviewing hundreds of extensions/themes. :)


=== Bugzilla ===
=== Bugzilla ===
9

edits