Dev Chat Summary: March 27

This post summarizes the weekly devchat meeting from March 27th, 2019 ( Slack Archive ).

Announcements

5.2 updates

The release did not meet original schedule for beta 1 but is back on track and beta release process will have been kicked off by the time you are reading these notes. Gary said, “There are currently 116 open tickets, which can be reasonably tackled in 3 betas.” The current goal is getting that down to 66 open tickets before beta 2. Target release for 5.2 is April 30. More info here: https://make.wordpress.org/core/5-2/

Coding standards changes up for discussion: Be on the lookout at /news for wider awareness to the update.

Calls from component maintainers

The JavaScript crew have published a post on how to build plugins that use modern JavaScript, which I’m sure they’d appreciate feedback on: https://make.wordpress.org/core/2019/03/25/building-javascript/

Editor folks have a block registration RFC that that’d love your input on:

https://github.com/WordPress/gutenberg/pull/13693

@desrosj mentioned #46195https://core.trac.wordpress.org/ticket/46195 and it was agreed the latest patch can move it forward as long as we provide dev notes on edge cases.

Open Floor

@elrae asked “Will the Classic Editor continue to disable other parts of Gutenberg as it rolls out? Specifically widgets and menu areas?” This is still to be determine but @pento mentioned, “Widgets and menu areas are much more contained, on the other hand, and can likely be made largely backwards compatible.”

@dmsnell mentioned #46199 which is a bug causing some unexpected editor crashes. We would love for someone familiar with the REST API to look into it. @pento said, “I think your patch looks like a reasonable change, but I’d like to get some input from some REST API folks before we commit it.”

@peterwilsoncc provided a very important reminder about being welcoming, “I’ve noticed a few facepalm, eye-roll and similar emoji reactions in Slack to tickets reported against long term design decisions of WP. Often these are from new contributors. Can everyone please avoid these as they can be intimidating for potential new contributors lurking in the room to get a feel for the project. I’ve experienced this feeling myself, lurking elsewhere to get the lay of the land.”


See you next Wednesday at the new Dev Chat time of 20:00 UTC. This adjustment is as a result of daylight savings time.

These meetings are held in the #core channel in the Making WordPress Slack.

#5-2 #devchat #summary