Performance team meeting summary 19 July 2022

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

Announcements

• @shetheliving: Our new blog is live at https://make.wordpress.org/performance/! How should we use this moving forward?
  • @flixos90: Thinking we continue to post meeting notes, etc. on Core and cross-post them to Performance
  • @pbearne: Could we use it for articles about performance best practices?
  • @flixos90: Main purpose is to have a single entry point for everything and a handbook for onboarding and best practices
  • @flashusb: Could we have an Email Updates widget like the other blogs?
  • @flixos90: Would be great to have a sticky at the top explaining that the blog is primarily for cross-posting and link to where most of our content is, including https://make.wordpress.org/core/tag/performance/, https://make.wordpress.org/plugins/tag/performance/, and https://make.wordpress.org/themes/tags/performance/
  • @ollliejones: Can it serve as a place for “more details” articles or site health check results?
  • @flixos90: More about contributing to the team and what the team is doing
  • Moving forward, we’ll continue to post agenda and notes on the Core blog and cross-post to Performance
  • @shetheliving will draft a sticky post for the Performance blog and look into an email updates widget in the sidebar

Focus group updates

Images

@adamsilverstein @mikeschroder

GitHub project

• @adamsilverstein: Finishing up work on the WebP/multi-mime type feature; @flixos90 has reviewed and added several new tests on the PR. Also updated the patch on the Trac ticket and would welcome feedback. Planning to commit later this week and once it lands there are already several follow-up pieces that are being worked on and need review. Also a few bugs related to WebP planned to review: https://core.trac.wordpress.org/ticket/54476 and https://core.trac.wordpress.org/ticket/53669
• @mukesh27: Working on Enhance JS replacement mechanism for WebP to JPEG to more reliably replace full file name #426 and Working on post meta solution for #395
• @joegrainger: Working on Continue research for Regenerate existing images #24 and Continue research for Update WordPress core functions to support multiple mime types #155
• @mehulkaklotar: Working on core patch updates for WebP, including Remove additional image backup sources & sizes files when attachment deleted #411
• @pbearne: With regenerate existing images, can @joegrainger also check that this creates dominant color metadata? He will check
• @spacedmonkey: Been working with @pbearne on the Dominant Color core patch
• @pbearne: Core patch should be ready with fixes to other unit tests, and core proposal will be published today

Feedback requested

• See above
• Needs Discussion (7 issues)
• Needs Dev (1 issue)
• Needs Review (1 issue)

Object Cache

@tillkruess @spacedmonkey

GitHub project

• @spacedmonkey: Reviewing some work from @tillkruess: https://github.com/WordPress/wordpress-develop/pull/2967 and https://github.com/WordPress/wordpress-develop/pull/2969
• @tillkruess: https://github.com/WordPress/wordpress-develop/pull/2967 could use some refinements but reviews are greatly appreciated; https://github.com/WordPress/wordpress-develop/pull/2969 could use another review
• @spacedmonkey: Needs review:
  • https://github.com/WordPress/wordpress-develop/pull/2684 – Biggest win and only blocked by a param name; tests are solid
  • https://github.com/WordPress/wordpress-develop/pull/2478 – Waiting for feedback and testing
• @spacedmonkey: On leave 25th July to 5th September

Feedback requested

• See list above
• Needs Discussion (3 issues)
• Needs Review (2 issues)

Site Health

N/A

GitHub project

• We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
• @furi3r: Posted feature proposal for Audit Full Page Cache and Full Page Cache Site Health Checks last week; no feedback yet
• @spacedmonkey: How long do we wait for feedback? https://github.com/WordPress/wordpress-develop/pull/2890 has been approved by two core committers so could be merged ASAP
• @flixos90: We’re not in a massive rush, wait 2 more weeks for feedback and then merge
• @spacedmonkey: Won’t be around, so someone else will need to merge

Feedback requested

• Needs Discussion (6 issues)
• Needs Review (1 issue)

Measurement

N/A

GitHub project

• We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
• No updates

Feedback requested

• Needs Discussion (5 issues)
• Needs Review (1 issue)

JavaScript

@aristath @sergiomdgomes

GitHub project

• No updates

Feedback requested

• Tree-shaking block styles on the frontend #41020
• Needs Discussion (2 issues)
• Needs Review (3 issues)

Infrastructure

@flixos90

GitHub project

• @flixos90: Published 1.3.0 yesterday and broke 7k active installs for the Performance Lab plugin
• @mukesh27: A few PRs that need review:
  • Fix unexpected input Warning message during release build/test process #437
  • PHPCS: Use a period at the end #436
  • Add constant for plugin_dir_path #429

Feedback requested

• See above
• Needs Discussion (4 issues)
• Needs Review (1 issue)
• Needs Dev (1 issue)
• Needs Testing (1 issue)

Open Floor

• @mukesh27: How about a weekly Bug Scrub for the performance channel for performance-focused Trac tickets? We have a total of 326 right now
  • @shetheliving: Was this intended to be a weekly scheduled meeting?
  • @mukesh27: Yes, if possible
  • @spacedmonkey: There are lots of core issues that are impossible to fix in the plugin and need to be fixed in core
  • @flixos90: Yeah, probably most Trac tickets should be fixed directly as core patches; only tickets that need to be implemented as bigger features should become plugin modules. Always depends on whether core has the necessary integration points to handle that or not.
  • @shetheliving: Weekly may be tough, how about monthly? Let’s start with the first Wednesday of the month at our regular meeting time, so our first one would be August 3, 2022, at 15:00 UTC

#core-js, #core-media, #performance, #performance-chat, #summary

#hosting-community