Difference between revisions of "HowTo Request User Experience Assistance"

From Apache OpenOffice Wiki
Jump to: navigation, search
m
m
Line 8: Line 8:
  
  
* Why work with UX?
+
* When '''''do''''' you need UX?
 
+
* When do you need UX?
+
 
** High-impact features or issues, e.g. ...
 
** High-impact features or issues, e.g. ...
 
*** ...changes to the "initial" user interface (e.g. main menu, tool bars, shortcuts),
 
*** ...changes to the "initial" user interface (e.g. main menu, tool bars, shortcuts),
Line 16: Line 14:
 
*** ...changing default settings affecting either of the two above
 
*** ...changing default settings affecting either of the two above
  
* When do you not need UX?
+
 
 +
* When do you '''''not''''' need UX?
 
** Guideline available
 
** Guideline available
 
*** [[User_Interface_Guidelines|OOo UI guidelines & specs]]
 
*** [[User_Interface_Guidelines|OOo UI guidelines & specs]]
Line 22: Line 21:
 
** Lower-impact features or issues, e.g. ...
 
** Lower-impact features or issues, e.g. ...
 
*** ...changes to "well hidden" parts of the UI, like the "more"-part of a rarely used dialog
 
*** ...changes to "well hidden" parts of the UI, like the "more"-part of a rarely used dialog
 +
 +
 
* How to contact UX / how to request assistance
 
* How to contact UX / how to request assistance
 
** send an e-mail to mailto:discuss@ux.openoffice.org (later to be changed into mailto: issues @ ux.openffice.org)
 
** send an e-mail to mailto:discuss@ux.openoffice.org (later to be changed into mailto: issues @ ux.openffice.org)
 +
 +
 
* What UX needs from you
 
* What UX needs from you
 
** issue ID
 
** issue ID
Line 29: Line 32:
 
** if your change affects the UI, ideally provide a screen shot of your patch in action
 
** if your change affects the UI, ideally provide a screen shot of your patch in action
 
** optionally: provide a URL to an install set (preferably Windows, but Linux/MacOSX/Solaris work, too) including your patch
 
** optionally: provide a URL to an install set (preferably Windows, but Linux/MacOSX/Solaris work, too) including your patch
 +
 +
 
* What can you expect from UX?
 
* What can you expect from UX?
 
** initial response within one week
 
** initial response within one week

Revision as of 11:22, 14 June 2007

ux-ooo-logo-rgb-129-61.png

ux.openoffice.org

Quick Navigation

Team

Communication

Activities


DISCLAIMER: This is an initial draft of a general guidance on how developers shall work with UX. Please feel free to comment on it, suggest changes, or ask questions about it at any time. As soon as a first stable version emerges, I will announce this on more public channels.

Thanks, --Lutz Hoeger 19:17, 11 June 2007 (CEST).



  • When do you need UX?
    • High-impact features or issues, e.g. ...
      • ...changes to the "initial" user interface (e.g. main menu, tool bars, shortcuts),
      • ...work flow changes (e.g. introducing new work flow steps, dialog boxes, error messages),
      • ...changing default settings affecting either of the two above


  • When do you not need UX?



  • What UX needs from you
    • issue ID
    • short description of the change & why you changed it
    • if your change affects the UI, ideally provide a screen shot of your patch in action
    • optionally: provide a URL to an install set (preferably Windows, but Linux/MacOSX/Solaris work, too) including your patch


  • What can you expect from UX?
    • initial response within one week
    • a name / OOo issuetracker ID of a UX engineer to assign the issue to
    • alternatively, the answer may be "no resources, go with your best guess"
    • if you don't hear anything from UX within two weeks, just proceed
Personal tools