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.

Meeting SOP

Priority list
Latest meeting: 28 July 2015

Action Items
 * Action: make sure there is a Phab ticket for each item on the list and that they are all tagged "#design_research_backlog"

To be Triaged

 * using our pragmatic personas and the future of personas

Project Review

 * 1) Support unforeseen VE Launch issues
 * 2) No news 28 July
 * 3) Flow: Exploratory Workflows Research (T101331)
 * 4) output: short deck of findings; after Wikimania, a more detailed report.  prioritized list of processes.
 * 5) deck finished: https://www.mediawiki.org/wiki/File:Flow_workflow_interviews_-_initial_findings_June_2015.pdf
 * 6) Jonathan working on final report: https://www.mediawiki.org/wiki/Flow/Community_process_workflow_interviews_(June_2015)
 * 7) May interview one more person
 * 8) Or, this person could be the first person for the next round
 * Q: Trevor was going to talk to Lila to confirm this priority over exploratory research in Flow general (30 June: not yet)
 * 1) We think this happened
 * 2) Flow: Exploratory Notifications Research Phab. Ticket?
 * 3) Same pattern of work as Workflows research
 * 4) Danny and Jonathan to continue working together on this
 * 5) VE Education Features
 * 6) Some new work will land this week
 * 7) should we re-test or re-assess education options?
 * 8) Finalized on 2nd approach; Nirzar created a document for that approach, needs design feedback
 * 9) First, a design meeting for education.  Second, a "product" meeting for education to confirm the approach.
 * 10) VE Link Inspector (T101166)
 * 11) Still a few previously planned tasks not yet completed
 * 12) Usability tests should happen after those tasks are done
 * 13) Currently stalled waiting for developer attention; could be weeks of dev work
 * 14) Search and Discovery of content within talk pages and flow (T96997)
 * 15) Completed.
 * 16) Content Translation Translation Dashboard
 * 17) Met at Wikimania.  Discussed priorities for next couple of months.
 * 18) Priority for implementation is article suggestions.
 * 19) ContentTranslation: Translation lists T104353
 * 20) Priority for research is translation lists.
 * 21) Entry points is a low priority currently
 * 22) VE Mobile Research (independent from Demo effort T101333)
 * 23) Got 14 interviews at Wikimania
 * 24) User Research to write up report
 * 25) Also did a survey, got 50 responses, now starting to analyze interview and survey data
 * 26) User Research created a presentation on editing experience for new and casual editors
 * 27) Will publish more broadly
 * 28) Upcoming: change to the behavior of VisualEditor when cursor is near a link
 * 29) "entering into the text of a link becomes a positive action"
 * 30) flagged for Nirzar
 * 31) had been avoiding this for various reasons but appears necessary due to language support issues
 * 32) probably a fairly constrained UI, but we can do some exploration around it
 * 33) Next Step: VE team makes a clear design and shares with Abbey and Nirzar for review
 * 34) Amir would like to review as well
 * 35) New Upload tool in VE and WikiText Editor
 * 36) Kaity was working on this a long time ago, and then Pau, and Pratik is working on it now
 * 37) Current design is similar
 * 38) Will need usability review (first Heuristic, then User-based testing if necessary)
 * 39) Desire is to ship by September 2015

Confirmed that we will continue with current meeting format:
 * current time and attendees as-is
 * take notes in Wikitext in Etherpad, then publish on wiki
 * Wiki page contains current notes; old notes are in wiki page history (note that this is an unusual pattern; may need to clarify or modify it to meet all use cases)