Performance Chat Summary: 18 June 2024

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

  • Welcome to our new members of #core-performance
  • Early WordPress 6.6 BetaBeta 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. 2 performance results [GitHub issue]
  • WordCampWordCamp 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’ve learned throughout the year and share the joy. Learn more. Europe highlights post [link]
  • Thanks to all who joined Contributor DayContributor Day Contributor 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://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WordCamp Europe! [accomplishments]

Priority Items

  • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
    • Current release (WP 6.6)
  • Performance Lab 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 (and other performance plugins)
    • Auto-Sizes for Lazy-Loaded Images
    • Embed Optimizer
    • Fetchpriority
    • Image Placeholders
    • Modern Image Formats
    • Optimization Detective
    • Performant Translations
    • Speculative Loading
  • Active priority projects

WordPress Performance Trac Tickets

Performance Lab Plugin (and other Performance Plugins)

  • @joemcgill Chrome 126 went stable last week, which includes support for auto-sizes, so I’d encourage more folks to start testing the Auto-sizes plugin and provide feedback
  • @mukesh27 For PL plugin PR #1298 is ready for review
  • @westonruter I’ve been working on adding integration between Embed Optimizer and Optimization Detective, allowing the collected URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org metrics to inform whether an embed should be lazy-loaded and if not (when in the initial viewport) to add preconnect links. This has exposed some limitations with the current implementation so I’ve been refactoring how the tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) processor is leveraged which will make it much more powerful for extensions to apply optimizations. Currently still a draft but should be ready for review this week: https://github.com/WordPress/performance/pull/1302
  • @westonruter for Speculative Loading, there’s a PR now to implement support for the search form, but this currently requires a hack which has been reported upstream to Chromium to allow speculative loading prerenders for GET forms: https://github.com/WordPress/performance/pull/1297
  • @westonruter ready for review is another PHPStan PR to apply strict rules: https://github.com/WordPress/performance/pull/1241

Active Priority Projects

Improving the calculation of image size attributes

  • @mukesh27 For accurate sizes, we used a different approach for updating the sizes. The PR #1252 is ready with those changes. If anyone has a moment, please take a look

Optimized Autoloaded Options

  • @joemcgill our only remaining task is to publish the dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.. I saw that @adamsilverstein provided some minor feedback, which @pbearne has already addressed. I think it’s probably read to go

Improved template loading

  • @thekt12 I have addressed feedback from @joemcgill –  https://github.com/WordPress/wordpress-develop/pull/6781. I still need to move this to GB as this is GB first issue
  • @joemcgill one of the things that I’ve been thinking about, related to these types of caches—where we’re trying to add persistence to all sites via the use of transients—is what is the best way to avoid the extra DB query that gets made when you have a transient with a TTL value. It may be worth updating the transient APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to allow for autoloading to be specified when setting the transient.

Open Floor

  • @joemcgill reminder about the new project board that we’ve got set up here. I’m curious if anyone is still using the older project boards on a regular basis. If not, I think we can remove them.

Our next chat will be held on Tuesday, June 25, 2024 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #performance, #performance-chat, #summary

Summary, Dev Chat, June 12, 2024

Start of the meeting in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., facilitated by @joemcgill. 🔗 Agenda post.

Announcements

  • WordPress 6.6 Beta 2 was released on June 11. Thanks to everyone who was involved in getting that release. Please keep testing!

Forthcoming Releases

Next major releasemajor release A 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.: 6.6

We are currently in the WordPress 6.6 release cycle. See the Roadmap Post for details about what is planned for this release.

WordPress 6.6 BetaBeta 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. 3 is scheduled for next Tuesday, June 18, and is the last scheduled beta before RCrelease 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. See the release schedule here.

@marybaum noted that the About page is currently in progress.

@joemcgill reminded everyone that we should be working on getting dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. published in the next 2 weeks before the field guideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. is finalized.

Next 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/ release: 18.6

Gutenberg 18.6 is scheduled for June 19 and will include these issues. This version will NOT be included in the WordPress 6.6 release.

Discussion

We didn’t have anything specific for discussion for this chat, as many folks were at WCEU.

We discussed how best to stay up to date with UIUI User interface changes in the Editor. @joemcgill noted that changes to the editor UI happen in the gutenberg repo, and are released first in the 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 so they can be tested before being included in a WordPress major release. Discussion about those changes generally happen in issues and PRs on that repo.

Additionally, plans for WordPress 6.6 were summarized in this Roadmap post, which may be a good way to see what else is changing so you can test and provide feedback before the final release.

@hellofromtonya also mentioned the #core-editor channel, which is helpful for when you’re looking for where to start and if a feature or change is in the works.

@colorful-tones added: Another means to keep up to date on the latest updates is to check out (and consider subscribing to updates in the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.) the WordPress Developer Blog. For example, the latest post: What’s new for developers? (June 2024) mentions this newer feature here.

@joemcgill also raised @dmsnell‘s excellently written proposal — Proposal: Bits as dynamic tokens — and recommended taking time to read it and provide feedback or ask questions in the comments of that post.

Open Floor

@oglekler kindly offered to help support Contributor DayContributor Day Contributor 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://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WCEU remotely, and contributors on the day were encouraged to join the #core Slack channel for help both on the day and going forward.

We also discussed not pinning the 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. scrub post, since it’s so long, and instead just link to it from the release page.

@ironprogrammer suggested posting a short signpost message pointing to the scrub, close comments, pin it. Or a sidebar update.

@joemcgill suggested exploring the excerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. feature on the Make team blogs.

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Props to @joemcgill for proofreading.

#6-6, #dev-chat, #summary

Performance Chat Summary: 11 June 2024

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

  • Welcome to our new members of #core-performance
  • 3.1.0 launched on June 6 to include new performance 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 assets
  • Early WordPress 6.6 BetaBeta 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. 1 performance results [GitHub issue]
    • Early investigations did NOT show a regressionregression A 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. at all, but instead shows that 6.6 Beta 1 is improved from 6.5.3 (conversation to be continued on the GitHubGitHub GitHub 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 be the repository owner. https://github.com/ issue)
  • Contributor DayContributor Day Contributor 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://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WordCampWordCamp 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’ve learned throughout the year and share the joy. Learn more. Europe, Turin, Italy on Thursday June 13

Priority Items

  • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
    • Current release (WP 6.6)
  • Performance Lab plugin (and other performance plugins)
    • Auto-Sizes for Lazy-Loaded Images
    • Embed Optimizer
    • Fetchpriority
    • Image Placeholders
    • Modern Image Formats
    • Optimization Detective
    • Performant Translations
    • Speculative Loading
  • Active priority projects

WordPress Performance Trac Tickets

Performance Lab Plugin (and other Performance Plugins)

  • @mukesh27 PR that ready for review:
    • PR #1298 – Audit Autoloaded Options Site Health should extend CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s check if available
  • @joemcgill Also worth noting that Chrome 126 is scheduled to ship today with auto-sizes support turned on, so we should be able to get better testing feedback soon from folks using that feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins..
    • @westonruter opened https://github.com/WordPress/performance/pull/1296 in order to do a quick minor releaseMinor 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. of Optimization Detective and could use reviews

Active Priority Projects

Improving the calculation of image size attributes

  • @mukesh27 has been working on improved image sizes algorithm
    • PRs merged:
      • PR #1250 – Initial implementation of improved image sizes algorithm
    • PRs ready for review:
      • PR #1290 – improved image sizes for left/right alignment
      • PR #1252 – Use correct sizes for small images

Optimized Autoloaded Options

Improved template loading

  • @thekt12 I have raised a new 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. #61405 (with a POC that currently breaks some tests ). Same pattern was also observed in WP_Theme_JSON_Data::$theme_json, but I am not sure of the performance impact it will have. PR#6781 will address the remainder of #57789 and #59600 ; estimated to give at least 3% improvement.

Open Floor

Our next chat will be held on Tuesday, June 18, 2024 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #performance, #performance-chat, #summary

Developer Blog editorial meeting summary, 6 June, 2024

Summary of the WordPress Developer Blogblog (versus network, site) meeting, which took place in the  #core-dev-blog channel on the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Start of the meeting in Slack.

Attendees: @greenshady, @ndiego, @webcommsat, @psykro, @colorful-tones, @milana_cap, @mobarak, @magdalenapaciorek, @juanmaguitar, @bph (as facilitator). @ironnysh and @bcworkz (async)

Last meeting notes: Developer Blog editorial meeting summary, May 2, 2024

Updates on the site

The site has passed the first 1,000 subscribers :rocket: Don’t want to miss the next blog post? Subscribe. And please share the links with your networknetwork (versus site, blog) as well. @webcommsat volunteered to submit an amplification request to the WordPress marketing team to celebrate the milestone with the community.

Newly published post since the last meeting: 

Since the last meeting, we published four articles.

Huge Thank you to the writer and reviewers! 

Project Status

The project board for Developer Blog content is on GitHubGitHub GitHub 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 be the repository owner. https://github.com/.

In review

In Progress:

Post on the To-do-list, assigned to writers.

Topics, approved, in need of a writer

If you are interested in taking on a topic from this list or know someone who would be a good person to write about them, comment on the Issue or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @bph in slack either in the #core-dev-blog channel or in a DM.

New Topics approved

Topic not approved:

The WordPress Developer Survey – A regular survey could give “the whole project a lot of useful data” There were concerns about logistical challenges and needs further discussion with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., the marketing team in its new media focus, and with Learn WP. The next step as identified as “to define the purpose of the survey, and what questions would be included/not included.” The discussion continues on GitHub

Open Floor

@webcommsat Inquired about topics schedule around the WordPress 6.6 release. There are a few posts already on the list or were just approved. As almost all topics are assigned to writers. Contributor’s bandwidth will determine the publishing timeline.

@colorful-tones requested input and possible resources on using Playground for his upcoming post on the developer Blog: a Good starting point is the Blueprint Gallery and an example from @greenshady on GitHub.

@colorful-tones has slightly changed the topic of his post he has been working on. It was originally thought to be an Interactivity APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. tutorial, but as you can read in the issue he went a different route. It was concluded that “it’s still a valuable post for the Dev Blog”, “the new focus is still really useful” and “the underlying method doesn’t need to be the same as the originally proposed method”

Next meeting: July 4, 2024, at 13:00 UTC in the #core-dev-blog channel

Props to @greenshady for review of the post.

#meeting, #meta, #summary

Summary, Dev Chat, June 5, 2024

Start of the meeting in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., facilitated by @mikachan. 🔗 Agenda post.

Announcements

  • WordPress 6.6 Beta 1 was released Tuesday, June 4! Thanks to all the contributors for a smooth and successful release. Please help test and report any issues you find.
  • WordPress 6.5.4 was released on June 5 and is now available for download. Thanks to all the contributors who worked on this release too! @jorbin noted that there is now a 6.5.5 milestone in tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., but suggests that we enter a holding pattern for ~2 weeks before deciding if it’s necessary.
  • 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/ 18.5 was scheduled for release on June 5 (completed after the meeting). This is the final release going into WordPress 6.6, and from this point only 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. fixes will be cherry-picked into the 6.6 branchbranch 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"..

Forthcoming Releases

Next major releasemajor release A 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.: 6.6

We are currently in the WordPress 6.6 release cycle. See the Roadmap Post for details about what is planned for this release.

Discussion

As we’re in the middle of the 6.6 cycle, we used the discussion time to check in on priority items for this release. Noting that an early look of the 6.6 source of truth has been published recently by @annezazu. This is usually particularly helpful for marketing, training, and docs at this stage. Feedback, questions, comments welcomed! Expect a finalized version in line with RCrelease 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). 2 on July 2nd.

@colorful-tones raised concern about whether pattern shuffling is suitable for 6.6 and identified a few items that came up right after BetaBeta 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. 1 that are on the WordPress 6.6 Editor Tasks board:

@joemcgill advised that if these are bugs, it is fine to fix during the beta period, but that they will need to be prioritized:

“…folks basically have the next 3 weeks do decide if these bugs should be fixed, if the feature should be removed, or if these are minor issues that don’t need to make the release. But punting the bugs is essentially committing to shipping the feature with known issues, so I would try to avoid punting them without discussion with folks closest to the features.”

@joemcgill also raised concern about the fact that we only have 3 weeks until RC1, which overlaps time that many contributors will be traveling and attending WCEU.

@marybaum requested that if we drop a feature, it would be fabulous to know that a week or so before RC 1 in order to update the About page prior to the RC 1 string freeze.

Open Floor

@apedog asked for someone to review #58932, which @joemcgill followed up on after the meeting.

@kkmuffme requested more attention to the following issues:

@joemcgill had reviewed these ahead of the meeting and mentioned that several were already too late to make this release. Specifically, the enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. tickets and one marked early. @hellofromtonya noticed that at least one needs deeper review because of a potential back-compat break.

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Props to @mikachan for proofreading.

#6-6, #core, #dev-chat, #summary

Performance Chat Summary: 4 June 2024

Meeting agenda here and the full chat log is available and the full chat log is available beginning here on Slack.

Announcements

  • Welcome to our new members of #core-performance
  • WordPress 6.6 betaBeta 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. 1 is today
  • Performance lab 3.2.0 release scheduled for June 6

Priority Items

Structure:

  • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
    • Current release (WP 6.6)
  • Performance Lab 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 (and other performance plugins)
    • Auto-Sizes for Lazy-Loaded Images
    • Embed Optimizer
    • Fetchpriority
    • Image Placeholders
    • Modern Image Formats
    • Optimization Detective
    • Performant Translations
    • Speculative Loading
  • Active priority projects

WordPress Performance Trac Tickets

  • WordPress 6.6 enhancement tickets
    • #61276 was just re-opened but the enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. is committed
    • @joemcgill The new Site Health check for large autoloaded options is committed https://core.trac.wordpress.org/changeset/58332. I also committed the caching improvements for generating global styles for blocks in https://core.trac.wordpress.org/changeset/58334
    • @spacedmonkey has several issues he would like reviewing #53167 #59595 and #59871
      • @joemcgill I committed the caching improvements that we’ve been working on and left a review on your PR, @spacedmonkey I think we could still consider making your proposed change, but the impact will be much smaller and should most likely start with a GB PR
    • @spacedmonkey I think that #53167 & #59871 are ready for commit IMO but we missed the cut off there
  • There are 9 performance tickets for 6.6, all of which are marked as bugs
    • @joemcgill The main one that I want a 2nd opinion on is #55996 and specifically this PR, which fixes 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. that the .org team ran into when trying to apply filters to blockBlock 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. content at the template level instead of the block level.

Performance Lab Plugin (and other Performance Plugins)

  • @westonruter Milestones for the plugins: https://github.com/WordPress/performance/milestones
  • @westonruter For 3.2.0 we’ll at least have the Upgrade Notice – I think we should discuss more what should be done there, whether we bring back the adminadmin (and super admin) pointer whenever there is a big new feature or if something else less obtrusive is warranted
  • @ashwinparthasarathi hoping to work on this https://github.com/WordPress/performance/issues/1239
    But it will probably make it in the next release.
  • @joemcgill states 1136 the main one that we need to try to get wrapped up
    • @stellastopfer Yes, we should get the last icon and the export today EOD
    • Active discussion on the ticketticket Created for both bug reports and feature development on the bug tracker. regarding the assets and agreed to go with just the “P” for now as we are short on time
  • Agreed to puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) the onboarding experience issue https://github.com/WordPress/performance/issues/1032
  • The last issue is https://github.com/WordPress/performance/issues/715 but it seems it won’t take much to get it over the finish line, with input from @adamsilverstein
  • @westonruter I submitted the Image Prioritizer plugin for review with the plugin review team. This includes the fetchpriority=high for the LCP image, including when there are different LCP image elements for different breakpoints. It also now includes applying correct lazy-loading so that images that appear in the initial viewport in any breakpoint never get lazy-loading whereas images outside the initial viewport in any breakpoint always get lazy-loading.

Active Priority Projects

Improving the calculation of image size attributes

  • @mukesh27 has been working on improved image sizes algorithm
    • PR that ready for review:
      • PR #1250 – Initial implementation of improved image sizes algorithm
      • PR #1252 – Use correct sizes for small images

Web Worker Offloading

Optimized Autoloaded Options

  • @joemcgill now that we’ve included the Site Health check, I think we can update the dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. draft and then close out that project. I’ve been waiting on the doc release leads to get a process setup that we can add our dev note to.

Open Floor

Our next chat will be held on Tuesday, June 11, 2024 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #performance, #performance-chat, #summary

Summary, Dev Chat, May 29, 2024

Start of the meeting in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., facilitated by @mikachan. 🔗 Agenda post.

Announcements

  • The scheduled date for WordPress 6.6 Beta 1 is June 4. From this point on, we will focus on testing and fixing bugs discovered during betaBeta 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. testing. Begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and the About page.
  • 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/ 18.4 was released on May 22. Read more about what was included in this release here.

Forthcoming Releases

Next major releasemajor release A 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.: 6.6

We are currently in the WordPress 6.6 release cycle. See the Roadmap Post for details about what is planned for this release. Gutenberg 18.5 RCrelease 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). is scheduled for May 31, which is the final RC before WordPress 6.6 Beta 1. It will include these issues and PRs.

Next maintenance release: 6.5.4

@jorbin has confirmed that there will be a 6.5.4 release scheduled for June 5, to accommodate #61269. An RC is scheduled for May 30.

@hellofromtonya shared that an alternate approach to #61269 is being considered for 6.5.4 and requested more feedback:

This could have an impact on the planned RC schedule for 6.5.4 depending on consensus on what approach to ship.

Discussion

With the Beta 1 deadline quickly approaching, we used the discussion time to check in on priority items for this release. Please review the list of Editor Updates from this week’s agenda for a list of updates of several key features related to this release.

@fabiankaegy has flagged that there are a number of commits that still need to be synced from the Gutenberg repo as part of this tracking issue. He also is tracking related PRs in this table on the WP 6.6 Editor Tasks board. Support from folks to review and commit these PRs is appreciated as we approach the 6.6 beta 1 deadline.

@joemcgill asked if the Release Squad needed any support to be ready for the 6.6 Beta 1 release next week.

@meher shared that all teams have reported a 🟢 status in the last check-in. Waiting for the Design and Performance to add their status. The documentation team has got help from folks.

Currently trying to decide whether the time to start Beta 1 should be 14:00 UTC or 16:00 UTC. Conversation about this continued after the meeting in the #6-6-release-squad channel.

Open Floor

Nothing was raised during Open Floor this week

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Props to @mikachan for proofreading.

#6-6, #core, #dev-chat, #summary

Performance Chat Summary: 28 May 2024

The full chat log is available beginning here on Slack.

Announcements

  • Welcome to our new members of #core-performance
  • Performance Lab 3.2.0 release date is June 6, 2024
  • WordPress 6.6 betaBeta 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. 1 is scheduled for Tuesday June 4

Priority Items

Structure:

  • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
    • Current release (WP 6.6)
  • Performance Lab 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 (and other performance plugins)
    • Auto-Sizes for Lazy-Loaded Images
    • Embed Optimizer
    • Fetchpriority
    • Image Placeholders
    • Modern Image Formats
    • Optimization Detective
    • Performant Translations
    • Speculative Loading
  • Active priority projects
    • Improve template loading
    • INP research opportunities
    • Improving the calculation of image size attributes
    • Optimized autoloaded options

WordPress Performance Trac Tickets

  • WordPress 6.6 enhancement tickets:
    • @adamsilverstein to test #53167 and aim to get it in beta 1
    • For #57789 @thekt12 added persistent cache to  get_theme_data . Yet to run it with existing unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. and take performance result. He will add a PR today for testing add it today for testing. Currently he is adding some last changes to https://github.com/WordPress/wordpress-develop/pull/6392 which will fix some unit test
    • @thekt12 has updated #59595 with https://github.com/WordPress/wordpress-develop/pull/6392 with the review changes. Suggest changes weren’t working fully as $metadata[‘name’] was not present for all the block_nodes so updated it even further. Also identified repetitive code in old function which is fixed
    • @mukesh27 has #61276 ready for review, it has lots of testing on this one
      • @johnbillion I think we already have a few site health checks that aren’t particularly actionable by an end user, so this shouldn’t be a blockerblocker A bug which is so severe that it blocks a release., but definitely something to consider
      • @joemcgill In the Performance Lab plugin, we include a way for end users to review the specific options that are being flagged and allow them to turn off autoloading for them. Still unsure if that functionality is ready for all end users, but the fact that this site health check can be enhanced with specific additional details is a nice starting point. We can always adjust the copy during betas as well. I think we’ll likely get more feedback once the Dev Notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for #42441 is published. Pairing the health check with this improvement seems like a nice affordance

Performance Lab Plugin (and other Performance Plugins)

  • @westonruter suggested moving the 3.2.0 performance lab plugin release date to June 6 to accommodate the newest designs for the new icons
  • @stellastopfer provided an update on the new Performance Lab icon set, and advised that option 2 is being voted the best set of icons
  • @westonruter On this note… For the onboarding experience I think timing is great to coincide with WP 6.5.4 to introduce redirection to the Performance screen when activating the plugin
  • Decision agreed to move Performance Lab plugin 3.2.0 release until after the WordPress 6.5.4 release on June 5
  • We have the first Performance Lab repo 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. scrub on Wednesday May 29
  • @westonruter Modern Image formats is close to wrapping a couple of PRs for merge – this ticket in particular by @adamsilverstein
  • @westonruter is etting very close to finishing the Optimization Detective refactor/extraction into Image Prioritizer dependent plugin

Active Priority Projects

  • @stellastopfer We now also have one project board that should cover all current and upcoming work. The board is still a bit of a WIP, but should get its final shape over the course of the next couple of weeks.
    • Hopefully, it will serve our team just as well as some of you lurkers out there, so you can get an idea on features added to upcoming releases, bug fixes and other improvements, but also discuss and contribute where you see an opportunity to do so.
    • The first next step would be to add all of the issues that are in progress, but aren’t there. Then we will triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and align on labels. I think there are some we can do without and others we can simplify.
    • If you click on the arrow in the tab, and go to Slice by > Milestone, it will open a sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. There you can choose the milestone you want to see card for and they will filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. on the right.
    • Only one milestone at a time. We could create a filter by due date. That would cover multiple
  • @joemcgill suggested we’ll probably need some follow-up or some documentation on how we want to use the board (best practices, tips, that sort of thing), but this is an amazing start and should help us organize visibility of our work much better.

Improving the calculation of image size attributes

  • @mukesh27 has been working on improved image sizes algorithm. And asked @joemcgill to please review it when you have moment.
    • PR that ready for review:
      • PR #1250 – Initial implementation of improved image sizes algorithm
      • PR #1252 – Use correct sizes for small images

Open Floor

Our next chat will be held on Tuesday, June 4, 2024 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #performance, #performance-chat, #summary

Summary, Dev Chat, May 22, 2024

Start of the meeting in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., facilitated by @joemcgill. 🔗 Agenda post.

Announcements

  • The scheduled date for WordPress 6.6 Beta 1 is June 4, which is less than 2 weeks away. From this point on, we will focus on testing and fixing bugs discovered during betaBeta 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. testing. Begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and the About page.
  • @ellatrix recently announced that the last 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/ release to go into WP 6.6 will have an RCrelease 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). next Friday, May 31.

Forthcoming Releases

Our next major releasemajor release A 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. is WordPress 6.6. See the Roadmap Post for details about what is planned. Also, see the Bug Scrub post for more details on when the 6.6 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. scrubs are happening.

@jorbin requested that we discuss the potential of doing a 6.5.4 release to accommodate #61269, and noted:

@hellofromtonya, @costdev and myself have been working through some options to help solve some issues that cropped up from 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 dependencies and are proposing #61269 as a solution that we would like to get in the hands of users as soon as possible.

Our suggestion is that we do a very small focused 6.5.4 on 5 June with an RC on 30 May. I am not currently aware of any other issues but would be open to including other fixes. I know it’s not much time for feedback, but am open to it as far as the schedule goes and also open to other tickets folks want to raise for inclusion.

The feedback that would be most helpful:

  • Testing and review of the proposed patchpatch 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.
  • feedback on the schedule,
  • proposal of additional issues that should be considered for the release if any

@jorbin also highlighted that we will need someone with MC access, someone with a metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. sandbox, someone who can create a helphub page. Please reach out if you can help with any of these tasks.

The next GB release, Gutenberg 18.4, is going out soon and includes these issues. As mentioned during the announcements section of this chat, that means the following GB release (18.5) will be the last one planned to be included in WP 6.6. Now’s a very important time to be testing and reviewing PRs that are being synced from that repo to trunktrunk 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..

Discussion

Ahead of the meeting, @annezazu highlighted the following updates on features for 6.6 – please help review and provide feedback as you can!

  • About a 10 minute long video demo of zoomed out view and where things stand, including current challenges with adding it to the pattern insertion experience. As it stands today, it looks like the zoomed out experience to build with patterns won’t be ready but will be an experiment in the plugin.
  • Block bindings latest update including a run down of merged PRs, risks for the release, and next steps. As it stands today, it looks like having the functionality to allow editing of custom fields when connected to blocks will likely not be ready for 6.6.
  • Section styling has a new discussion around CSS specificity which is necessary to resolve for the feature to land. There is potential breakage that might happen with the zero specificity styles and an alternative plan presented to preserve backwards compatibility.

@fabiankaegy and @colorful-tones have been doing great work triaging the WP 6.6 Editor Tasks board as well.

@vcanales mentioned the following issues in the WordPress 6.6 Editor Tasks board that are up for grabs for developers:

Open Floor

@dmsnell mentioned the HTML API: we’re getting nervously close to the deadline but still on task for our two main updates:

  • adding a spec-compliant text decoder
  • refactoring the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. Processor so that it always presents a normalized “perfect” view of the HTML it’s parsing

@dmsnell mentioned that the best way to support this project is to review the work or share thoughts about how it’s all structured. The WP_Token_Map (Core-60324) is the biggest general thing in view and everyone is invited to share input on it or on the dev note I’ve prepared.

@dmsnell also raised two other tickets:

  • #61009 allows storing the proposed “Bits” syntax, making it possible for experimentation inside Gutenberg.
  • #61052 allows storing custom data attributes containing dashes, which is what the Interactivity APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. relies on.

The first one opens up the ability for Gutenberg to start experimenting with Bits, which are “Shortcodes, 2.0”, or dynamic tokens for externally-sourced data. This could use security review and scrutiny but is quite small in scope. The idea is that these can appear with a name and attributes which denote that something will replace it when rendered, but where Blocks are big, Bits are small, for example:

<//wp:post-meta key="isbn">

The main discussion around this is here.

The second ticketticket Created for both bug reports and feature development on the bug tracker. is about aligning kses with the needs of the Interactivity API. There is more information in this ticket. It would also be helpful to have more eyes and scrutiny on the way that this has been implemented.

For more information about both of these tickets, please read @dmsnell‘s messages during the dev chat from here.

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Props to @joemcgill for proofreading.

#6-6, #core, #dev-chat, #summary

Summary, Dev Chat, May 15, 2024

Start of the meeting in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., facilitated by @annezazu. 🔗 Agenda post.

Announcements

A reminder that the WordPress 6.6 roadmap has been published. Please also read and leave feedback on the Server to client data sharing for Script Modules proposal. Feel free to leave feedback either during Dev Chat or on the proposal post.

Forthcoming Releases

We’re currently in the WordPress 6.6 release cycle. You can find out more about the release squad in this post.

@annezazu noted that after a discussion in the public #6-6-release-leads channel, there is an update underway for the remaining roles yet to be filled. This has now been posted here.

For any folks who want to learn more about the release and help contribute back, I want to call attention to this post on Early opportunities to Test WordPress 6.6. Help the release and learn about it at the same time!

Discussion

Release Squad: A lengthy discussion ensued about the fact that 3 weeks from BetaBeta 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. 1 that the full release squad has not been filled. There were questions about why this release has been so hard to fill and what we could do to improve this in the future. Some questioned the size of the release squad making it difficult to fill and others questioned the length of the cycle. Suggestions were made to try to recruit a release squad earlier in the cycle, or even at the end of the previous cycle.

Note: Since the meeting, the WordPress 6.6 release squad is ready.

Canonical blockBlock 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. plugins proposal: There is an initial issue and discussion here, and a follow-up Gutenberg PR is currently in progress to create a time to read block. Have folks had a chance to catch up here? Any questions or concerns?

  • @jeffpaul questioned what problem this would solve compared with either shipping these blocks in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. or allow them to be maintained as community plugins.
  • @jorbin expressed support for the idea, but identified that there were some questions that need to be answered in addition to what @grantmkin shared in this GitHub comment.
  • @annezazu shared that the difference is useful in that some blocks haven’t been a great fit for Core, for a variety of reasons. This separation allows the base experience to remain the same while offering strong, supported blocks provided by Core that folks can add on.
  • This was a lengthy discussion. Everyone is encouraged to provide feedback on the related issue.

Proposal: Server to client data sharing for Script Modules: This proposal is still looking for feedback.

Open Floor

@kkmuffme requested guidance on several tickets that have stalled, that he is hoping will get picked up in time for the 6.6 release. Following the meeting, @jeffpaul scrubbed the list and pinged relevant core developers who might be able to review and provide feedback.

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Props to @mikachan for proofreading.

#6-6, #core, #dev-chat, #summary