Media meeting recap – June 22, 2017

Overview

This post is a summary of the latest weekly Media component meeting, which took place in #core-media on Slack, on Thursday, June 22 at 18:00 UTC. The purpose of these meetings are to move priority tasks forward, provide feedback on issues of interest, and review media focused tickets on Trac.

Agenda:

  1. Media Priorities for 4.9
  2. Preparing for Gutenberg
  3. Improving bug triage/review

Attendees:
@joemcgill, @omarreiss, @adamsilverstein, @karmatosed, @mikeschroder, @mapk, @desrosj, @sergeybiryukov, @blobfolio, @afercia, @saracannon.

Transcript: https://wordpress.slack.com/archives/C02SX62S6/p1498154451224688

Media Priorities for 4.9

We spent the first part of the meeting collecting possible priority tickets for the WP 4.9 release cycle. Here are the list of tickets that were identified (in order of suggestion), but if you have additional tickets to nominate, please leave a comment on this post. Note that tickets that line up with the focuses of improving editing, site customization, and the REST API are more likely to get attention.

  • #39647: Make media upload “HTTP error.” more user-helpful
  • #40439: Save progress of intermediate image creation after upload
  • #37840: Optimize full size images
  • #30634: Media: Image cropping on mobile devices does not work
  • #17247: Crop tool is automatically selected when editing an image
  • #30155: Fix crop image functionality within edit flow
  • #39553: Use REST API endpoints for Plupload backend

Preparing for Gutenberg

During the WordPress Community Summit, several of us began having early conversations about what comes next for the wp.media UI once Gutenberg is released. Gutenberg is currently making use of the existing media flows. In coming months, there will no doubt be more conversations about how to improve the experience of publishing/editing media in WordPress, and we should start intentionally planning for how those improvements might be made.

While this process will most likely have technical implications, we should begin with research and design to make sure we understand and account for actual user needs before jumping into the code. @karmatosed has volunteered to lead that effort, starting by reaching out to the Gutenberg team about joining us during the next meeting, Thursday, June 29, at 18:00 UTC.

Improving bug triage/review

In order to facilitate conversations about larger priority efforts, we’re going to begin experimenting with running Media focused bug scrubs separately from the weekly component meetings. @desrosj graciously volunteered to head up the first few, starting next Tuesday, June 27, at 16:00 UTC. These will focus on unanswered tickets to begin, but the focus will change as we make progress on the backlog. If you’re interested in volunteering to lead a bug scrub yourself, get in touch with me (@joemcgill) or @desrosj in Slack for details.

#4-9, #core-media