The chat was led by @davidbaumwald based on this agenda.
The full meeting transcript is available on Slack.
Highlighted blog (versus network, site) posts
@davidbaumwald shared some posts from the Make Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blog.
5.4 Retrospective – Call for feedback: the deadline is April 30 and everyone is welcome to leave a feedback.
Proposal: Core Team Rep Elections: the deadline for nominations and self-nominations is May 4.
We’re applying to Season of Docs: a new working group that needs help!
WordPress 5.5: Call for Tickets: the deadline is April 30.
Upcoming Releases
WordPress 5.4.1 Release Candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1 was supposed to be released yesterday Wednesday, but there were some miscommunication between Core team and Gutenberg 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/ team. The RC One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). has then been pushed back to this Friday. The Gutenberg changes that are going to be included in the release are listed in this pull request. The milestone for this point release is also cleared.
@davidbaumwald reminded that for 5.5, all the maintainers have been pinged about potential features and focuses. If you’re a component maintainer and haven’t replied yet, please do, so scope and schedule can be proposed.
He also said that work for 5.6 release, aka all-women release, continues. All the women that expressed interest have been contacted. @chanthaboune, @angelasjin, @cbringmann and @francina will work on phase 2: identifying missing roles and cohorts to organize the team that will ride along with 5.5.
Components Check-in
@francina has pinged #meta team about having a weekly scheduled post to check Components status; @dd32 expressed some concerns about the noise that it will create. @davidbaumwald suggested to move on with this for a three-month test.
@audrasjb gave an update about plugins and themes auto-update feature. The team released version 0.6.0 of the Feature Plugin yesterday Wednesday.
The Feature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. contains all the identified must-have features and the UI User interface was reviewed by several teams. The team is now about to write the Core merge proposal post on Make/Core. More infos here.
Open Floor
@apedog asked a question about routing in WordPress Core. He stated that the WP class having $_SERVER hard-coded into it. And this would require re-writing the methods inside WP class, but without changing its functionality.
@clorith said that he’s generally against the bot idea for a general channel with lots of chatter, and the loss of potential input to backscroll. If it’s going to happen, it should be on Make/* somewhere for consistency and visibility.
@audrasjb pointed out to #16557, a long standing ticket Created for both bug reports and feature development on the bug tracker. raised by some people in the French WordPress community. It appears it would be a great SEO enhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. to provide proper filters on redirect_guess_404_permalink() function.
He milestoned the ticket to 5.5.0 and refreshed the existing patch 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. against trunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. after testing it. This still needs some unit tests, but before writing them, it would be nice to get a quick review on the current proposal.
@netpassprodsr called for review on #49832.
#5-4-1, #5-5, #5-6, #summary
