{"id":123615,"date":"2026-05-28T17:47:06","date_gmt":"2026-05-28T17:47:06","guid":{"rendered":"https:\/\/make.wordpress.org\/core\/?p=123615"},"modified":"2026-05-28T17:48:18","modified_gmt":"2026-05-28T17:48:18","slug":"wordcamp-asia-2026-core-committers-meeting","status":"publish","type":"post","link":"https:\/\/make.wordpress.org\/core\/2026\/05\/28\/wordcamp-asia-2026-core-committers-meeting\/","title":{"rendered":"WordCamp Asia 2026 Core Committers Meeting"},"content":{"rendered":"<p class=\"wp-block-paragraph\">On April 11, 2026, <span tabindex='0' class='glossary-item-container'>Core<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Core<\/span> <span class='glossary-item-description'>Core is the set of software required to run WordPress. The Core Development Team builds WordPress.<\/span><\/span><\/span> Committers in attendance (including emeritus) at <span tabindex='0' class='glossary-item-container'>WordCamp<span class='glossary-item-hidden-content'><span class='glossary-item-header'>WordCamp<\/span> <span class='glossary-item-description'>WordCamps 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\u2019ve learned throughout the year and share the joy. <a href=\"https:\/\/central.wordcamp.org\/about\/\">Learn more<\/a>.<\/span><\/span><\/span> Asia in Mumbai, India gathered for a brief informal meeting.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There was no formal agenda, but a few goals for the meeting were mentioned at the beginning:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Allow newer committers to meet more senior ones.<\/li>\n\n\n\n<li>Allow anyone to raise questions, concerns, or suggestions that have been on their minds.<\/li>\n\n\n\n<li>Just spend some time together chatting and getting to know each other.<\/li>\n\n\n\n<li>Discuss short and medium term challenges.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Below are some brief notes from discussions that happened following<a href=\"https:\/\/en.wikipedia.org\/wiki\/Chatham_House_Rule\"> Chatham House Rule<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">7.0 Release<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The 7.0 timeline and active freeze on unrelated commits to <code>trunk<\/code> were discussed before moving on to examining the remaining open tickets in the milestone. All findings and thoughts were added publicly to each individual <span tabindex='0' class='glossary-item-container'>ticket<span class='glossary-item-hidden-content'><span class='glossary-item-header'>ticket<\/span> <span class='glossary-item-description'>Created for both bug reports and feature development on the bug tracker.<\/span><\/span><\/span>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A summary of the state of the real-time collaboration feature was given so that everyone in attendance was up to speed with the approaches being evaluated and what the potential tradeoffs are. Attendees agreed to add any thoughts they had to the respective tickets and pull requests.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It was flagged that there could be some differences between how <span tabindex='0' class='glossary-item-container'>MySQL<span class='glossary-item-hidden-content'><span class='glossary-item-header'>MySQL<\/span> <span class='glossary-item-description'>MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. <a href=\"https:\/\/www.mysql.com\/\">https:\/\/www.mysql.com<\/a><\/span><\/span><\/span>\/MariaDB and SQLite work. Since Playground runs on SQLite, there could be some compatibility issues with the proposed table structures that surface. It could be helpful for SQLite support to be re-evaluated in WordPress Core to have a more firm policy around support expectations.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Code Syncing from <code>gutenberg<\/code> Repository<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The new build tooling processes introduced during the 7.0 cycle through <a href=\"https:\/\/core.trac.wordpress.org\/ticket\/64393\">#64393<\/a> were discussed.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>In practice, it\u2019s not clear what this means going forward when managing multiple branches.<\/li>\n\n\n\n<li>For <code>7.0<\/code> and <code>trunk<\/code> (at the time of the meeting), the <code>gutenberg.sha<\/code> value pinned is from the <code>wp.7.0<\/code> <span tabindex='0' class='glossary-item-container'>branch<span class='glossary-item-hidden-content'><span class='glossary-item-header'>branch<\/span> <span class='glossary-item-description'>A 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\".<\/span><\/span><\/span>.<\/li>\n\n\n\n<li>That would remain true for the <code>7.0<\/code> branch, but <span tabindex='0' class='glossary-item-container'>SVN<span class='glossary-item-hidden-content'><span class='glossary-item-header'>SVN<\/span> <span class='glossary-item-description'>Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase.<\/span><\/span><\/span> <code>trunk<\/code> will be updated to pin from the upstream <code>trunk<\/code> branch after the release.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">One of the benefits of these build script changes is that it\u2019s easier to sync code maintained in the <span tabindex='0' class='glossary-item-container'>Gutenberg<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Gutenberg<\/span> <span class='glossary-item-description'>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 \u2018blocks\u2019 to add richness rather than shortcodes, custom HTML etc.\r<a href=\"https:\/\/wordpress.org\/gutenberg\/\">https:\/\/wordpress.org\/gutenberg\/<\/a><\/span><\/span><\/span> repository more often. What an ideal sync schedule could look like was discussed:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Sync on the week following a new release of the Gutenberg <span tabindex='0' class='glossary-item-container'>plugin<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Plugin<\/span> <span class='glossary-item-description'>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 <a href=\"https:\/\/wordpress.org\/plugins\/\">https:\/\/wordpress.org\/plugins\/<\/a> or can be cost-based plugin from a third-party.<\/span><\/span><\/span>. This allows for any <code>.1<\/code> and <code>.2<\/code> releases that may be necessary to occur.<\/li>\n\n\n\n<li>During <span tabindex='0' class='glossary-item-container'>beta<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Beta<\/span> <span class='glossary-item-description'>A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.<\/span><\/span><\/span>\/<span tabindex='0' class='glossary-item-container'>RC<span class='glossary-item-hidden-content'><span class='glossary-item-header'>release candidate<\/span> <span class='glossary-item-description'>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 <a href=\"#alpha-beta\">alpha (beta)<\/a>.<\/span><\/span><\/span> periods, syncing weekly or prior to each pre-release version using a SHA value from the corresponding <code>wp\/X.Y<\/code> branch for the <code>gutenberg.sha<\/code> property.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This practice does have some nuance that needs to be discussed more broadly. Mainly, when SVN <code>trunk<\/code> is bumped to <code>X.Y+1-alpha<\/code>, it makes sense to also update the pinned SHA value in <code>wordpress-develop<\/code> to represent the most recent Gutenberg plugin release. While this makes sense in theory, it is counter to the current practice of \u201ccommit to <code>trunk<\/code> first, then <span tabindex='0' class='glossary-item-container'>backport<span class='glossary-item-hidden-content'><span class='glossary-item-header'>backport<\/span> <span class='glossary-item-description'>A 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.<\/span><\/span><\/span> to numbered branches\u201d because there will possibly be some divergence in SVN <code>trunk<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There is also still some code that requires the manual creation of a pull request to <code>wordpress-develop<\/code> from <code>gutenberg<\/code>, so the process is not 100% there just yet.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Ways To Improve New Build Scripts<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>There are likely ways to improve how code is imported into the <code>wordpress-develop<\/code> repo so that it lands in more appropriate locations. Examples: no <span tabindex='0' class='glossary-item-container'>admin<span class='glossary-item-hidden-content'><span class='glossary-item-header'>admin<\/span> <span class='glossary-item-description'>(and super admin)<\/span><\/span><\/span>-facing code in <code>wp-includes<\/code> or using insertion points for various points in <code>wordpress-develop<\/code> <span tabindex='0' class='glossary-item-container'>PHP<span class='glossary-item-hidden-content'><span class='glossary-item-header'>PHP<\/span> <span class='glossary-item-description'>The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher<\/span><\/span><\/span> files to copy relevant chunks of code.<\/li>\n\n\n\n<li>The inline documentation for the code managed in the <code>gutenberg<\/code> repository is currently lacking important elements such as <code>@since<\/code> tags.<\/li>\n\n\n\n<li>There is still friction between <span tabindex='0' class='glossary-item-container'>JavaScript<span class='glossary-item-hidden-content'><span class='glossary-item-header'>JavaScript<\/span> <span class='glossary-item-description'>JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user\u2019s browser.\r<a href=\"https:\/\/www.javascript.com\/\">https:\/\/www.javascript.com<\/a><\/span><\/span><\/span>-based and PHP-based functionality in this process.<\/li>\n\n\n\n<li>There is more room to automate the process in general.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">There was agreement that a good way to proceed would be to take inventory of what manual workflows still exist even after the recent changes to how this is managed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Performance Team<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">It was noted that the Performance Team has experienced a decrease in active contributors with only a small number who are regularly active. There are currently 7-10 individual performance-focused plugins being maintained by the team.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There were two agreed upon take aways:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Stepping back to highlight the status and goals of each plugin could make it easier for contributors who have not yet been involved to be brought up to speed and potentially attract new contributors.<\/li>\n\n\n\n<li>There are a few high-potential plugins that need coordinated effort to get them to the finish line and integrated into Core.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Looking Ahead to WordPress 7.1<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The discussion transitioned from discussing those high-potential performance plugins that could possibly be ready for a merge proposal to possible targets for the 7.1 cycle more broadly. Some of the ideas brought up were:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Retrying client-side media (was reverted and punted from 7.0).<\/li>\n\n\n\n<li>Template Organization\/Management (also reverted and punted from 7.0).<\/li>\n\n\n\n<li>Front-end view transitions for all users (not just logged out). Still has implementation hurdles that need broader discussion.<\/li>\n\n\n\n<li>Per-template styles<\/li>\n\n\n\n<li><a href=\"https:\/\/wordpress.org\/plugins\/auto-sizes\/\">Enhanced Responsive Images<\/a> (<code>sizes=\"auto\"<\/code> support and improved <code>sizes<\/code> attributes for <span tabindex='0' class='glossary-item-container'>block<span class='glossary-item-hidden-content'><span class='glossary-item-header'>Block<\/span> <span class='glossary-item-description'>Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.<\/span><\/span><\/span> themes).<\/li>\n<\/ul>\n\n\n\n<p class=\"has-text-align-right wp-block-paragraph\"><em>Props <a href=\"https:\/\/profiles.wordpress.org\/westonruter\/\" class=\"mention\"><span class=\"mentions-prefix\">@<\/span>westonruter<\/a> for peer review.<\/em><\/p>\n<p class=\"o2-appended-tags\"><a href=\"https:\/\/make.wordpress.org\/core\/tag\/core-committer-meetings\/\" class=\"tag\"><span class=\"tag-prefix\">#<\/span>core-committer-meetings<\/a>, <a href=\"https:\/\/make.wordpress.org\/core\/tag\/core-committers\/\" class=\"tag\"><span class=\"tag-prefix\">#<\/span>core-committers<\/a><\/p><nav class='o2-post-footer-actions'><ul class='o2-post-footer-action-row'><li class='o2-post-footer-action'><a href=\"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2026%2F05%2F28%2Fwordcamp-asia-2026-core-committers-meeting%2F%23respond&#038;locale=en_US\" title=\"Login to Reply\"  class=\"genericon  genericon-reply\"  data-action=\"login-to-reply\"  data-actionstate=\"default\" >Login to Reply<\/a><\/li><\/ul><div class='o2-post-footer-action-likes'><\/div><ul class='o2-post-footer-action-row'><\/ul><\/nav>","protected":false},"excerpt":{"rendered":"<p>On April 11, 2026, CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers in attendance (including emeritus) at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They&#8217;re one of the places where the WordPress community comes together to teach one another what they\u2019ve [&hellip;]<\/p>\n","protected":false},"author":4552240,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"advanced_seo_description":"","jetpack_seo_html_title":"","jetpack_seo_noindex":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[1173],"tags":[5726,5046],"class_list":["post-123615","post","type-post","status-publish","format-standard","hentry","category-meetings","tag-core-committer-meetings","tag-core-committers","mentions-westonruter","author-desrosj"],"revision_note":"","jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p2AvED-w9N","_links":{"self":[{"href":"https:\/\/make.wordpress.org\/core\/wp-json\/wp\/v2\/posts\/123615","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/make.wordpress.org\/core\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/make.wordpress.org\/core\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/make.wordpress.org\/core\/wp-json\/wp\/v2\/users\/4552240"}],"replies":[{"embeddable":true,"href":"https:\/\/make.wordpress.org\/core\/wp-json\/wp\/v2\/comments?post=123615"}],"version-history":[{"count":3,"href":"https:\/\/make.wordpress.org\/core\/wp-json\/wp\/v2\/posts\/123615\/revisions"}],"predecessor-version":[{"id":123623,"href":"https:\/\/make.wordpress.org\/core\/wp-json\/wp\/v2\/posts\/123615\/revisions\/123623"}],"wp:attachment":[{"href":"https:\/\/make.wordpress.org\/core\/wp-json\/wp\/v2\/media?parent=123615"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/make.wordpress.org\/core\/wp-json\/wp\/v2\/categories?post=123615"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/make.wordpress.org\/core\/wp-json\/wp\/v2\/tags?post=123615"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}