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 14 Jul 2016. Next Meeting 28 Jul 2016.

=New Items for next meeting= Add items here at any time.

= Projects =
 * 1) Gather input for "Edit Review" project.
 * 2) Joe: finished first round
 * 3) Design will schedule at least one more Huggle users and reach out for six to eight more interviewees for prototype testing, deadline for completion of interviews by first week of August
 * 4) Useful session at Wikimania https://wikimania2016.wikimedia.org/wiki/Discussions/Quality_tools
 * 5) Etherpad notes are now consolidated with wiki page
 * 6) New Wikitext Editor
 * 7) New FY2017Q1 goals include "work more strongly on consistent wikitext editor, as beta feature"
 * 8) James: New Wikitext editor will need heuristic evaluation before calling it Beta.  Would also like some structured user testing from new users.  Also looking for power user feedback, as a Beta feature.
 * 9) TODO: Joel to book James, Daisy, JMo, Nick [opt] to book kickoff meeting (to set deadline, scope of work, what are we agreeing to)
 * 10) Conceptual development for Mobile long-form editing
 * 11) James: stalled; next step is to have kickoff meeting but wait until Ed is here in person
 * 12) Ed is going to be working in SF for several months starting Aug 4
 * 13) Also other VE people will be in town
 * 14) Heads-up to to DR team to clear some time in Aug/Sep to work in person with VE people on Mobile editing
 * 15) TODO: Joel to follow up with VE and DR prior to Aug 4 (ASAP) about reserving time
 * 16) The items:
 * 17) https://phabricator.wikimedia.org/T113638 Back and Undo buttons ...
 * 18) https://phabricator.wikimedia.org/T99274 Emphasize VE's save button ...
 * 19) https://phabricator.wikimedia.org/T93325 VisualEditor mobile design
 * 20) Present Mobile research from Wikimania (T106422, T101333)
 * 21) "Learnability of our Content" project (m:Research:Student use of free online information resources)
 * 22) Presented.  https://meta.wikimedia.org/wiki/Research:Student_use_of_free_online_information_resources/Results
 * 23) Another presentation about survey results scheduled for 8/11 at 11:30am PT, contact JMo for an invite (current list – JF/TP/TN/JK/…).
 * 24) JMo will be contacting Trevor when report is ready
 * 25) New Upload tool in VE and WikiText Editor – T40030
 * 26) Volker: Had meeting with Volker, James and Steven LaPorte, Mark H, updated them on our planning
 * 27) Got some ideas from legal team regarding possible simplification of the /legal/ text and possibly unifying it in UploadTool and UploadWizard
 * 28) There will be upcoming actions within that group of people.
 * 29) James: also a question for the product side: how much do we want the tools to force-educate people about copyright?
 * 30) Volker: no current followup for this group; take off this meeting's agenda until further notice from Volker
 * 31) Compact Language Links
 * 32) Amir: Heads up: it was deployed today to a lot of medium-sized wps.  Enabled in almost all projects except largest 20 or so wps.
 * 33) Success = # of clicks on language links going up, % of clicks with relation to number of visits
 * 34) Accessibility Consulting for user standardization
 * 35) Volker: Paused for at least a month
 * 36) Task list / campaigns feature
 * 37) Amir: heads up, no action item
 * 38) During Q1, planning to start building shared task list / campaigns feature for content translation
 * 39) Pau and JMo worked on design recently
 * 40) More research needed?
 * 41) Pau: results are good enough to proceed for now, then more research to evaluate how it works and learn about more specific design issues 2-3 steps ahead.
 * 42) Tracking the statistics of a campaign is quite far ahead.
 * 43) Translation lists/campaignas could be something we want to have research on
 * 44) When?  if all goes well, testable code will be available in September
 * 45) Pau: could use some help [before that] with prototype
 * 46) Action now?  Check in at next meeting.

=Discussion= n/a