Dev Chat Summary: June 3, 2020

@whyisjake facilitated on this agenda. @sageshilling is the author of this summary, and @marybaum is your marginally faithful editor.


@chanthaboune had three: 

  1. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. has two brand-new team reps – @francina and @audrasjb! See more here.
  2. @chanthaboune will host office hours with Matt at WordCamp Europe this weekend.
  3. Release squads for the rest of 2020 are pretty close to final, with one update outstanding.

@whyisjake pointed the group to the latest Gutenberg news, which included a near-weekly release–this time to version 8.2.

Upcoming releases: 5.4.2

@whyisjake shared the status of the next minor.

After a smooth release-candidate launch just hours before devchat, he confirmed, “We are looking really great for a release on the tenth.” Check the Trac milestone here and you’ll see for yourself!

Component Updates

@swissspidy expects to share a merge proposal for sitemaps next week 🙂 based on this pull request. He commented that folks are “adding the finishing touches here and there until we have something we believe is ready to merge.”

@audrasjb reminded the group that two weeks ago the Plugins and themes auto-update feature got merged, and so far the feedback is pretty good.

The coders on the ticketticket Created for both bug reports and feature development on the bug tracker. are adding a few more hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., and @audrasjb pointed to two relevant tickets that need copy review by Friday, when @audrasjb will submit them for final review. @m_butcher, @yvettesonneveld and @marybaum are on the task.

The two tickets are #50215 and #50268. If you’re reading this, you too can look at the copy and add your suggestions!

Open Floor

(Ed. note: Got a pressing topic for Open Floor? Add it to the agenda post as a comment, and come to the chat. It’s in SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at, so you don’t even have to comb your hair! )

From comments on the agenda:

@glorialchemica asked for an update on the full-site-editing, or FSE, for short, project.
@chanthaboune responded.

So, the form to show interest has been closed, and I believe that the process of reaching out to everyone has started. The point at which actual feedback outreach and processing begins is a little fluid, since it’s tied to development timelines but it should get going in the next month or so if I recall correctly. In my absence, @annezazu will be driving the bulk of that work.


@annezazu announced that she was in the process of inviting everyone who’d signed up to a private Slack chat where folks could try things out and communicate efficiently; a lively discussion followed, with several keepers of WordPress history reminding the group of relevant incidents in the history of the project.

The result: @annezazu immediately made a public space for FSE and will take the private one down shortly.

@timothyblynjacobs asked for feedback from the Build/Test Tools maintainers on #50251. @jorbin took a look and said, Looks good. I’m going to commit it

@francina reminded the group about Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of There are many teams that people can participate in, each with a different focus. at WCEU!

@joyously mentioned there was a meeting about the editor and CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings., and FSE.  She asked if there will be another one? 

@desrosj I think that meeting was more to help the Customizer maintainers shape their expectations of where their expertise would be needed throughout the FSE process. 

@whyisjake ended the meeting at the top of the hour.

If you’d like more depth about anything the Core team discussed, you can read the full chat transcript here.

#dev-chat, #summary