Design Research-Editing Department KIT

About this meeting
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.

Standard Procedure
Review all active projects in descending priority order: TODO: figure out how to keep notes from this meeting synced with notes for individual tasks in User Research's Phabricator Project
 * 1) Check to see if there is a higher-priority project (existing or new)
 * 2) Announce any news, new results, change in status
 * 3) Clarify the scope and definition of the project if needed
 * 4) Review action items from previous meeting and unblock/escalate if needed
 * 5) Identify any problems, blockers, open questions, or new dependencies, and next steps to resolve them
 * 6) Update notes for project, overwriting notes from previous meeting
 * 7) See if the project is done, and if so, mark it done in the notes.

Project Review
 * 1) Support unforeseen VE Launch issues
 * 2) Critical issues only.  no work yet, just standby
 * 3) Talking to Aaron today about his findings, see if any work is needed to follow up on his findings
 * 4) May or may not include any engineering changes
 * 5) Flow: Exploratory Workflows Research (https://phabricator.wikimedia.org/T101331)
 * 6) Doing research in the next few weeks with power users from Jonathan Morgan
 * 7) needs to finish before Wikimania
 * 8) Had a kickoff meeting already
 * Q: Trevor was going to talk to Lila to confirm this priority over exploratory research in Flow general
 * 1) Haven't talked to Lila at that level of detail
 * 2) need to validate our use cases
 * 3) This will validate concepts for power users
 * 4) Have already validated new user use cases
 * 5) how is collab being supported by community by current system of talk pages?
 * 6) making sure that we understand how the current talk pages support the current workflows
 * 7) understand the problems and benefits of current system
 * 8) VE Link Inspector
 * 9) Four outstanding improvements, has been scoped
 * 10) only half is critical
 * 11) Follow up with Nirzar, Design Research, VE Product Owner
 * 12) Lower priority, because Lila: VE should be judged against the Wikitext editor, not other wysywig web editors
 * 13) Search and Discovery content within talk pages and flow (https://phabricator.wikimedia.org/T96997)
 * 14) Research from Abbey for Pau
 * 15) Finished an hour, need another hour of work
 * 16) Content Translation (T76457: [Epic] ContentTranslation - Translation Dashboard, T76448: [Epic] ContentTranslation - Entry Points)
 * 17) Haven't done User Research in last few months
 * 18) fixing bugs, deploying
 * 19) trying to deploy to all languages by the end of this month
 * 20) Met with incoming board member James Heilman, who leads medical translation project, which has complicated workflow
 * 21) Use wiki pages and google spreadsheets
 * 22) we would like to support that workflow directly within the wiki, may be easier and get people more engaged
 * 23) many different
 * 24) Scope of work
 * 25) Pau has started work on this
 * 26) working on prototypes to show at Wikimania
 * 27) overall requirements for research:
 * 28) get current status of translations.  Can get this information at Wikimania
 * 29) Research on "Lists of articles": https://phabricator.wikimedia.org/T96147: learn how communities are organizing campaigns and use to validate or reject current design proposal
 * 30) heterogeneous user base - need user profiles and requirements up to and beyond MVP
 * 31) Can observe people doing translation at Wikimania - what research do we want to do during this?
 * 32) Can we do research in time to inform the prototype shown at Wikimania?
 * 33) Research is useful before, during, or after Wikimania?  Will keep iterating after Wikimania so this is not a hard deadline.
 * 34) Pau has enough information and research to do a basic prototype that can be used for research later
 * 35) Profiles vs persona
 * 36) Profile is a specific person, persona is a synthesis
 * 37) workshop next week on Pragmatic Personas.
 * 38) Could collect profiles at Wikimania that would support Design Research to construct personae
 * 39) Next Step: create a ticket for research
 * 40) VE Mobile Research (independent from Demo effort)
 * 41) Timeline does not allow for design research effort
 * 42) will restart the effort after Wikimania with proper design research effort
 * 43) Must clarify when presented that the Demo does not incorporate any Design Research work

"Backlog" - here are all of the extensions Editing may be responsible for, with current understood priorities bolded
 * Collaboration: Campaigns, ContactPage, Echo, Flow, LiquidThreads, MassMessage, MoodBar, NewUserMessage, Petition, Thanks, WikiLove


 * Language: Babel, cldr, ContentTranslation, DoubleWiki, Josa, Translate, TranslationNotifications, UniversalLanguageSelector


 * Multimedia: CommonsMetadata, GlobalUsage, Graph, ImageMap, ImageMetrics, MultimediaViewer, MwEmbedSupport, PagedTiffHandler, PdfHandler, Score, TimedMediaHandler, timeline (aka EasyTimeline), UploadWizard, VipsScaler, VipsTest


 * Parsing: ParserFunctions, Parsoid, Scribunto


 * VisualEditor: BetaFeatures, Calendar, CategoryTree, CharInsert, Cite, CiteThisPage, Citoid, CodeEditor, CreditsSource, Disambiguator, FlaggedRevs, GeoCrumbs, GettingStarted, GoogleNewsSitemap, GuidedTour, InputBox, Insider, intersection (aka DynamicPageList Wikimedia), LabeledSectionTransclusion, Listings, Math, PageTriage, Poem, ProofreadPage, Quiz, RSS, SandboxLink, SubPageList3, SubpageSortkey, SyntaxHighlight_GeSHi, TemplateData, TemplateSandbox, TocTree, UserDailyContribs, VisualEditor, WikiEditor, wikihiero