Design Research-Editing Department KIT

This is a bi-weekly meeting between the Design Research team and the leads of the Editing Vertical teams (Collaboration (Flow), Wikitext, VisualEditor, mobile editors, Multimedia, Content Translation, Upload Wizard) to coordinate and plan Design Research work. This meeting is intended to clarify priorities, define work, schedule work, manage conflicts, share findings, and ensure Design Research and Editing stay aligned in their work. See the Meeting Standard Operating Procedure.

Last meeting 19 Jan 2016. Next Meeting 2 Feb 2016.

New topics for next meeting:
Add new topics here between meetings.

= Project Status =
 * 1) Usability Testing for Education Features T108620
 * 2) Daisy - waiting to hear from James when New User Education and Single Edit Tab are ready for testing.
 * 3) Don't need accounts assuming the test can be run on test wiki
 * 4) TODO: James to clarify
 * 5) Paying for testers
 * 6) No update from JMo
 * 7) New Upload tool in VE and WikiText Editor – T40030
 * 8) A/B test (T120867) inconclusive.
 * 9) check for further action
 * 10) Content Translation – Translation Dashboard
 * 11) Completed third and final testing session.
 * 12) Got interesting feedback but third participant was not perfectly qualified; JMo may schedule another session.
 * 13) UX Testing Notifications
 * 14) Pau: Completed second round of testing last Tuesday.  https://meta.wikimedia.org/wiki/Research:Cross-wiki_notifications_user_research
 * 15) Pau is planning prototype for next round of testing
 * 16) Joe: Who writes the script for testing?  Daisy: Usually DR, but Pau does it sometimes
 * 17) Amir: Joe and Pau and Benoit and Nick worked on refreshing the terminology for Notifications, which is great.  Are you testing the terminology as part of this?
 * 18) Joe: It comes up in testing but we don't focus on it specifically
 * 19) Pau: new prototypes will use new language
 * 20) Joe: Waiting for JMo to plan third round. (Rounds test different aspects, not necessarily the same thing three rounds in a row)
 * 21) TODO: Joel to notify Roan that Notification page design not expected to be finalized by end of January due to the schedule of testing
 * 22) "Learnability of our Content" (was "   Concepts in broad user interaction") project
 * 23) No Update (JMo)
 * 24) Present Mobile research from Wikimania (T106422, T101333)
 * 25) No Change 19 Jan 2016.
 * 26) Fix Feedback Tool UI Problems [T100011], T86956
 * 27) No change 19 Jan 2016.
 * 28) Make plan to deal with known usability issues in VE Mobile
 * 29) No change 19 Jan 2016.

=Discussion=
 * Amir asked about different times due to conflict - failed to find any other working time when we tried to move it in Nov/Dec 2015.
 * Amir: Regarding content translation, we don't have big design changes coming up, but I want to ask Pau whether it will be relevant to add Pau's design work around Abuse Filter?
 * Pau: Depends on what we want to learn. We are measuring errors produced by users being hit by Abuse Filter.  That would guide our understanding of how things are working.  If we want to understand specific problems, we can do some testing.  Not sure if that will involve using the current tool, prototypes, or both.
 * Joe: Does the filtering involve an interaction with the user or does it happen after the fact, with alerts?
 * Pau: Suppose I'm translating an article from English to Spanish. It includes a link to Youtube.  I add paragraphs and publish it.  Suppose that es.wp has a filter that considers Youtube links as spam.  I get a weird message preventing me from publishing.  Since I just adapted the content, I may not even realize where the Youtube link is, or that I have to find it and remove it.  Lots of steps, and we can't modify the abuse filter, since it's wiki-specific.  Some steps we can take, highlighting information, messaging, to make it more clear.
 * Daisy: Research Team might be on off-site in two weeks.