Dev chat summary: September 11


@Francina asked the group for announcements, and @jbaudras highlighted this Make/Design post:
There are 3 tickets waiting for final decision in order to land in WP 5.3

Then she added two more:

Make WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
Introducing Twenty Twenty
The 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 will soon celebrate its first birthday in Core and with every update it grows more capable. The promise of the block editor is to give users the freedom to design and structure the…

Make WordPress Core
Defining Content–Block Areas
One of the major projects from this year’s focuses is to expand the block editor beyond the content area and into other parts of the site. This included, so far, explorations to bring blocks into o…
Sep 5th

Media component maintainer Anthony Burchell told the group he’s been sharing that link around and getting great feedback.
@francina praised the video in the post. She added, “Personally I’m looking forward to seeing all the possibilities that blocks are giving us!”
After @afercia mentioned some accessibilityAccessibility 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). ( feedback, @francina moved the discussion forward, inviting everyone (you too, dear reader!) to leave comments on the relevant posts.

Upcoming releases: 5.3

Bugscrubs: @davidb opened with this news: we still had 314 tickets milestoned for 5.3.

The discussion that followed surfaced a general preference to focus on enhancements and features between now and BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1, when features freeze, and on 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. fixes between Beta 1 and release.

As of devchat, 120 features and enhancements are milestoned for 5.3 on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..

@davidb and the focus leads will do a bit of promoting to get more folks to come to bugscrubs.
(Ed. note: Beta 1 should land September 23; final release is slated for November 12.

Default theme focus lead @ianbelanger reported in on the next default theme, Twenty Twenty. has a weekly meeting, on Mondays at 19:00 UTC, and has opened its GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. repo to contributors.

Marketing has nominated @miker as its focus lead for the release. It’s started meeting on Fridays at 16:00 in the Marketing channel, to work on copy for the About page. @marybaum and @miker asked for input from maintainers on enhancements they think are important.

In Docs, we have one dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. published and two more under review. Lead @justinahinon is going to all the component meetings, to let their teams know the Docs team is around to help with their notes.

Media: @mikeschroder is the 5.3 focus lead.

Next bugscrub is Thursday at 05:00 UTC. Check the rest of the schedule at


@antpb reported in on Media, which is also taking the lead on APAC-friendly meeting times. As he said:

“This devchat does not align with normal hours for him, so I will help with updates here. Discussion about the scope of the 5.3 Media will take place tomorrow at 13:00 UTC (agenda to come soon in the #core-media room). I anticipate the scope to largely focus on 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). ( and image handling improvements. I know of a few on my plate currently that will also fit in line with the release focus of UIUI User interface improvements.”

@clorith and @jeffpaul will work to get scrubs posted on WordPress 5.3 Development Cycle – Make WordPress Core.

@pierregordon volunteered to become a maintainer for the External Libraries component.

And there was more discussion on getting people to come to bugscrubs.


As we hit the hour, folks who needed to do other things (like sleep, eat or work) signed off. But the chat was still lively enough that several people stayed on tolerant more about exactly what a component maintainer’s role includes.

@jbaudras referred to this post:

These maintainers are vital to keeping WordPress development running as smoothly as possible. They triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. new tickets, look after existing ones, spearhead or mentor tasks, pitch new ideas, curate roadmaps, and provide feedback to other contributors. Longtime maintainers with a deep understanding of particular areas of core are always seeking to mentor others to impart their knowledge.

From (edited)

Devchat ended at ten minutes past the hour.

#5-3, #core, #dev-chat, #twenty-twenty