Emily Clarke 4:55 pm on March 26, 2024
Tags: , , ,   

Performance Chat Summary: 26 March 2024

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

Announcements

  • Welcome to our new members of #core-performance
  • WordPress 6.5 delayed (see blog post):
    • 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). 4 will be March 28
    • Release April 2
  • Performance Team have launched two new plugins
    • Optimization Detective 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
    • Embed Optimizer plugin
  • Reminder on timezone difference for this week, this chat will remain at 16:00 UTC and then shift to 15:00 UTC from April 2, 2024

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
    • Future release
  • Performance Lab plugin (and other performance plugins)
  • Active priority projects
    • INP research opportunities
    • Improve template loading

WordPress Performance Trac Tickets

  • For WordPress 6.5:
    • @flixos90 Nothing concrete, though since part of the reason for the release delay is changes to the Font 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., we should probably keep an eye on that it doesn’t regress performance. As far as I understand the scope of the changes, it shouldn’t… but still worth staying on top of
  • For Future Releases:
    • We already have 14 open items in the 6.6 milestone
    • @flixos90 update on #42441 (enhancing autoload API and disable autoload for large options) – The PR has two approvals and looks excellent to me, so I’ve marked the ticketticket Created for both bug reports and feature development on the bug tracker. for commit
      • Going to wait for a few more days to see if any additional feedback comes in, but generally plan to commit this next week so that we can get a lot of testing during the 6.6 release cycle

Performance Lab Plugin (and other Performance Plugins)

Active Priority Projects

    Improve template loading

    INP research opportunities

    • @adamsilverstein As promised, I have collected the results of my INP research and am sharing now in this summary doc (along with a linked spreadsheet with all the data). If you want access to the colab and queries, please request it directly in the colab.
      • The summary doc Analysis section highlights some notable data for both coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and plugins/themes (with action items) that will be worth investigating further. Since there is a ton to absorb there, I think its best to leave comments/questions on the doc itself so we can discuss async, and maybe we can discuss further at a subsequent meeting.

    Open Floor

    • @pbearne one ticket from the old tickets https://core.trac.wordpress.org/ticket/29717 might worth looking at
    • @joemcgill We’ve traditionally done a post following a 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. which gives an overview of the performance characteristics of that release. I was planning to draft one for 6.5 once we can take a final set of benchmarks, but I’m assuming that we’re going to end with similar metrics to what we’ve been seeing in the last several RCs, since we’ve not had any new improvements or regressions. I’ll also include details about the editor improvements, but that doesn’t effect any of the CWV metrics we’ve been focusing on. I’d appreciate any thoughts folks have about how to communicate the performance of 6.5 clearly, while accurately reflecting that our benchmarks do NOT show an improvement over the previous release.
    • REMINDER: This meeting will switch to 15:00 UTC from April 2 (next week) onwards

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

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

    Jonathan Desrosiers 11:40 pm on March 25, 2024
    Tags: , ,   

    WordPress 6.5 release delayed 1 week

    Based on community feedback on the Unblocking WP6.5 – Font Library and Synced Pattern Overrides and Font Library follow up posts, there has been a change to the WordPress 6.5 release schedule and a final change to the Font Library. 

    The release of WordPress 6.5 will be delayed one week and is now scheduled for release on Tuesday, April 2nd, 2024.

    The delay is to accommodate the following:

    • The directory for font storage will be changed to wp-content/uploads/fonts.
    • The Editor team will work on including fixes for a select few high impact bugs that have been identified with the Font Library feature in the upcoming 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.0.0 release. This ensures they will receive some testing before being considered for merge into trunk prior to WordPress 6.5 RC4.
    • An unplanned WordPress 6.5 RC4 is now scheduled for release on 28 March 2024 at 16:00 UTC with the updated font storage location and any other related bugs deemed critical to the release. This will be a normal release candidaterelease 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)., with the announcement being published on the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ News blogblog (versus network, site) for extra reach.
    • The 1 week delay allows for ample time for testing, acknowledging that Thursday-Monday is a major holiday for parts of the globe.

    Why the change?

    This approach ensures that the greatest number of sites possible can benefit from the new Font Library feature without the need to install or configure anything.

    While attempting to implement the originally suggested compromise, the sentiment from the trusted contributors involved was that a solution could not be shipped with a level of confidence that meets the standards that core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. hold themselves to in the remaining time before the originally scheduled release.

    After evaluating the potential options and discussing the proposed solution, the most risk averse option was determined to be storing fonts in the wp-content/uploads/fonts directory.

    Shipping a feature that requires additional configuration or technical knowledge isn’t in line with the guiding philosophies that have helped the project mature into the successful project that exists today. Part of the original post was a call to return back to those project philosophies, and something this change attempts to adhere to.

    The Dry run post will be updated to reflect the schedule for the new release date of 2 April.

    Post release

    Following the 6.5 release, these items detailed in the original post should still be explored:

    • A roadmap will be published outlining where the project components are headed in relation to establishing new first-class concepts outside of previously established paradigms within the software (like breaking down themes into fonts, patterns, templates, etc.). Why was this such an important and impactful decision? What is the goal we are trying to accomplish? And how might it present itself again in the future?
    • A means to move the canonical location of the fonts directory. Should the wp-content directory become writable for a site, a safe path forward should be offered for its owners.
    • Explore whether additional checks should be added to Site Health.

    Props to @desrosj, @davidbaumwald,@hellofromtonya, @chanthaboune, @peterwilsoncc, @priethor, @jorbin, @annezazu, @akshayar, & @courane01 for pre-publish review.

    #6-5, #core, #release-process

    Emily Clarke 1:07 pm on March 25, 2024
    Tags: , , ,   

    Performance Chat Agenda: 26 March 2024

    Here is the agenda for this week’s performance team meeting scheduled for Mar 26, 2024 at 16:00 UTC.

    • Announcements
      • Welcome to our new members of #core-performance
      • WordPress 6.5 delayed:
        • 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). 4 will be March 28
        • Release April 2
      • Performance Team have launched the new Optimization Detective plugin
      • Reminder on timezone difference for this week, this chat will remain at 16:00 UTC and then shift to 15:00 UTC from April 2, 2024
    • 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
        • Future release
      • 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)
      • Active priority projects
        • INP research opportunities
        • Improve template loading
        • Plugin checker
    • Open floor

    If you have any topics you’d like to add to this agenda, please add them in the comments below.

    This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

    #agenda, #meeting, #performance, #performance-chat

    Akshaya Rane 11:16 am on March 22, 2024
    Tags: , ,   

    WordPress 6.5 Release Day Process

    UPDATE: Following Font Library-related discussion the release party has been rescheduled to April 2nd, 2024.

    Preparation for the WordPress 6.5 release is underway.

    This post shares the release process, including the timeline and how you can help.

    Release Timeline Overview

    Dry Run

    The Dry Run is a key event as a final walk-through for the final release. As noted above, this is scheduled on April 1, 2024 in the #core Slack channel.

    What happens usually during the dry run?

    • Bug reports are reviewed to determine if any are critical to warrant another 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). (release candidaterelease 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).).
    • Checks and any necessary updates are made in the src/wp-adminadmin (and super admin)/includes/update-core.php file.
    • Pre-release scripts are run to ensure test suites, coding standards, and other automated checks pass.

    If the results are acceptable, the release will go into a 24-hour code freeze period.

    24-Hour Code Freeze 

    After the dry run and before the release party starts, a mandatory 24-hour code freeze goes into effect.

    What does this mean? No source code for 6.5.0 (i.e., in the 6.5 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".) can be changed during these 24 hours.

    What happens if a critical 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. is reported during this period? The release squad will meet with committers and maintainers to determine if the issue is a blockerblocker A bug which is so severe that it blocks a release..

    • If yes, another RC release happens, and the release process restarts (meaning the dry run is repeated, and then the 24-hour code freeze clock restarts).
    • If not, then the bug is targeted for 6.5.1.

    The Release Party 📅

    The WordPress 6.5 Release Party will start on Tuesday, April 2, 2024 at 18:00 UTC in the  #core Slack channel.

    The release party walks through the steps in the Major Version Release process for anyone who wants to follow along.

    Please note releasing a major version requires more time than releasing a 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. or release candidate. There are more steps in the process. If any last-minute issues need addressing, more time will be needed.

    How You Can Help

    A key part of the release process is checking that the ZIP packages work on all the available server configurations. If you have some of the less commonly used servers available for testing (IIS, in particular), that would be super helpful. Servers running older versions of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher and MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. will also need testing.

    You can start this early by running the WordPress 6.5 RC4 packages, which are built using the same method as the final packages.

    During the release party, options will be provided on how to help test the release package.

    Tips on What to Test

    In particular, testing the following types of installs and updates would be much appreciated:

    • Does a new WordPress install work correctly? This includes running through the manual install process, as well as WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ or one-click installers.
    • Test upgrading from 4.0.38, 4.9.22, 5.8.6, 5.9.5, 6.0.3, 6.2.2, 6.3.0, 6.4.0, 6.4.1, 6.4.2 and 6.5 RC3, as well as any other versions possible.
    • Remove the wp-config.php file and test a fresh install.
    • Test single site and multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site/networknetwork (versus site, blog) (both subdirectory and subdomain) installations.
    • Does it upgrade correctly? Are the files listed in $_old_files removed when you upgrade?
    • Does multisite upgrade properly?

    Testing the following user flows on both desktop and mobile would be great to validate each function as expected:

    • Publish a post, including a variety of different blocks.
    • Comment on the post.
    • Install a new 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/theme, or upgrade an existing one.
    • Change the site language.
    • If you’re a plugin developer, or if there are complex plugins you depend upon, test that they’re working correctly.

    For a more in-depth list of what features to test, make sure to check the Help Test WordPress 6.5 post.

    Thanks to @davidbaumwald, @priethor for the peer review.

    #6-5, #core, #release-process

    Peter Wilson 10:51 pm on March 21, 2024
    Tags: , dev-note, ,   

    Font Library update: storage of font files

    This post has been superseded by the post WordPress 6.5 release delayed 1 week, in which it’s announced fonts will be uploaded to the fonts sub-directory of the uploads folder.

    The Font Library, a new feature of WordPress 6.5, will allow users of 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. editor themes to upload and customize their site’s fonts. You can learn about the full set of Font Library features in the #dev-note.

    As fonts are a new first-class object, there has been some discussion around where to store the associated files while accounting for different file systems used by WordPress sites. The particular challenge has been for file systems that do not allow for the writing of files outside the uploads directory (See Gutenberg#59417 and Gutenberg#59699).

    To account for such file systems, it was originally decided to natively fallback to the uploads directory natively in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

    Revised approach to font file storage

    Exploratory work on supporting a fallback directory natively has demonstrated that this approach would lead to a high risk of bugs. Therefore, the original decision is being modified and the new approach will be:

    • WordPress Core will by default only attempt to store font files in the wp-content/fonts directory,
    • For file systems unable to write to or persistently store files in the new directory it is recommended to install the 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 Fonts to Uploads to store the files in the under existing uploads directory, in wp-content/uploads/fonts
    • Developers wishing to modify the directory without using a plugin can use the font_dir 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. documented in the announcement post.

    Props @mmaattiiaass and other contributors for working on the exploratory pull request.

    Thank you @desrosj, @priethor, @chanthaboune and @jorbin for contributing to and reviewing this post.

    #6-5, #dev-notes, #dev-notes-6-5

    Sarah Norris 7:30 pm on March 21, 2024
    Tags: , ,   

    Summary, Dev Chat, March 20, 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.

    Announcements

    WordPress 6.5 RC 3 was released on March 19, 2024, and Gutenberg 17.9 was released on March 13. Please continue to help test and provide feedback.

    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.5

    We are in the final week before WordPress 6.5 is scheduled to be released, with a Dry Run scheduled for next Monday, March 25, and the release scheduled for Tuesday, March 26.

    @swissspidy and @sergeybiryukov will both be around to help during the Dry Run.

    Please continue to test the 6.5 release. See this list of key features to test, which was published alongside WP 6.5 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.

    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.0

    Gutenberg 18.0 is scheduled for release on March 27 and will include these issues.

    Discussion

    Given that this was the last dev chat before the 6.5 release, we concentrated on discussing any final decisions, blockers, etc.

    @swissspidy suggested starting with the Font Library:

    From what we’ve seen so far, it seems that adding such a fallback logic appears to be more complex than originally anticipated and that it’s not feasible to land this in time for 6.5. Adding a silent fourth 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). solely for that would be too risky.
    So for 6.5 we might want to consider:
    1. Leave the current situation as-is (fonts go to `wp-content/fonts`, no fallback)
    2. Point people to plugins such as Fonts to Uploads and the dev-note explaining how to change the upload location.
    3. Re-evaluate fallback logic for 6.5.1 or 6.6 if needed, also considering potential folders in the future (patterns, templates, AI models, etc.)

    We discussed how the fallback logic is proving to be more complicated than expected and will present a future maintenance burden and potential for bugs that aren’t worth the risk of rushing to land a fix. We mentioned alternative options, including delaying the release and removing the Font Library.

    The suggestion from release leads and people familiar with the latest state of the Font Library was that it is in a good enough shape to include, and that the difficulty is in the implementation of the potential automatic fallback and not in implementing the feature itself. Therefore, the plan following the conversation was that the feature will be shipped without the fallback logic in place.

    Based on this, the following actions should be taken:

    1. A post on make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to communicate the decision — @peterwilsoncc offered to start on a draft
    2. Update the docs with a pointer to the 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 — @flexseth offered to help update docs (@mikachan also happy to help here)
    3. Update https://wordpress.org/plugins/fonts-to-uploads/ to a Canonical plugin with maintenance by WP Contributors/WP.org with source moved under the WP org 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/ so that it’s a shared responsibility
    4. Once the post outlining the decision to change to the the fallback directory behavior is posted, we should inform #forums, along with a request from them to be on the lookout for issues with the lack of a default Font Library fallback — @jorbin offered to help with this

    Also related to the Font Library, @grantmkin noted that there is a wordpress-importer PR that needs review if someone has expertise and availability.

    Highlighted posts

    The full list of posts from the last week in Core can be read on the agenda at this link.

    Open floor

    There were two issues raised on the agenda:

    1. Would the fix for plugin zip file uploads be included in 6.5?
      • Yes, the fix is merged into 6.5
    2. Will we have an extra RC, since there are some unresolved Font Library tasks?
      • There is currently no extra RC release planned

    When discussing whether we needed another RC, the suggestion was to release an RC for any necessary Font Library changes (or any additional needed code changes) later this week, while the $_old_files change and theme bumps are handled during the Dry Run without publishing an extra RC.

    @joemcgill closed the chat by suggesting that if the purpose of an RC is to allow time for more testing, to not make it silent, and encourage the release leads to finalize a plan. Coordination about an extra RC continued following the meeting in the release leads channel.

    Props to @joemcgill for reviewing.

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

    Sarah Norris 9:45 am on March 20, 2024
    Tags: ,   

    Agenda, Dev Chat, Wednesday March 20, 2024

    The next WordPress Developers Chat will take place on  Wednesday March 20, 2024 at 20:00 UTC in the core channel on Make WordPress Slack.

    The live meeting will focus on the discussion for updates on 6.5, and have an open floor section.

    Additional items will be referred to in the various curated agenda sections, as below. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this agenda.

    Announcements

    WordPress 6.5 RC 3 was released on March 19, 2024. Thanks to everyone involved and those who helped test.

    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.5

    Updates from the release squad can be shared in the Dev Chat.

    Please continue to test the 6.5 release. See this list of key features to test, which was published alongside WP 6.5 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.

    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.0

    Gutenberg 18.0 is scheduled for release on March 27 and will include these issues.

    Discussions

    This week the discussion will focus on any priority topics that need to be raised before the launch of WordPress 6.5.

    Proposed topics

    • Are there any priority topics needed for discussion ahead of the WordPress 6.5 release?
      • Is there a need for a silent 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).?

    Feel free to suggest additional topics related to this release in the comments.

    Highlighted posts

    CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Updates

    Tickets for assistance

    Tickets for 6.5 will be prioritized.
    Please include detail of tickets / PR and the links into comments, and if you intend to be available during the meeting if there are any questions or will be async.

    Open floor

    Items for this can be shared in the comments.

    Props to @joemcgill for reviewing.

    #agenda, #dev-chat

    Birgit Pauli-Haack 6:42 pm on March 19, 2024  

    Hallway Hangout: Using Site editor in production for client sites

    The topic is on how do agencies and freelancers adjust their workflow and tooling to provide a consistent experience for their clients. The difference between classic themes and 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. themes are considerable. For instance, block themes have settings information stored in various places (database and theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.), and templates and patterns are handled differently. How does it all change workflows regarding version controlversion control A version control system keeps track of the source code and revisions to the source code. WordPress uses Subversion (SVN) for version control, with Git mirrors for most repositories. and deployment. Is there a common method that could be identified and help other agencies and freelancers in their work with block themes?

    In this informal discussion could touch on

    • Common issues agencies encounter
    • How people use the Create Block Theme 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,
    • How to manage theme.json,
    • Tools and automation helpers.
    • and a lot more

    Everyone is welcome at this Hallway Hangout, but it covers topics that are geared towards developers in agencies and freelancers working with client projects.

    Join us on Wednesday, March 27, 2024, at 16:00 UTC. The Zoom link will be shared on the day in the #outreach channel.

    Props to @greenshady and @belbo for review.

    Emily Clarke 5:01 pm on March 19, 2024
    Tags: , , ,   

    Performance Chat Summary: 19 March 2024

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

    Announcements

    • Welcome to our new members of #core-performance
    • WordPress 6.5 Release Candidaterelease 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). 3 is today (Mar 19)
    • Reminder on timezone difference for the next week, this chat will remain at 16:00 UTC and then shift to 15:00 UTC from April 2, 2024

    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
      • Future release
    • 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)
    • Active priority projects
      • INP research opportunities
      • Improve template loading
      • Plugin checker

    WordPress Performance Trac Tickets

    Performance Lab Plugin (and other Performance Plugins)

    Active Priority Projects

    Plugin Checker

    • No updates this week, will be removed from agenda moving forwards unless there are proactive updates on release 1.1

    Improve template loading

    • @thekt12 I should be able to raise a PR for review today, for #59600 including template part caching

    INP research opportunities

    • @adamsilverstein I have continued working on INP research in a colab nostly by querying httparchive data. Recently I added a few new queries that gather:
      • Plugins on WordPress sites with not good INP (based on Wapalyzer detection)
      • Long task scripts on WordPress sites with not good INP (using the long task audit)
      • Long task scripts on WordPress sites overall
    • I then focused in on scripts by path and ran some group queries that only look at the path. Removing the host part ensures we catch common scripts that run across many WordPress sites. Finally, I am grouping by host to see if any 3p stand out at a top level. I’m collecting all the resulting data in a sheet and will soon be ready to summarize the findings in a doc and share everything!

    Open Floor

    Our next chat will be held on Tuesday, March 26, 2024 at 16:00 UTC in the #core-performance channel in Slack.

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

    Emily Clarke 5:31 pm on March 18, 2024
    Tags: , , ,   

    Performance Chat Agenda: 19 March 2024

    Here is the agenda for this week’s performance team meeting scheduled for Mar 19, 2024 at 16:00 UTC.

    • Announcements
      • Welcome to our new members of #core-performance
      • WordPress 6.5 Release Candidaterelease 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). 3 is today (Mar 19)
      • Reminder on timezone difference for the next week, this chat will remain at 16:00 UTC and then shift to 15:00 UTC from April 2, 2024
    • 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
        • Future release
      • 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)
      • Active priority projects
        • INP research opportunities
        • Improve template loading
        • Plugin checker
    • Open floor

    If you have any topics you’d like to add to this agenda, please add them in the comments below.

    This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

    #agenda, #meeting, #performance, #performance-chat