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), Echo, ERI, 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 8 Sep 2016. Next Meeting 29 Sep 2016.

=New Items for next meeting= Add items here at any time. = Projects =
 * 1) New Wikitext Editor
 * 2) James: Is now complete [enough to test].  Will get team to sync it over to a test instance server
 * 3) Daisy, please proceed with testing ASAP
 * 4) Recent Changes Pages
 * 5) Joe: need to finalize that design, which requires testing
 * 6) As soon as we can, we need to do research.  Both some classic UX testing, and something a little different: "effectiveness testing".
 * 7) Should have a design to test in the next [day?] from Pau
 * 8) Joe to meet with Daisy, Pau, Aaron, Benoît (Nick as backup) to plan
 * 9) Nick: can we incorporate results of ERI before finalizing this design?  response: yes.
 * 10) Edit Review Improvements
 * 11) Nick: Is ERI notes done?
 * 12) JMo: Nothing else scheduled, but I do need to collect the transcripts and interviews.  Will try to do that before end of day Friday.
 * 13) Supporting Templates When Translating Articles ("STWTA")
 * 14) Pau: Met with Daisy to go through designs
 * 15) next step is to do testing sessions — Daisy is already ready to proceed
 * 16) Accessibility Consulting for user standardization
 * 17) Volker: Still paused
 * 18) Task list / campaigns feature
 * 19) Pau: Don't think we need research for that for at least a couple of months.
 * 20) check again in October
 * 21) Conceptual development for Mobile long-form editing
 * 22) Paused.
 * 23) On the border between evaluative and generative.

=Discussion=
 * 1) continue existing DR:Editing meeting or set up individual team (VE, Collab, CX, etc) 1:1 meetings with Daisy
 * 2) Proposal: continue with this meeting as is
 * 3) Daisy attends and covers evaluative DR.  Is involved in generative work, however:
 * 4) JMo is lead for topics involving generative DR; is otherwise optional for this meeting
 * 5) Need to notify him ahead of time if he's needed for meeting (Daisy will be able to help with this)
 * 6) James: LA is manager of Daisy's team; maybe she should be invited
 * 7) James: this is bi-weekly because weekly would be overloading for full DR.  But if it's just Daisy, should we meet weekly?
 * 8) Joel: Purpose of meeting is to be minimum forum for DR/Editing coordination and planning.  People can talk directly to Daisy without waiting for the meeting, but the meeting guarantees communication with max 2-week delay.  So maybe don't need it weekly?
 * 9) Daisy: with reading I [check in every week?]
 * 10) James: and then this meeting becomes [?]
 * 11) JMo: would remain useful for me for getting a glimpse at what's happening [in DR/Editing]
 * 12) James: monthly editing pitch meeting might be more useful
 * 13) Pau: talking about research needs of 4 groups.  Should aim for priorities not to change from week to week.  Daisy would benefit from some stability on priorities.  Fine not doing prioritization every single week.
 * 14) Daisy's proposal:
 * 15) maybe keep this meeting for prioritization, make it every 3 or 4 weeks.
 * 16) Use remaining time in this meeting to share results.
 * 17) Book 1-1s with Daisy.
 * 18) Joe: 3 weeks sounds good
 * 19) TODO: Joel to change meeting to every 3 weeks
 * 20) Daisy: there is now a Phabricator board Editing-UX-Research
 * 21) James: can we replace the Mediawiki list (with etherpad live editing) with the Phabricator board
 * 22) Joel TODO follow up in email on practical ways to do that