Media Meeting Recap – May 23, 2019

Overview

This post is a summary of the latest weekly Media component meeting, which took place in the #core-media SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, on Thursday, May 23, 2019. The purpose of these meetings are to move priority tasks forward, provide feedback on issues of interest, and review media focused issues. The focus of this meeting, was around the timing of our meeting going forward.

Attendees: @karmatosed @joemcgill @desrosj @mikeschroder @antpb @anevins @sergeybiryukov @pbiron

Transcript: Read on Slack

5.2.2

It was discussed by @desrosj that #46052 would be great to have fixed to 5.2.2. There was discussion around wether or not this issue was a regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. due to blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor or not related at all. Worth noting that this is happening also while using the Classic Editor pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. Investigation is needed still.

5.3

Discussion began around the scope of Media for 5.3. There are 47 tickets in the 5.3 milestone. @desrosj mentioned that a few things need to happen to keep the scope manageable. If you have a chance, it would be great to review any tickets assigned to yourself in the 5.3 milestone and decide to puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) or future releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. the issue. As he said,

Everyone should look at the tickets they own in the milestone and determine of the issue is realistic for 5.3. If not, please punt to Future Release (no shame in this!).

If the ticketticket Created for both bug reports and feature development on the bug tracker. is realistic, but you have lost interest or are not the best person to own anymore, please just remove yourself as owner.

There are 24 un-owned issues. I’d like to see all of these have an owner to help push these along during the release.

@desrosj

@azaozz has been graciously diligent in comprising a list of Uploads issues that should be prioritized. Most of all #40439 needs to be merged as soon as possible as it is currently a blockerblocker A bug which is so severe that it blocks a release. for all of the issues in the list. For that ticket, @mikeschroder mentioned that some eyes/hands are needed on the UXUX User experience/UIUI User interface side for handling during the upload; likely a mix between the modal and GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/. There is currently UI for testing in the patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. but this is not the final design. This should aim to land early in the 5.3 cycle. The full list can be found below:

@pbiron brought up a ticket that would be great to have #44900 be considered for 5.3. It currently needs design feedback so that @pbiron can move it along. Any help there would be very appreciated.

The media team is also aiming for a A11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Media focused bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub at the beginning, middle, and end of the release cycle. More to come on that as they are scheduled. There are a large handful of smaller bugs that will not require a major amount of work to address in this cycle so they will be high priority. Any preferred times/dates for the scrubs are encouraged to be included in the comments below.


Next Meeting

The next #core-media meeting is set for Thursday, May 30, 2019 at 13:00UTC See you there!

#core-media, #media, #summary