The WordPress coreCoreCore 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 bugbugA 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.
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 ticketticketCreated 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.
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases. A release squad for 6.8.2 and 6.8.3 will be announced soon.
Discussions 💬
The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core 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.
Proposal concerning Core TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. workflow keywords
He asked the following: “Need committers to help with the revision of the Workflow Keywords (specially the committercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. and backportbackportA port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. part where I have more doubts). First I’m willing to publish an article explaining the new ideas with the first revision of the revised diagram and it could serve as an attention call for anyone willing to make an opinion or add anything else before the final proposal.”
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.
The full chat log is available beginning here on Slack.
Performance Lab PluginPluginA 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. (and other performance plugins)
@westonruter announced that the initial release of theView Transitions plugin is now live on WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. 🎉
@jonoaldersonwp and @westonruter both installed the plugin on their personal sites and reported positive feedback on its visual smoothness and polish.
@flixos90 shared that a blogblog(versus network, site) post is being prepared to explain the plugin’s background a bit more, and there are plans to explore it further with contributors at WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe.
@flixos90 highlighted the significant value of achieving these transitions without needing to rearchitect the entire site or work around WordPress’s default behavior.
@jonoaldersonwp noted that this solution is preferable to the old AMP-based AJAX content wrapper approach.
Open Floor
@b1ink0 reminded everyone that the upcoming Performance Bug Scrub is scheduled for June 10, 2025, noted an open host slot, and invited anyone interested to lead it.
@flixos90 volunteered to host the bugbugA 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. scrub on June 10, due to a scheduling conflictconflictA conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. with the originally planned slot on June 24.
WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe is one week away!
@benjamin_zekavica facilitated the organization of the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team tables. If you plan to attend, check the Core Team at WCEU 25 | Contributor Day article.
GutenbergGutenbergThe 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/ 20.9 is now available
The new version of the Gutenberg pluginPluginA 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. is now available in our plugin directory.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The Core Team is putting together a squad for future minor releases.
In preparation for the WordCamp Europe 2025 Contributor Day, @benjamin_zekavica called for important Core bugbugA 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. tickets to be submitted for planning.
@realloc will lead the MultisitemultisiteUsed to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site table and is working with maintainers to identify good first bugs.
Core committers are encouraged to actively participate and make at least one commit — with @mamaduka offering remote support.
Where do bugs go if they are introduced in a point releaseMinor ReleaseA 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.?
There was a discussion about how to handle bugs found during a point release. Usually, these bugs should be included in the next point release, especially if there is a patchpatchA 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. or if it is a regressionregressionA software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5..
Whether a fix is backported depends on factors such as the bug’s age, severityseverityThe seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs., and the risk of the fix. Since clear guidelines are lacking, decisions are made case by case by release leads. More documentation on this process was recommended.
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 ticketticketCreated 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 📢
WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe is one week away 🤯 @benjamin_zekavica facilitated the organization of the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team tables. If you plan to attend (please do!), check the Core Team at WCEU 25 | Contributor Day article.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The Core Team is putting together a squad for future minor releases. And yes, more volunteers are welcome.
Next GutenbergGutenbergThe 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/ version: 20.9
Gutenberg 20.9 is scheduled for release on Wednesday, May 28, 2025. So it might be out by the time we start dev chat 💪
Discussions 💬
The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core 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.
@benjamin_zekavica posted about WordCamp Europe Contributor Day in Basel. Do you have ahigher-priority ticket dear to your heart? This is a great time to work on it and shepherd it to resolution. Please add them to the WCEU prep post as commentsso the table leads and supporters can prepare.
Where do bugs go if they are introduced in a point releaseMinor ReleaseA 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.?
@sirlouen asked: Should bugs introduced during a point release cycle be moved into the next point release or the next major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.? This item is not documented. Since we are moving to a different release cadence, it could use some clarity.
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.
We’re so excited—next week, on June 5th, we’re heading to Basel for WordCamp Europe! 🎉 The event kicks off with Contributor DayContributor DayContributor 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 https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/, a fantastic opportunity to come together and help shape the future of WordPress.
New contributors are especially welcome!
Whether you write code or not, everyone can get involved with the WordPress CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.. Wondering how? It’s easier than you think.
We’ll have several tables dedicated to the Core Team, and we’ve brought together a fantastic group of experienced contributors to guide and support you.
⚠️ Before the event, we kindly ask you to prepare everything at home.
Please prepare your setup at home: Install all necessary software, clone the repositories, and download Node.js packages and all software in advance! To avoid slowdowns or connection issues, we encourage everyone to limit heavy downloads during the event.
New to contributing? No problem! We have experienced mentors at each table who are happy to help you get started.
Bring your charger and adapters It’s going to be a full day – make sure your devices stay powered!
Join the conversation Don’t be shy! Ask questions, share ideas, and get to know fellow contributors.
Prepare at home 🏡
Register for a WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ profile and the WordPress.org Slack instance
The large majority of the communication around contributing to the WordPress open sourceOpen SourceOpen 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. projects happens on WordPress.org or in the WordPress Slack instance. Your first step should be to register for both in that order.
To get started right away working with us on WordPress and the GutenbergGutenbergThe 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/ Editor, please make sure your technical setup is ready. You’ll need a laptop and access to all the accounts we’ve linked for you above.
WordPress Core
If you’d like to contribute directly to WordPress Core, you should start by forking the WordPress Development Repository. Then, make your changes in your own branchbranchA directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".. Once ready, submit a pull request referencing the related ticketticketCreated for both bug reports and feature development on the bug tracker. number. The system will automatically detect the number and link your patchpatchA 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 the corresponding ticket.
To contribute to the Gutenberg Editor, you don’t necessarily need Docker. Simply fork the Gutenberg repository, make your changes in a new branch, and submit a pull request. The only requirement is a recent version of Node.js.
Want to contribute to the future of WordPress? Whether you’re into fixing bugs or creating new features for the Gutenberg editor – your skills are needed! Learn how to get started and explore all the ways you can make an impact – more information available at the link below.
GitHubGitHubGitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ Repositories
These links are specially curated for new contributors who want to help with the WordPress Core or the Gutenberg Editor pluginPluginA 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.. They provide filtered resources and guidance to get you started smoothly and make meaningful contributions. Welcome aboard!
Want to make a real impact on WordPress? Help improve the platform by testing new features and catching bugs before they go live. Learn how you can get involved and support the community – all the details are in the link below.
Great documentation helps users and contributors alike. Whether you enjoy writing guides, updating existing content, or translating for a global community – your input is essential.
No problem – you are welcome to ask your questions in the #contributor-day channel as well as in the #core channel. @mikachan and @audrasjb will be available throughout the day to assist you with any inquiries.
Sign up for our Contributor Day stats!
We want to make Contributor Day even better for everyone — and we need your help! Please take a moment to fill out our quick form to share who participated, which tickets you worked on, and whether you’re new or a returning contributor.
Rest assured, the data you provide in Google Forms will be deleted after the event. The summarized results will be published as a recap post on the Core Blogblog(versus network, site) — with contributors properly credited and tagged.
It only takes a few minutes — but makes a big difference! The submission is now closed. ⚠️
On June 5, 2025, the Contributor DayContributor DayContributor 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 https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ at WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe will take place in Basel, and the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is looking for experienced volunteers to support onsite.
Co-Lead (preferably a Core CommittercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.) | One position available:
You are a Core Committer or very experienced with the WordPress Core project
You have helped lead or support a Contributor Day before
You can assist with technical questions and confidently guide new contributors through tools like TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and GitHubGitHubGitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/
You communicate clearly and feel comfortable using English
Supporter | Two positions available:
You are familiar with the Core Team workflows
You help new contributors with setup, explain tools, and assist with initial tasks
You communicate clearly and feel comfortable using English
Please apply by leaving a comment under this post by May 29, 2025. We look forward to your support—let’s make this Contributor Day a success together! 🥳
There are no major announcements from the past week.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases.
Next GutenbergGutenbergThe 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/ version: 20.9
Gutenberg 20.9 is scheduled for release on Wednesday, May 28, 2025.
Discussion 💬
Refreshing Workflow Documentation
@SirLouen suggested updating the TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. workflow keyword documentation, noting that some terms are outdated, misused, or conflicting. He plans to draft a revised version to provide clearer guidance for contributors and aims to publish it on the blogblog(versus network, site). The goal is to support future discussion and improve overall understanding of keyword use.
Improving the Local Development Environment
The current local development environment for WordPress is minimal and does not include all tools needed for comprehensive testing. Since different approaches are used, the documentation should be updated and improved to reflect the latest state.
Reducing Redundant Test Reports
@krupajnanda suggests limiting the number of test reports on simple tickets (e.g., UIUIUser interface/UXUXUser experience, accessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)) to around 5 and adding a message to guide contributors to more important tickets, to reduce redundant testing. @jorbin and others agree but emphasize that this shouldn’t be automated, as a person needs to verify the validity of test reports.
Additionally, once enough test reports are received, the needs-testing label should be removed to focus efforts on tickets still requiring testing.
Open floor 🎙️
Review Needed: Unicode Email Addresses
@agulbra is requesting a review for ticketticketCreated for both bug reports and feature development on the bug tracker.#31992. The code was written last year, but it’s now ready to be merged since PHPMailer has released the required dependencies. @ironprogrammer has already reviewed it and suggested asking for further feedback here. It would be great if someone could take a look. Thanks!
Call for Core Bug Tickets for the WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe 2025 | Contributor DayContributor DayContributor 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 https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/
@benjamin_zekavica mentioned that preparation for the WordCamp Europe Contributor Day in Basel should begin. To support this, suitable tickets need to be collected. If anyone finds higher-priority tickets that could be worked on during the event, they are encouraged to add them as comments in this article. This would help streamline the preparation process.
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 ticketticketCreated 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 📢
There are no major announcements from the past week.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases.
Next GutenbergGutenbergThe 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/ version: 20.9
Gutenberg 20.9 is scheduled for release on Wednesday, May 28, 2025.
Discussions 💬
The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core 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.
Refreshing Workflow Documentation
@sirlouen suggests updating the workflow keyword documentation, as some terms are outdated, misused, or conflicting. He proposes drafting a clearer version to publish on the blogblog(versus network, site) for better contributor guidance.
Improving the Local Development Environment
The current WordPress development setup makes certain testing tasks (like email testing) harder than necessary. @sirlouen recommends adding helpful tools to make the environment more complete and testing more efficient.
Reducing Redundant Test Reports
@krupajnanda points out that some simple tickets, especially UIUIUser interface/UXUXUser experience and accessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) ones, receive too many test reports, while more complex tickets are often ignored. She proposes setting a soft limit (e.g. 5 reports) and adding a message to guide contributors to other important tickets.
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.
