Reporting and Analyzing User Experience Issues for FLOSS

[Daniel Schwartz]

Hi all,

I am working on a Special Interest Group proposal for CHI 2010 with  
Alex Faaborg from Mozilla regarding how user experience/user interface  
(UX/ UI) issues are best reported and captured for FLOSS.
If you could take a few moments to answer the following questions by  
the end of this week, that would be very helpful. I totally understand  
if you do not have time due to the holidays and I appreciate any time  
you can give.

If you know of other people who would be willing to fill out this  
questionnaire, please feel free to forward on.

For your following FLOSS project(s)   (please indicate which if you  
are OK to divulge such info):

1- Are UX/ UI issues specifically able to get reported when not part  
of some other issues (meaning UX/UI issues can be reported without  
some crash error or code bug)? (If Yes, please indicate how so and  
always feel free to elaborate)

1A- If Yes to 1, how are reported UX/UI issues vetted?

1B- If Yes to 1, what kind of attributes in your bug tracker are used  
in capturing UX/UI issues?


2- When issues are reported with UX/UI impacts, are the respective UX/ 
UI impacts also able to get reported? (If Yes, please indicate how so  
and always feel free to elaborate)

2A- If Yes to 2, how is UX/UI aspect of the issues vetted?

2B- If Yes to 2, what kind of attributes in your bug tracker are used  
in capturing UX/UI issues?

3- Does your project have any UX folks as part of its core team? If  
so, what is their role in handling UX/UI Issues?

4- Anything else you'd like to comment regarding UX/UI and how such  
issues are handled for your project?

Thanks, Daniel

Daniel Schwartz, Senior Interaction Designer | PH +1.650.506.3516
Oracle Applications User Experience
500 Oracle Parkway MS2op10 Redwood Shores, CA 94065

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/devel/attachments/20091222/586cbca2/attachment.html>