Performance team meeting summary 17 May 2022

Table of Contents

Announcements

@shetheliving: Do we want to cancel our 31 May meeting due to WCEU?
- Thumbs up/thumbs down poll here
- 4 voted to keep and 8 to cancel, so we will cancel

@adamsilverstein: Work continuing on WebP integration points in Ensure WebP/Image/Optimization plugins can integrate & use existing WebP images #160 and on bringing over features from the plugin that aren’t in the core patch yet, including featured images, always using the smallest image, and edit/restore functionality. Research continues on Research: Impact of additional WebP images on upload #289 and Research: WebP compatibility #290, and to help answer questions around the impact of additional files, we’ve created a survey which was shared in the #hosting-community channel. This will be open for the next few weeks, then we’ll collate results and report back.
@mitogh: Wrapping up PR for Ensure edited image sources are backed up when restoring the original image #295 this week
@spacedmonkey: Continuing review on Add low quality image placeholders #19
- @flixos90: Excited for this to land, let’s double down on getting it ready for 1.2.0

N/A

We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
@furi3r: Add Site Health test for full page caching (advanced cache) #220 was moved to 1.2.0 is just about ready and waiting for testing

N/A

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

@shetheliving: Review the module proposal workflow and leave any feedback on the PR
- @flixos90: We’ve been working on this to have a long-term plan for each module; want to avoid a module going into the plugin and growing stale without any iterations or next steps
- @jeffpaul: I’ll review with an eye from the core perspective
- @flixos90: Another benefit of this documentation is that it includes a high-level overview of how to propose a feature project for core, which isn’t really documented right now; this could be a good starting point for the future
@olliejones: Might be cool to have a stub performance-lab module for modification by would-be contributors
- @flixos90: That’s a great idea, though there would be little to start with since a module can be pretty much anything. The best place to start right now is with the writing a module doc, though that’s more about the technical starting point and the new proposal doc is more about overall workflow.
@flixos90: Released v1.1.0 yesterday. Next release will be 1.2.0 on Monday, June 20, so we should target merge for anything for that release by about June 15.