Dev Chat Agenda – June 25, 2025 – Make WordPress Core

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

The next WordPress Developers Chat will take place on Wednesday June 25, 2025 at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

The various curated agenda sections below refer to additional items. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

Announcements 📢

None for this week

Forthcoming releases 🚀

WordPress 6.8.2 is underway.

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

Brainstorming suggested by @paaljoachim “The Full Site Editor is fairly new and there are naturally features that could be improved. It would be great with an overview of current FSE plugins that aim to improve what we have today. I find it difficult to locate external FSE plugins. How can be make FSE plugins more visible in the repo?
This could perhaps also be extended to walk through the current GutenbergGutenberg 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/ pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party -> experiments and where these currently are at in their development phase.”

Open floor 🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

#6-8, #agenda, #dev-chat, #wceu-25

John Blackbourn 10:34 pm on June 24, 2025

Not sure if I’ll make the meeting but I have a topic for discussion. Should all enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. and feature requestfeature request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged. tickets for the 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. be closed?

There are 78 such tickets in the “Customize” component, although not all of these apply to the Customizer.
Jonathan Desrosiers 2:25 am on June 25, 2025

👋 I just wanted to ask that the following post is mentioned at some point during dev chat: https://make.wordpress.org/project/2025/06/25/a-little-late-spring-cleaning/.
Brad Jorsch 1:43 pm on June 25, 2025

I filed https://core.trac.wordpress.org/ticket/59282 with a PR almost two years ago, and haven’t gotten much feedback after some initial comments which I (think I) addressed. Hoping raising it in the dev chat might spur some progress. 🙂

I’ll join the channel for the chat.
agulbra 2:51 pm on June 25, 2025

Thanks to justlevine and sirlouen for reviewing the PR I’ve made for issue 31992. There are now nice comments for the unit tests I added, CI shows all green (except for one very odd timeout?), etc., and I’d appreciate more review and testing.

Welcome!

Communication

Announcements 📢

Forthcoming releases 🚀

Discussions 💬

Open floor 🎙️

Share this:

Site resources