Adam Silverstein 2:35 pm on February 2, 2023
Tags: , ,   

Automated performance monitoring in WordPress core

Gathering performance metrics automatically is a way to track performance over time and ensure that WordPress continues to improve.  Automated performance tooling will also help the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team identify issues and resolve them with less effort.

Why add automated performance testing?

Adding automated performance testing will help us monitor performance changes in WordPress core continuously. It gives us a track record to capture how core performance is being enhanced over time, and it allows us to catch regressions early and accurately identify underlying causes. Similar to our unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. suite, automated performance testing would help protect core from introducing large performance regressions by catching problems immediately and tracking performance over time. Automating testing also means saving contributor effort by replacing a time consuming manual process.

The core performance team is focused on improving core performance. Examples of this work include introducing changes that reduce the number of database queries or improve caching. Each new performance team feature must show measurable gains, and each new WordPress release is performance tested by the team. In the 6.1 release cycle, this led to the discovery of some significant performance regressions, e.g. in this Gutenberg issue or this Trac ticket. Automated testing would catch this type of regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. as soon as it was introduced, making it much easier to resolve.

It is worth noting that 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/ has already done extensive work on performance, tracking metrics with each commit and publicizing details with each release.  

What automated performance testing would do in core

Similar to Gutenberg, WordPress core would gather a set of automated performance metrics along with the existing test runs (e.g. unit tests, coding standards) we already have for each new commit. These metrics can be used to identify the exact point a performance regression is introduced into core. At milestones like 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., the metrics can be compared against the previous release to gauge progress.

Goals for the initial version

The scope of the  initial version of automated performance testing is intentionally kept limited so we can deliver more quickly, then we can iterate. 

The initial version will include the following features:

  • For each core commit a 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/ action will run a set of automated performance tests, collecting key data points about how WordPress is performing (such as total load time and total query time) on 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. and classic themes. 
  • The system will collect server timing metrics using the standard WordPress environment and current recommended version of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher.  

Future Enhancements

Several areas of work are considered out of scope for the initial implementation, primarily to keep the focus limited for the initial release — not because they aren’t good ideas! Once we build a solid foundation for tests and are confident in the metrics we are collecting, we can consider additional improvements.

  • Collecting additional metrics: initially we will focus on key server timing metrics
  • Collecting metrics for other contexts: initial metrics will only measure the home page of the latest core block and classic themes with their default demo content.
  • 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/. or ticketticket Created for both bug reports and feature development on the bug tracker. reporting: initial work will focus only on collecting and recording metrics at each commit. 

FAQ

Will the data be stable enough to be useful?

Performance results can vary in a CI environment, making regressions harder to detect. To mitigate this, the system will run several iterations and use the median value.

What metrics will be collected exactly?

Initially we will only collect a few key metrics to keep the dashboard simple, focused on the total load time. Once we have established the new tool, we can consider including additional metrics, or adding hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. to make the test runs extensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software..

What about testing older PHP versions?

To reduce the time/cost associated with running these tests, they will be limited to the current recommended version of PHP. Unlike unit tests, performance tests are unlikely to produce significantly different deltas for different PHP versions: regressions are likely to be across PHP versions.

Why not test wp-adminadmin (and super admin) or more routes?

In order to keep the time and cost of running these tests low, and the dashboard simplified, initial testing is intentionally being kept somewhat minimal. In the future it would be good to consider adding other common routes such as the wp-admin dashboard and single post page.

Thanks to @tweetythierry @flixos90 @joemcgill @mukesh27 for reviewing this post and to @youknowriad for the inspiration (and foundation) of the Gutenberg performance metrics.

#core-performance, #performance, #testing

Abha Thakor 12:35 am on February 2, 2023
Tags: , , , ,   

Dev Chat summary, February 1, 2023

Start of the weekly WordPress developers meeting in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel of the Make WordPress 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/..

Agenda followed this week.

Summary from Dev Chat, January 25, 2023

@ironprogrammer: It’s been a busy week preparing for 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. 1, and many thanks to everyone who has contributed their valuable time towards the project.

Highlighted Posts

  1. Proposal: Old Tickets Trac Triage Sessions – next session will be on February 9, 2023 and all are welcome to come and help. If you can host a session, reply on the post.
    Looking for any volunteers if they’d like to run another session, though you will be forgiven if your focus is on 6.2.
  2. A Week in Core – January 30, 2022, bringing us the following stats:
    • 49 commits
    • 59 contributors
    • 62 tickets created
    • 6 tickets reopened
    • 62 tickets closed
    • 5 new contributors 
  3. Help Learn.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/ provide suitable materials for users learning and keeping pace with the software
  • Help share where you find materials to advance your WordPress knowledge and how you like materials to be presented. This will greatly assist Learn WordPress to provide more suitable content and presented in ways that would support users’ needs. Please fill in and share the Individual Learner Survey. It is expected to take 5-7 minutes of your time. https://learn.wordpress.org/individual-learner-survey/

Releases

Next major: 6.2 Release

6.2 Development Cycle – this has information on the schedule, 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. scrubs, and more.

Reminder: Beta 1 is planned for February 7, 2023. No time as yet for start of Beta 1 release process, updates will be in the #6-2-release-leads channel on Slack. 

The bug scrub schedule if you can pitch in.

Beta 1 Release post – link will be shared after dev chat for comments until 23:59 UTC February 2, 2023.

Walkthrough – provisional date February 21, 2023. More details to come.

Maintainer Updates/Blockers/Tickets Help

Time for any Component Maintainers to highlight tickets that need help to land in 6.2.

@kraftbj: Emoji: Nothing for 6.2. While Emoji 15.0 was released last year, Twemoji, the library we use, has not been updated. Since there is still some unknown in the air, will be surveying other options. No decision or anything at this time or the near term. Looking for a plan/update for WP 6.3. Ticketticket Created for both bug reports and feature development on the bug tracker. #57600. 

@sergeybiryukov: I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: switch_to_user_locale() function was introduced to make it easier to switch to a specific user’s localeLocale A locale is a combination of language and regional dialect. Usually locales correspond to countries, as is the case with Portuguese (Portugal) and Portuguese (Brazil). Other examples of locales include Canadian English and U.S. English.. Thanks @swissspidy and @costdev! View ticket #57123 for more details.

Build/Test Tools, Date/Time, General, Permalinks: No major news this week 

@webcommsat: About/ Help & Quick/Edit scrub / review on Monday – focusing on clearing some of the tickets, some testing of patches aimed at 6.2. May call out for further testing later today as tests still running. Additional component maintainer to be added after a number of years of assisting on tickets.

@afragen: Upgrade/Install. Getting closer to landing #57375 and #57557 for 6.2. This should provide much needed stability and performance improvements to 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 updating. It should also pave the way for other features. Shared thanks to @azaozz @peterwilsoncc and @costdev for getting us almost over the finish line in the past two to three weeks, and to everyone else who has played a significant part.

@luminuu: request for views on the ticket #55985 to move it forward before the feature freeze for 6.2. The specific PR to test this would be GitHub #2920.This relates to removing Google fonts from Twenty Twelve.

Open Floor

Community Summit

@webcommsat: Community Summit will take place August 22-23, 2023 – the deadline has been extended for comments/ suggestions from Make teams for this year’s event. I will be sharing a post with the key information so far, and to provide a space for 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. to add comments which the team can submit in the next few weeks.

If you were involved in the previous Community Summit, any insight on highlighting topics from core or anything that was raised that could be re-highlighted, let Abha know or comment on the P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. post which is coming.

WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

The event will take place on February 17, 2023, 02.00 UTC.

Update from @desrosj: Working on getting this together. Expecting a performance table and editor table, in addition to general Core tables. Working on a write up of “how to be prepared for Contributor Day” with the hope of getting it sent to attendees prior to the event to limit the amount of debugging local environment problems that has to be done on the event day. Hoping it will make the day more positive and productive overall! If it is not possible to go on the site, it may be communicated via an an email to attendees instead.

Update from @ironprogrammer: started drafting similar guidelines for Test contributors. Numbers expected useful, and for volunteers to know.

Update from @webcommsat:
– anyone working on core docs for this contributor event, can we also use some of this to update the handbook to help others prepare for these events in the future. Cross-link from core handbook to Test guide.
– appears that there will be a virtual attendees too at this event. They will join teams’ slack channels after the team introductions. Some have been joining already! If you can assist virtually with signposting new contributors on Slack during the event, please let abhanonstopnewsuk know on Slack, with what times you could provide support (in UTC).
– to follow up with organizers on virtual offering, numbers signed up for both in-person and virtual, and if known, how many have expressed preference to join the Core Team.

Props to: @ironprogrammer for facilitating the meeting and summary review,
and to @webcommsat for preparing the agenda and writing the notes.

#6-2, #dev-chat, #meeting, #summary, #week-in-core

annezazu 11:12 pm on February 1, 2023
Tags: ,   

Core Editor Improvement: Strengthening style options

These “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement…” posts (labeled with the #core-editor-improvement tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)) are a series dedicated to highlighting various new features, improvements, and more from Core Editor related projects. 

There are a variety of tools and methods for styling your site, from global edits via the  Styles interface to more nuanced changes for individual blocks. Ahead of WordPress 6.2, there are new features that make it easier to create consistent designs, understand at a glance what impact changes will have, and customize more aspects of your site to your liking. There’s something for everyone, whether you’re creating your next 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. theme, a designer seeking a pixel-perfect layout, or someone looking to reuse a design. Taken together, these changes create a clearer design process that is intuitive and efficient for modification and reuse. 

Interfaces for creating your style

While expanding the tools and options for what you can style are incredibly important, so are the ways in which design changes are represented. The following interface updates help ensure you can more clearly see the impact of the changes you want to make:

  • Design blocks globally with the new Style Book that allows you to see all blocks on your site as you style them (44420). 
  • Rely on an inline preview of blocks when working with Styles to better understand the impact of changes (42919). 
  • See a broader view of your template when selecting a style variation (44987).

Tools to customize further

While some are content with relying on what a block theme or Core provides, others want more ways to get a design or layout just right. With the last few releases of 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/, the following options have been added that allow for that exact kind of deeper customization folks are used to:

  • Add Custom CSSCSS Cascading Style Sheets. for your entire site directly from the Styles interface (30142). 
  • Add Custom CSS on a per block basis directly from the Styles interface (44412). 
  • Edit block style variations, like with the Button or Image blocks, from the Styles interface (46343)

Options to create consistent designs

With a growing number of design tools in each WordPress release, designs can become both more complex and nuanced. To help streamline the design process and make it easier to reuse your work, take a look at these new options:

  • Take local changes from a single block and apply them globally across your entire site, with a new control within the Advanced block settings (44361, 46965). 
  • Copy and paste block styles to create consistent designs in a few clicks (44418). 

Thank you to @dansoschin and @cbringmann reviewing this post. 

#core-editor-improvement, #gutenberg

Emily Clarke 5:03 pm on January 31, 2023
Tags: , , , , , , ,   

Performance Chat Summary: 31 January 2023

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

Announcements

  • Performance team roadmap for 2023 https://github.com/WordPress/performance/issues/631 If you’re actively contributing to the WordPress Performance Team or plan to do so this year, please share your priorities for 2023 as a comment on this issue!
    • @flixos90 Anyone that is more or less regularly contributing to the team is asked to think about and share their priorities for this year, if possible
    • @spacedmonkey There is also SQLite database and object cache that are in play
      • @flixos90 I think SQLite is clearly a focus. What is on the issue right now is not at all a complete roadmap. The idea is that anyone can post comments with what they would like to prioritize
    • @olliejones It’s my impression that almost nothing, except @flixos90 contributions, are on the priority list yet. So, it’s up to the rest of us.
      • @flixos90 Exactly, I just posted 2 things that we already have proposal posts for, as a starting point. So yes, it’s explicitly a call for anyone involved in the team to contribute to this roadmap
    • @spacedmonkey One thing I have not discussed publicly, but want to look into lazy loading meta data in core. We have a problem that more and more WP_Queries are being run per page and lots of post meta is being loaded when not needed https://core.trac.wordpress.org/ticket/57496
  • The 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/ team recently added TTFB measurement to their repo, which is being collected in the code health dashboard here: https://codehealth.vercel.app/project/1. It’s making visible the performance regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in 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. theme rendering when compared with classic themes for a simple “hello world” page. As a team, we would like to make sure we’re properly prioritizing the tickets we have for 6.2 that would positively impact this metric—particularly anything that we need to land before the 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. 1 milestone next week.
    • @joemcgill I think much of the work for 6.2 that was focused on improving server response times for block themes has already been merged, but I’m mindful of the beta milestone coming next week and want to help prioritize helping land anything that I can that is still in the air.
      • @spacedmonkey me and @flixos90 have worked a lot on block theme performance. Any questions on what I am working on, please feel free to pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me
      • @joemcgill Main thing is whether there are any enhancements that still need to land that you’re waiting on review for?
    • @clarkeemily we also have the Bug Scrub tomorrow at 16:00 UTC time where we can talk through other 6.2 performance items
    • @mukesh27 Is anyone on the Gutenberg team checking those regressions, or do we have to?
      • @joemcgill Good question. I think they are, but there’s no reason we shouldn’t take a look every so often. Really, it would be nice to do something similar for CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
      • @mukesh27 Are those changes incorporated into the core of WordPress?
      • @johnbillion I’d love to do something similar for core, the main problem is how to avoid variance so the reporting over time is accurate
      • @flixos90 We have talked about it before in that recent hallway hangout earlier in January. In fact @adamsilversteinis working on a Make post that should go out this week
      • @spacedmonkey I would also have some way of query count per page load.
      • @joemcgill I think long term variance is a concern, but maybe not a blockerblocker A bug which is so severe that it blocks a release. as long as the short term trends are instructive/useful.
  • Plan to have quick-fire focus area updates (15m) so we can focus the remainder of todays chat on Next steps for Unbundling the 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 (proposal)

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

Feedback requested

Measurement

N/A

GitHub project

  • @joegrainger Still making good progress on the Plugin Checker, starting to approach the remaining issues on the infrastructure so will soon be in a position to run some of the initial checks and do some testing. Feel free to track progress on the GitHub repo and leave any thoughts/ideas on issues. The repo will be eventually moved to the WordPress organisation when ready.

Feedback requested

JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets.

@aristath @sergiomdgomes

GitHub project

  • No updates

Feedback requested

Database

@olliejones

GitHub project

Feedback requested

Infrastructure

@flixos90

GitHub project

  • @flixos90 nothing to update for Infrastructure

Feedback requested

Open Floor

  • Unbundling Performance Lab plugin
  • TL:DR; the team are in agreement to proceed with working towards splitting out standalone plugins and keeping the Performance Lab plugin as it is for now
  • Detailed conversation below:
    • @flixos90 We are still waiting to get feedback from Matt on the 3 alternative options that we have outlined and discussed earlier in January. However, I think it would be unwise to just wait and do nothing until we hear back, for which we don’t have a timeline. Therefore my proposal is to work towards simply splitting out standalone plugins and keeping the Performance Lab plugin as is for now
    • A bit more context on the reasoning behind that proposal: The “for now” here is important, as that would likely be a temporary solution. Doing so is effectively our option 1 that we voted for in https://github.com/WordPress/performance/issues/618#issuecomment-1377598692, but the main reason I’m proposing to already work towards it here is that that option is the least disruptive and the least effort, and even if we eventually go with option 2 or 3, we would need to implement the same changes as part of that
    • It is also the most natural transition, for example @aristath‘s SQLite standalone plugin has already been broken out as a standalone plugin
    • The idea is that with the above we would work in the right direction no matter what the eventual final outcome should be. And in any case we would not be wasting time doing work that would potentially not be needed
    • @joemcgill So, if I’m understanding properly, you’re proposing that the performance lab plugin would still include the modules that have been split out. Correct?
    • @flixos90 Yes, it is effectively like option 1 in https://github.com/WordPress/performance/issues/618#issuecomment-1377598692
    • @joemcgill What other plugins need to be split out that aren’t already?
    • @flixos90 I think that we need to discuss. But first I wanted to get feedback on the general idea I shared above. Is that a reasonable next step, as a temporary measure to work in the right direction?
    • @johnbillion Does that duplicate any work or is there a handy build/deployment step for publishing the separate plugins?
    • @flixos90 We would have a build step that simply replaces module headers with plugin headers and deploys those as individual plugins. All modules already work standalone, so there’s no extra work involved in that regard. The main work would be to implement the build and deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. step.
    • @joemcgill At least the SQLite integration plugin is already moved to a separate repo, so it’s a bit clunky to have some of these modules in a mono-repo and some not. It would be nice to align on a development approach.
    • @flixos90 Absolutely; if we go with this approach, we would likely move the SQLite repo back into the PL repo (just for development, the plugin repos on .org would of course remain separate)
    • @johnbillion +1 on a monorepo otherwise we introduce more metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. problems maintaining separate repos
  • No other thoughts on the above from todays meeting, @flixos90 based on the feedback above I think it’s reasonable to proceed with this option for now, to work in the right direction. What we should discuss then though is our approach on how to break out modules as standalone plugins (which we already started talking about a few weeks back)
    • @joemcgill My initial question is whether all modules should be standalone plugins, or if some of them are better suited to stay as part of central infrastructure or smaller experiments as “core modules” of the performance plugin?
    • @flixos90 Exactly, I would outline these alternative ways to go about it:
      • Every module becomes a plugin?
      • Some modules are grouped together into “focus” plugins?
      • Only some modules get broken out as a plugin?
    • @olliejones Specifically, does it make sense to have a standalone “Enhanced Site Health” plugin containing the various site health modules?
      • @flixos90 Potentially. Though my personal take is that we should avoid grouping modules as then we are still going the slippery slope of not having individual plugins for individual features. FWIW, we used to have plugins like https://github.com/audrasjb/site-health-audit-enqueued-assets, and I think that’s the most appropriate approach, even if those plugins are extremely niche
    • @joemcgill Personally, I would keep things like audits, health checks, and small feature experiments like fetchpriority in the main plugin, and break out larger feature plugins.
      • @flixos90 If we do this, we won’t fully address the request of having individual plugins for individual features. What if someone just wants to test fetchpriority? Yes, it’s much simpler than e.g. WebP, but I’m not sure that justifies going a different route for the two
      • @joemcgill That may have been a bad example, and also the part that I’m least confident about, but seems it would be nice for us to have a place to experiment with smaller changes that we are thinking of proposing as enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. in core and not have to spin each one out to a separate plugin until/unless it matures to the point where it’s warranted.
      • @flixos90 Ah okay, that idea sounds interesting. Certain things could start out as a module in the PL plugin and only become plugins as they mature?
    • @olliejones So, PL contains stuff that’s bound to be included in core, AND stuff that’s bound for standalone plugins? Is that right? Or is the criterion for putting a module into PL still that it is bound for core?
      • @joemcgill Right, or if they’re a large enough feature that it makes sense being its own thing. I would say the SQLite persistent cache fits that qualification for me
      • @flixos90 All of that would be things to be included in core. Whether it’s a module in the PL plugin or a standalone plugin is just different ways to “test-drive”. So if we did that, we would still have a mapping that a module can be mapped directly to a standalone plugin, but we would decide for each module whether/when to do that on a case by case basis?
      • @olliejones Is that too limiting? Is Matt thinking along the lines of Drupal’s Core Modules? Is that the direction his “canonical plugins” want to go? Should this team stay away from doing stuff UNLESS it’s bound for core? That’s what I mean. There’s plenty of perf work that only applies to some installs, not all.  Like the persistent object caches. Maybe like webp.
        • @flixos90 we can totally work on things that are not for core; for example the plugin checker project we’re working on. It’s just that the scope of the Performance Lab plugin has been for features targeted for WordPress core. Of course it can always happen that a feature is never deemed eligible or ready. But features in the PL plugin should have the intent to land in core eventually
      • Conclusions: @flixos90 I think we are converging on the approach of “decide on a case by case basis for each module whether/when it becomes a standalone plugin”, but it’s been only a short conversation with few voices heard, so maybe we can defer a hard decision until next week; I’ll summarize in https://github.com/WordPress/performance/issues/618 and we can keep discussing there
      • @olliejones add to roadmap https://github.com/WordPress/performance/issues/631 for future discussion

Our next chat will be held on Tuesday, February 7, 2023 at 16:00 UTC in the #core-performance channel in Slack.

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

#core-performance, #meta

Abha Thakor 12:58 pm on January 31, 2023
Tags: , ,   

Dev Chat Agenda: February 1, 2023

The WordPress developers chat meets in the core channel of the Make WordPress Slack on Wednesday February 1, 2023 at 20:00 UTC .

1. Dev Chat introduction

Summary from last week: January 25, 2023 – @webcommsat

2. Announcements

Please add any relevant WordPress announcements in the comments.

3. Posts to note

Reminder of Proposal: Old Tickets Trac Triage Sessions – next session will be on February 9, 2023 and all are welcome to come and help. If you can host a session, reply on the post.

A Week in Core – January 30, 2023 – @audrasjb

Please add any other suggested posts in the comments to be highlighted in the meeting.

4. Releases

Next major: 6.2

Development Cycle – this has information on the schedule, 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. scrubs, and more.
Reminder: 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. 1 is planned for February 7, 2023.

Update from release squad and discussions to progress the release. 

Squad members can also add comments to this post if they are unable to attend the dev chat live.

5. Blockers/ help

Component Maintainers or anyone wishing to highlight a potential blockerblocker A bug which is so severe that it blocks a release. or issue on a ticketticket Created for both bug reports and feature development on the bug tracker. can comment on this post if unable to attend the meeting live. Priority in the meeting will be given to tickets aimed at 6.2.

6. Open Floor

  • Reminder: if you are planning items for the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tables at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. in February 2023, please let abhanonstopnewsuk (on 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/.) know to help update the handbook for future events.

Please add comments on this post with items you would like to suggest for Open Floor.

#agenda, #dev-chat, #meeting

Emily Clarke 10:58 am on January 31, 2023
Tags: , , ,   

Performance Chat Agenda: 31 January 2023

Here is the agenda for this week’s performance team meeting scheduled for January 31, 2023 at 16:00 UTC.

  • Announcements
    • Performance team roadmap for 2023 https://github.com/WordPress/performance/issues/631 If you’re actively contributing to the WordPress Performance Team or plan to do so this year, please share your priorities for 2023 as a comment on this issue!
    • The 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/ team recently added TTFB measurement to their repo, which is being collected in the code health dashboard here: https://codehealth.vercel.app/project/1. It’s making visible the performance regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in 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. theme rendering when compared with classic themes for a simple “hello world” page. As a team, we would like to make sure we’re properly prioritizing the tickets we have for 6.2 that would positively impact this metric—particularly anything that we need to land before the 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. 1 milestone next week.
    • Plan to have quick-fire focus area updates (15m) so we can focus the remainder of todays chat on Next steps for Unbundling the 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
  • Focus area updates (15m max today)
  • Infrastructure
  • Open floor
    • Next steps for Unbundling the Performance Lab Plugin proposal

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

Jb Audras 11:42 pm on January 30, 2023
Tags: , , meta6545,   

A Week in Core – January 30, 2022

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between January 23 and January 30, 2022.

  • 49 commits
  • 59 contributors
  • 62 tickets created
  • 6 tickets reopened
  • 62 tickets closed

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Bootstrap/Load

  • Avoid initializing WP_Recovery_Mode when fatal error handler is disabled – #56848

Build/Test Tools

  • Back up and restore the $wp_filters global when running tests – #57236
  • Revert [55137] – #57555
  • Update PostCSS to version 8 – #57554, #57555
  • Update caniuse-lite to the latest version – #57555
  • Update third-party 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/ Actions – #57572
  • Resolve some line endings issues in blocks/renderCommentTemplate.php on Windows machines – #56793
  • Use wp_recursive_ksort() in WP_Theme_JSON_Resolver tests – #56793

Bundled Themes

  • Twenty Twenty-One: Refine primary-navigation.js behavior for anchor links – #53331
  • Twenty Twenty-Two: Remove color reference from pattern names – #56720

Code Modernization

  • Allow some parameters with reserved keywords in wp-includes/class-wp-text-diff-renderer-*.php – #56788
  • Fix a JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. error in wpdialog – #56830
  • Rename parameters that use reserved keywords in phpunit/tests/functions/wpRefererField.php – #56788
  • Rename parameters that use reserved keywords in phpunit/tests/kses.php – #56788
  • Rename parameters that use reserved keywords in phpunit/tests/post.php – #56788
  • Rename parameters that use reserved keywords in phpunit/tests/rest-api.php – #56788
  • Rename parameters that use reserved keywords in phpunit/tests/shortcode.php – #56788
  • Rename parameters that use reserved keywords in phpunit/tests/widgets/wpWidgetMedia.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/blocks.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/class-wp-theme-json-resolver.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/class-wp-theme-json.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/formatting.php – #56788
  • Rename parameters that use reserved keywords in wp-includes/functions.php – #56788

Coding Standards

  • Allow some parameters with reserved keywords in wp-includes/compat.php – #56788, #56791
  • Bring some consistency to the order of attributes in password fields – #56791

Database

  • Add %i placeholder support to $wpdb->prepare to escape table and column names, take 2 – #52506
  • Replace str_ends_with() usage in wpdb::prepare() – #52506
  • Replace substr_compare() usage with substr() in wpdb::prepare() – #52506

Docs

  • Add missing @since tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) for WP_Theme_JSON_Resolver::remove_json_comments() – #56792
  • Update $types param for wp_get_global_stylesheet() – #57563, #56792
  • Various improvements in ms-blogs.php function descriptions, as per docblocks standards – #56792

Editor

  • Add is 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. theme setting to get_block_editor_settings() – #57549
  • Adds ‘settings.typography.fluid.minFontSize’ support to wp_get_typography_font_size_value() – #57529
  • Adds pagination and ordering support to WP_REST_Pattern_Directory_Controller – #57501
  • Fix undefined variable following [54805] – #56974, #57067
  • Migrate old to the new pattern categories – #57532
  • Remove WP_DEBUG defined check in wp_tinycolor_hue_to_rgb() – #57527
  • Use a non-persistent object cache in wp_get_global_settings() – #57502
  • Use a non-persistent object cache instead of transient in wp_get_global_stylesheet() – #56910
  • Use in/decrementors in wp_tinycolor_hue_to_rgb() – #57527

I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.

Media

  • Add download link to media modal and attachment details – #41474
  • Deprecate unused method WP_Media_List_Table::column_desc() – #39710

Menus

  • Add missing escaping function in Adminadmin (and super admin) Menu walker – #57541

RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.

  • Only create autosave when content changed – #49532

Themes

  • Add “Style Variations” to the list of WordPress theme features – #56869, #meta6545
  • Add static cache variable to wp_theme_has_theme_json() – #56975
  • Avoid unnecessary database queries from get_default_block_editor_settings() in WP_Theme_JSON_Resolver::get_theme_data() – #57547
  • Support additional link related pseudo classes in theme.json – #57053

Props

Thanks to the 59 people who contributed to WordPress Core on Trac last week: @jrf (14), @poena (14), @sergeybiryukov (14), @aristath (14), @justinahinon (11), @costdev (11), @mukesh27 (9), @oandregal (5), @spacedmonkey (5), @mamaduka (4), @ironprogrammer (4), @hellofromTonya (4), @flixos90 (4), @audrasjb (4), @azaozz (3), @ntsekouras (3), @joen (2), @Otto42 (2), @hellofromtonya (2), @mcsf (2), @ryelle (2), @andreaboe (1), @TobiasBg (1), @shubham1gupta (1), @peterwilsoncc (1), @andrewserong (1), @ramonopoly (1), @cu121 (1), @arrasel403 (1), @paaljoachim (1), @robinwpdeveloper (1), @chaion07 (1), @afercia (1), @annezazu (1), @jameskoster (1), @sabernhardt (1), @aniketpatel (1), @dgwyer (1), @dmsnell (1), @aduth (1), @sanjucta (1), @iandunn (1), @JeffMatson (1), @antpb (1), @countrymusicchicago (1), @joedolson (1), @amin7 (1), @inwerpsel (1), @craigfrancis (1), @antonvlasenko (1), @xknown (1), @ellatrix (1), @alexstine (1), @glendaviesnz (1), @scruffian (1), @jorgefilipecosta (1), @ocean90 (1), @czapla (1), and @whaze (1).

Congrats and welcome to our 5 new contributors of the week: @andreaboe, @shubham1gupta, @sanjucta, @countrymusicchicago, @inwerpsel ♥️

Core committers: @sergeybiryukov (20), @hellofromtonya (8), @audrasjb (7), @flixos90 (5), @desrosj (4), @davidbaumwald (2), @swissspidy (1), @joedolson (1), and @adamsilverstein (1).

#6-2, #core, #meta6545, #week-in-core

Fabian Kägy 10:36 am on January 30, 2023
Tags: , , ,   

Editor Chat Agenda: February 1st 2023

Facilitator and notetaker: @fabiankaegy

This is the agenda for the weekly editor chat scheduled for Wednesday, February 1st 2023, 03:00 PM GMT+1. This meeting is held in the #core-editor channel in the Making WordPress 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/..

The 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). of 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/ 15.1 was delayed one week and will happen on February 1st to align better with the upcoming WordPress 6.2 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. to be released on 7th of February. A project board for WordPress 6.2 Editor tasks is available.

Key project updates:

Task Coordination.

Open Floor – extended edition.

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-agenda, #meeting

David Smith 10:22 am on January 30, 2023
Tags: , , ,   

Core Editor chat summary: 25th January 2023

This post summarises the weekly editor chat meeting (agenda here) held on 2023-01-25 14:00 UTC in Slack. Moderated by @get_dave.

Status Updates

  • Version 15.0.0 of the 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/ 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 is the latest major version and version 15.0.1 was also released to resolve some iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. issues.
  • Please note than the 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). of Gutenberg 15.1.0 will be delayed to align better with the upcoming WordPress 6.2 beta (to be released on 7th of February).
  • A project board for WordPress 6.2 Editor tasks is available.

Updates based on updated scope for site editing projects

Task Coordination

The following items were shared by folks to update us on what work is in progress or where help is needed:

@mamaduka:

  • primarily working on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher backports for WP coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • We’ve got a nice tracking issue if anyone is interested. Please check the issue description if your username is mentioned, and let us know if you can help with backports. Tracking issue: 

@get_dave:

@paaljoachim – gave a lot of feedback to the current call for FSE testing. 

@ndiego – working on Editor Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. for 6.2. If you see an issue/PR that you feel needs attention for the 6.2 release. Please feel free to add it to the 6.2 Project Board. We will triage from there.

Open Floor

The full Open Floor discussion is available on 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/..

A new contributor joins us – welcome Alex

Ongoing value of these chats/meetings

  • @paaljoachim asked if/how we can improve the value of the Core Editor meetings.
  • @get_dave suggested including more of a triage session and wondered whether that would interfere with @ndiego‘s efforts.
  • @poena highlighted meeting time of day as a key blockerblocker A bug which is so severe that it blocks a release..
  • @ndiego noted that the triage sessions are also suffering from low attendance. He agreed that we should consider ways to improve the value of the chat.
  • @danielbachhuber suggested a better form of async meeting/scrubbing.
  • @danielbachhuber also highlighted the problem that it’s hard to get product decisions and feedback if you are not:
    • on a team working full time on Gutenberg.
    • working on something directly related to the roadmap

Thanks to everyone who attended the chat.

#core-editor, #core-editor-summary, #meeting-notes, #summary

Abha Thakor 8:12 pm on January 27, 2023
Tags: ,   

Dev Chat summary, January 25, 2023

Start of the weekly WordPress developers chat in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel of the Make WordPress 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/..

The Agenda followed.

Announcements

  • none

Highlighted posts

a) A Week in Core – January 23, 2023

b) Components
@francina recommend reading about every component to stay up to date with the development of the current WP release (6.2).

c) 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/
– What’s New in Gutenberg 15.0

– One more Guterberg release is planned to go that will be merged in WordPress 6.2. The 15.1 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). (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).) 1 is planned for February 1, 2023. 

 d) Old tickets
As part of the 20 year celebration of WordPress, there is a proposal for a triage sessions dedicated to old tickets. 
A first/kickoff session will be on January 26, 2023 at 16:00 UTC.
– The sessions will start with a selection of very old tickets, but if people have suggestions for tickets that are over 10 years old, it would be appreciated.
Actions:
– requests or comments can be added to the post
– attend one of the sessions

– The primary goal is not to resolve tickets directly, but to add the right workflow keywords, to close tickets that are no longer relevant, and if possible to find an interested person to take ownership on each ticketticket Created for both bug reports and feature development on the bug tracker., to refresh the patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing., etc.

A discussion followed on opening the 6.3 milestone, in order to be able to move tickets that we know cannot be milestoned to WP 6.2, instead of moving them to Future Release. Others recommended against punting everything to 6.3 as that shifts burden to the 6.3 team to assess what’s needed on as they’re starting their release cycle. Suggested instead, making an informed decision of “is it somewhat certain this will be ready for 6.3”, and if not then move to Future Release.

Releases

Next major: 6.2

Development cycle page 

WordPress 6.2 Planning Roundup including the schedule and the squad 

Bug Scrub Schedule

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. 1 of WordPress 6.2 is scheduled for February 7, 2023

Update from @francina: There won’t be a go/no-go demo or a walkthrough this time. @marybaum said walkthrough will be after Beta 1, date not confirmed as yet.

You can read updates from all release leads in the #6-2-release-leads channel, starting at this timestamp.

@francina: discussion on some confusion around the Feature Freeze milestone which was never formally documented and lasted only for a couple of release. Recap from @jeffpaul: Beta 1 = end of enhancements/features; some things that are labeled that way in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. may get converted to bugs/tasks because what remains are small things post-commit of the large actual feature/enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. code.

Bug fixes can still be merged in Beta and so do task (blessed).

Component Maintainers / tickets help

Updates from components maintainers section of the agenda from @francina:
– Discussion in the Release Leads channel 
– This section of the chat usually sees the maintainers attending giving status updates, which are covered in “Week in Core”. The agenda also lists help for tickets.
– Move to “request for help/blockers”? In the past, there were discussions around having a weekly post on the blogblog (versus network, site) for Maintainers. The discussion in dev chat can be read at this Slack message. The discussion included the value of a user group for maintainers, the notification link to maintainers group on Slack needs updating via a MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. ticket, annual review / check-in with maintainers. Other comments from those not able to be at dev chat are welcomed.

@sergeybiryukov on General components: Work has continued on renaming parameters that use reserved PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher keywords. Ticket #56788 for more details.

“For transparency, these commits are a result of weekly coding sessions with the WordPress Core team at Yoast, where we focused on improving PHP 8.x compatibility. The initial PRs took me a while to review and finalize, as I wanted to strike a balance between embracing the chaos that is WordPress codebase and making these naming changes at least somewhat consistent. This did not seem like a huge task initially, but still spanned over a few releases.

“For our next focus, we’re thinking of resolving some WPCSWPCS The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the WordPress Coding Standards. May also be an acronym referring to the Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. issues in core (remaining non-strict comparisons, etc.) and adding missing @covers annotations in unit tests (there is a huge existing PR that has been open for a long time and needs a refresh and review).”
Action: If you can think of any other code maintenance tasks that would improve developer experience, please feel free to suggest.
A few areas where contributors can help with:
– the missing @covers annotations in unit tests is a big issue. Refreshing the PR on #56782 would be a good first step 

@audrasjb‘s request relating to 6.2: for someone working on Gravatars to ask them a few question about the background of the current implementation in WordPress. The ticket itself is already handled (#57493), more info is requested as the GravatarGravatar Is an acronym for Globally Recognized Avatar. It is the avatar system managed by WordPress.com, and used within the WordPress software. https://gravatar.com/. documentation doesn’t include any history. More details from this Slack timestamp.

@webcommsat: For About/ Help and Quick/Bulk components, we will be having a focus review on Monday January 30, 2023 at 15:00 UTC next week (earlier time) as we have some APAC contributors coming along.

@afragen: Upgrade/Install component:
There’s a great new feature for Upgrade/Install that is only waiting on some testing in VirtualBox 7. Some VB7 testing is currently being done by @costdev. This new feature should greatly speed up 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 updates for all users. The PR has passing unit tests. Requested: some extra reviews on PR3798 and any concerns added to the ticket
 for discussion. Requested if it is not able to be committed before beta1, is it possible to have it task (blessed) ?

@craigfrancis: request on what can be done regarding the “early” ticket #52506. It has had some checks, and request for as much testing as possible. Suggested committing so there would be more testing time in beta and RC, or alternatively wait about 18 weeks (until 6.3 early), where Craig believes it will be in the same position again. @jeffpaul suggested co-ordinating with @davidb as owner of the ticket on likelihood of committing in 6.2. @sergeybiryukov offered help for review if there is a consensus from release leads that it can be committed this week. Core tech lead invited – @audrasjb confirmed did not see any blockerblocker A bug which is so severe that it blocks a release.. If the owner and/or one other committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. are happy with the current implementation, suggested to ship it now.
[Note there is currently an ongoing discussion on definition of early]

Open Floor

i) New Contributor meetings
@jeffpaul raised a question on New Contributor meetings, which takes place two weeks before dev chat. He suggested a similar process for contributors helping run this meeting as the team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. annual process. He highlighted the existing core contributors listed as help run this meeting “have been in that role for quite some time and it may be worth seeing who else might be able to help run this meeting so some of these folks can rotate out. So I’d suggest we at least share this during dev chat and see if folks are interested in helping out (and also if any of the existing folks would like to politely rotate out as well)? I don’t think we need a formal nomination/voting process here, so much as looking for folks to commit to help with this meeting (say over the course of 3/6/9/12 months).”

@desrosj and @sergeybiryukov advised since the start of the New Contributor meetings there has always been an open door to anyone that wanted to help run the meetings. They have once or twice had someone new express interest in helping run the meetings. Confirmed more people to help are welcome. No formal process was thought to be needed.

Call: These meetings can be held at other times too – contributors who regularly show up can offer to help run meetings. Eg aimed at contributors in APAC/other non-Americas-centric timezones wanting to host as a one-off or on a regular basis.

Actions: @desrosj: A new page in the handbook was suggested on facilitating new contributor meetings.

There have been previous discussions on an earlier time which would fit both APAC and some European timezones. @marybaum @robinwpdeveloper and @webcommsat have offered to assist with facilitation and regularly attend the existing one. Discussions are ongoing on this, and a follow-up conversation with some of the existing contributors is planned.

For more on this from the meeting, Slack timestamp.

@costdev: request to become component maintainer for the Filesystem component. The plan is to first address docs inconsistencies/typos and such, then move onto writing tests. Then with this solid basis continue working on the open tickets.

Props to @webcommsat for the agenda and posts highlight preparation, to @francina for facilitating the meeting,
and to @webcommsat for the summary, and @audrasjb and @marybaum for reviewing.

#dev-chat, #summary