VisualEditor/Design meetings/2015-05-11

Update on VE usability testing

 * Should be ready for testing by tomorrow
 * Want to add additional text to the generate context menu
 * Will test without that
 * Nirzar will file a task

Process questions

 * Follow-up: should tasks be created when there are issues with implemented design not matching spec?
 * New task?
 * comment in existing task?
 * email?
 * other?
 * Nirzar’s feedback loop will be shorter now that he’s embedded
 * (but how is it visible to anyone else w/o asking Nirzar or James)
 * Definition of "done"
 * Who declares a story Done, the Product Owner or the customer?
 * Is Nirzar the customer in this case?
 * Joel will add issue to the process report: who can edit what in Phab? Not much clarity, which makes it harder for external people to participate via Phab. Can the designer reopen a task over implementation details?

What’s next in usability improvements for VE in usability (after usability testing)?

 * labels inside citation tool
 * fixing link inspector
 * have 4 things to change; 2 are already done
 * two usability tasks lined up in Phab, new features
 * what major task should be next: guided tour or mobile editing?
 * Question is really what the development priority is; design is already ongoing for both
 * How do we make that decision?
 * In the past, James/Trevor have led this decision
 * Joel will put this issue in the process report as a “big change” priority
 * Joel will put this question on launch meeting agenda
 * should we do a full-scale guided tour or more limited, discrete help popups?