The WordPress Developers Chat meeting took place on April 26, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.
Key Links
Highlighted Posts
Here’s the awesome activity seen in Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between April 17 and April 24, 2023:
- 27 commits
- 36 contributors
- 51 tickets created
- 6 tickets reopened
- 53 tickets closed
- and 4 new contributors 🎉
- The benefits of prioritizing and measuring performance in WordPress 6.2: Read about the collaborative planning and work that contributed to the performance gains brought with WordPress 6.2.
- WP Feature Notifications: 2023 Status Update: This update explains recent progress toward a Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-targeted modern WordPress user notification system, its interplay with 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/ Phase 3, and how you can get involved.
- WP Briefing: Episode 54: A Bill of Rights for the Open Web: Listen as Josepha explores the four freedoms of open source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL., which have been referred to as a “Bill of Rights” for the open web.
Release Updates
6.3 Planning
@ironprogrammer shared a reminder that the WordPress 6.3 Planning Proposal & Call for Volunteers is open for release squad members and mentors through this Sunday, April 30.
6.2.1 Minor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.
@audrasjb provided a WP 6.2 triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. update:
@ironprogrammer asked for confirmation that a small squad is still needed to run the 6.2.1 release, which @audrasjb confirmed. JB then added that an active Gutenberg contributor should ideally help shepherd the related issues/PRs/tasks; and that someone would be needed to help build packages, suggesting that @sergeybiryukov might help with Mission Control.
@ironprogrammer suggested sharing the needs for Gutenberg contributor involvement in the #core-editor channel, which @audrasjb confirmed he would follow up.
Open Floor
During open floor, @presskopp raised visibility on the following Trac tickets:
#33073: Some strings need “no HTML entities” translator comments — @ironprogrammer proposed that the ticket Created for both bug reports and feature development on the bug tracker. be milestoned for 6.3, as it had suggestions on how it might be addressed. @sergeybiryukov assigned the milestone to move the ticket forward.
#57999: Don’t show error message when there is nothing to update — @audrasjb suggested moving the ticket to 6.3; @pbiron agreed by setting the milestone and self-assigning the ticket. @ironprogrammer suggested that example reproduction flows be added to the ticket in order to help during testing.
#53682: tags (keywords) with umlauts don’t get saved in German locale — @audrasjb noted that this ticket still needed a 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. to move it forward.
#54836: Huge error logs filled with “WordPress database error Illegal mix of collations” errors caused by spammers — @ironprogrammer agreed with @audrasjb‘s in-ticket assessment, and that a Database component maintainer should review the ticket, so pinged @craigfrancis. @pbiron asked if the issue was due to different collations in the DB, or if the collation differed from the spam text encoding, and Brian asked for reproduction steps to better understand what triggers the errors.
#50081: orderby datetime field — @audrasjb identified this as a Docs (DevHub) issue, and updated the ticket. @leogermani and @sergeybiryukov responded and provided context for when the code example was last updated. JB updated the sample code in DevHub and closed the ticket. 🎉
#39645: If user “admin” doesn’t exist (renamed admin account) users can create a user with username admin — this last ticket mention occurred after Dev Chat wrapped up, and there was no further discussion on it.
Next Meeting
The next meeting will be on May 3, 2023 at 20:00 UTC.
Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the #core Slack channel.
Props @costdev for peer review of this summary, and to everyone who participated in the Dev Chat.
#6-3, #6-2, #dev-chat, #meeting, #summary
