This is the agenda for the meeting. You can read the logs here on Slack.
Focus group projects discussion
This is an asynchronous update about the progress for the Site Health group, shared by @audrasjb:
- The existing and future Site Health checks will be moved to the Performance mono repo
- We received some feedback, the idea is to create issues to discuss them on GitHub GitHub is a website that offers online implementation of git repositories that can 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/
- @audrasjb will be available to work on this after 5.9 second beta 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.
@furi3r also offered to bring the work done here in a module, on the performance plugin 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 repository.
There has been no major progress for this group since the last discussions. Hopefully we will see more after the 5.9 release.
@adamsilverstein shared that the team is continuing the Asia/Pacific timezone friendly meetings Thursdays at +02:00 UTC. They’ve started work on some initial tickets related to WebP: creating an initial module for WebP on Uploads, and researching optimal compression/quality settings for WebP (and eventually AVIF) images in this issue.
About this top, @blogaid expresses some serious concerns they have about creating WebP on uploads. This is being discussed in this issue. Please leave a comment there if you have an opinion about this.
@tillkruess migrated the POC document for this group to a dedicated project on the GitHub repository. In addition to that, more details were added on the issues, based on the feedbacks of the focus group members.
We have discussed the offer to use Platform.sh and Blackfire for being able to run automated performance tests against pulls requests and branches. Discussions on this are happening on this issue.
There is also a suggestion by @wp-source to use Lighthouse CI and CrUX to make synthetic tests on PRs. You can read the discussions about this proposal here on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. See also this issue about creating a standard VM for performance testing of WordPress.
@tweetythierry proposed a discussion topic for the next meeting. About how we could improve the theme checker (and introduce a plugin check) with some performance “warning”. It could start simple by warning about enqueueing best practice or checking the number of assets enqueued and their sizes.