Focus area updates
- @mukesh27: Working on Regenerate thumbnail duplication webp file #575
- @mxbclang: Noting a few items that are able to picked up if anyone has interest/capacity; see Needs Dev below
fetchpriorityexperimental module was merged last week and is planned for release in v1.8.0 in December
- @spacedmonkey: Focusing on
theme.jsonparsing issues, so lots of code review. Working on:
- No updates
JS & CSS
- No updates
- @mxbclang: What are the next steps on Revisit indexes for DB performance #132?
- @olliejones: Current voting winner points to doing something dbms-version-specific to the schema, eventually in core, think we can do this in the plugin if we’re willing to accept a mu-plugin drop-in module. Disadvantage here is complexity.
- @flixos90: This is tricky – we have a voting winner, but also some strong opinions from different sides including a WP lead developer.
- @mxbclang: Seems like the best next step here would be to close out the vote as planned but hold on next steps pending further discussion in the issue, then regroup on this in a future chat
- All agreed; vote will close and @mxbclang will add a comment about next steps
- @olliejones: SQLite Object Cache is coming along nicely; will create a new module proposal issue once it’s closer to complete
- @olliejones: For future discussion: Do we need some sort of formal set of filters, etc. to support the big competent hosting providers in this back-end area?
- @flixos90: Been working on iterating on the Server-Timing API PR. Still in draft because unit tests need to be added, but ready for review. Would love feedback and opinions on the API implementation. The most important recent change is that it is now initialized early through a drop-in, so it can capture measurements that happen before WP plugins are loaded.
- @olliejones: There’s a sustainability team forming – see #sustainability Slack channel
- @nickchomey: Been working on implementing a real PWA for a site under development. Plugin options are limited right now but @westonruter‘s plugin is the right approach. Is this something that the performance team can move forward?
- @flixos90: Not sure what the current state of the plugin is; original idea was for it to be a feature plugin
- @nickchomey: Proposing a real coordinated effort be made to improve it to the point that it could be merged into core
- @flixos90: It could definitely be feature plugin material, but as always it requires resources. If a small group is up for tackling, we would be supportive and help here possible.
- @westonruter: The plugin is stable and essentially in maintenance mode. Not clear if there is the 80% user benefit to justify core merge just yet. See discussion between @nickchomey and @westonruter in GH issue: https://github.com/GoogleChromeLabs/pwa-wp/issues/884.
- @flixos90: Key aspect of proposing this for core would be to come with an actual usage of PWA capabilities that immediately benefits core users
- @westonruter: Benefit that all users could get now is offline browsing on the front-end, but there’s a separate concern of what happens when a large portion of the web is registering service workers
- @pbearne: Aren’t we going to need something like this for real-time multi-editing in Gutenberg?
- @olliejones: Maybe the Twenty Twenty Four theme could be made PWA-friendly?