Dev Chat summary: Wednesday, November 30, 2022

Here’s a summary of the weekly WordPress developers’ chat for November 30.

1) Welcome

IF you’re new to dev chat, you can find out more about this weekly meeting in the handbook.

Meeting facilitators: @marybaum and @webcommsat.

Agenda followed; thanks to @marybaum for preparing it.

Start of the 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/..

Summary from the November 23, 2022 dev chat.

2) Announcements

Slack link.

  • WordPress 3.7 – 4.0 have landed their final versions. Props to everyone who volunteered and to @peterwilsoncc for leading.
  • 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/ 14.7 is expected to land a 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). today.
  • Nominations for 2023 Core Team Representatives close this Friday.

3) Blogblog (versus network, site) posts of note

Slack link.

4) Upcoming releases

Slack link.

a) The 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. is 6.2

December is a great time to work on the things you would most like to see land in 6.2.

b) The next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. is 6.1.2.

No updates from the release teams at this time.

5) Components and tickets

Slack link.

a) Components

Build/Test Tools, Date/Time, General, 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., Permalinks: no major news this week – @sergeybiryukov.

Site Health: nothing new to report – @clorith

Quick/ Bulk Edit Component

  • #54378 @webcommsat: This ticketticket Created for both bug reports and feature development on the bug tracker. could be an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. if anyone wanted to work on it. This has been raised in scrubs previously.
  • #55549 This ticket has been closed for now after testing.
  • #56137 Raising this ticket as it has come up a couple of times in meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. groups – request to be able to add excerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. in Quick Edit.

b) Tickets

  • No other tickets were raised.

6) Open Floor

Slack link.

a) WordPress 6.1 issue #45713

@bernhard-reiter: WordPress 6.1 has an issue with .is-layout-flex. The issue is complicated, and some testers are having trouble reproducing it. Full details are in the chat as it happened.

Props to: @marybaum and @webcommsat for running dev chat, @dpotter05 for the summary, and to @webcommsat and @marybaum for review.

#6-1, #6-2, #dev-chat, #summary

Performance Chat Summary: 29 November 2022

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

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

Feedback requested

Measurement

N/A

GitHub project

  • No updates

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

  • @mxbclang: What are the next steps on Revisit indexes for DB performance #132?
    • @olliejones: Current voting winner points to doing something dbms-version-specific to the schema, eventually in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., think we can do this in 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 if we’re willing to accept a mu-plugin drop-in module. Disadvantage here is complexity.
    • @flixos90: This is tricky – we have a voting winner, but also some strong opinions from different sides including a WP lead developer.
    • @mxbclang: Seems like the best next step here would be to close out the vote as planned but hold on next steps pending further discussion in the issue, then regroup on this in a future chat
    • All agreed; vote will close and @mxbclang will add a comment about next steps
  • @olliejones: SQLite Object Cache is coming along nicely; will create a new module proposal issue once it’s closer to complete
  • @olliejones: For future discussion: Do we need some sort of formal set of filters, etc. to support the big competent hosting providers in this back-end area?

Feedback requested

Infrastructure

@flixos90

GitHub project

  • @flixos90: Been working on iterating on the Server-Timing API PR. Still in draft because unit tests need to be added, but ready for review. Would love feedback and opinions on the 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. implementation. The most important recent change is that it is now initialized early through a drop-in, so it can capture measurements that happen before WP plugins are loaded.

Feedback requested

Open floor

  • @olliejones: There’s a sustainability team forming – see #sustainability Slack channel
  • @nickchomey: Been working on implementing a real PWA for a site under development. Plugin options are limited right now but @westonruter‘s plugin is the right approach. Is this something that the performance team can move forward?
    • @flixos90: Not sure what the current state of the plugin is; original idea was for it to be a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins.
    • @nickchomey: Proposing a real coordinated effort be made to improve it to the point that it could be merged into core
    • @flixos90: It could definitely be feature plugin material, but as always it requires resources. If a small group is up for tackling, we would be supportive and help here possible.
    • @westonruter: The plugin is stable and essentially in maintenance mode. Not clear if there is the 80% user benefit to justify core merge just yet. See discussion between @nickchomey and @westonruter in GH issue: https://github.com/GoogleChromeLabs/pwa-wp/issues/884.
    • @flixos90: Key aspect of proposing this for core would be to come with an actual usage of PWA capabilities that immediately benefits core users
    • @westonruter: Benefit that all users could get now is offline browsing on the front-end, but there’s a separate concern of what happens when a large portion of the web is registering service workers
    • @pbearne: Aren’t we going to need something like this for real-time multi-editing in 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/?
    • @olliejones: Maybe the Twenty Twenty Four theme could be made PWA-friendly?

Our next chat will be held on Tuesday, December 6, 2022 at 16:00 UTC in the #core-performance channel in Slack.

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

#meta

Dev Chat summary: Wednesday, November 23, 2022

The weekly WordPress developers chat meeting was held 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/. at 20:00 UTC.

Agenda followed.

Start of the meeting in the core channel of the Make WordPress Slack.

Summary from November 16, 2022 dev chat.

1) Announcements

Slack link.

  • What’s new in Gutenberg 14.6 has been published.
  • Support will end for WordPress 3.7 – 4.0 on December 1, 2022. The last release party for these versions will be on November 30, 2022. More in the post.
  • The WordPress developer blogblog (versus network, site) is in public 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.. Contributors needed. For more information please contact @bph or join the #core-dev-blog channel in the Make WordPress slack. Update post.
  • The call for nominations for 2023 Core Team Representatives is open until December 2, 2022. Self-nominations are welcomed.
  • DevHub is getting a new look. Feedback from developers needed, particularly on the way documentation has been split and the way 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. changed inside the articles in the code reference. Please comment in Figma or on this post from the documentation team.

2) Blog posts of note

Slack link.

3) Upcoming releases

Slack link.

The next major is 6.2; the next minor is 6.1.2. Look for updates next week.

4) Components and tickets

Slack link.

a) Components

No major news this week for these components:

  • Build/Test Tools
  • Date/Time
  • General
  • 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.
  • Permalinks

Help needed with onboarding new maintainers. If you’re a maintainer with tips you can share and/or are willing to let someone shadow you, please contact @marybaum

b) Tickets

@helen highlighted ticketticket Created for both bug reports and feature development on the bug tracker. #57187 for people who had particular experience in containers.

5) Open Floor

Slack link.

No issues were discussed.

Props to to @marybaum and @webcommsat for facilitating; to @DavidPotter for the summary, and to @webcommsat and @audrasjb for reviewing; and to @estelaris, @audrasjb, @azaozz, and @sergeybiryukov for participating.

#6-2, #dev-chat, #summary

Editor chat summary: 23 November 2022

This post summarises the weekly editor chat meeting (agenda here) held on Wednesday, November 23, 2022, 14:00 UTC in Slack. Moderated by @andraganescu.

Announcements and Links

Key project updates

Task Coordination

N/A

Open Floor

@andraganescu noticing that the meeting was the lowest engagement and participation ever recorded, confirming quite a long and steady trend of this meeting loosing its purpose, raised that we should make the meeting twice a month and also reshape its usefulness.

This is also a requirement because 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/ appears to be managed by the community much better than a couple of years a go:

  • there are consistently updated tracking issues
  • there are repeated and well done outreach programs
  • most of the editor issues end up as 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/ issues

Therefore having a meeting just to have it seems pointless.

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Read complete transcript

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

Performance Chat Summary: 22 November 2022

The full chat log is available beginning here on Slack.

Announcements

  • @clarkeemily thanked the team for the 1.7.0 release yesterday

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

  • No updates

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

Feedback requested

Measurement

N/A

GitHub project

  • No updates

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

  • @aristath continues to refine the SQLite module, and it’s pending a review so we can merge it
  • @aristath started working on a draft post to publish on make when the SQLite module gets merged, to invite testers.
  • @aristath having difficulty running performance A/B tests for the WP-CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. classes autoloader POC. This one is going to take some more time.
  • @OllieJones has been working on an sqlite-object-cache 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 (see repo). He mentioned it in last week’s meeting, but the question is whether we want to include this as a module in the performance-lab plugin. Right now it’s standalone and works perfectly fine. My personal opinion is it should be considered as a module… SQLite is universal and can therefore be used in Core to improve performance as a caching mechanism.

Feedback requested

Infrastructure

@flixos90

GitHub project

  • No updates

Feedback requested

Open floor

  • @oandregal asked: for folks working around wp_get_theme etc. Wanted to share a cross-PRs comment. I’m having troubles following direction regarding whether or not to use wp_get_themeThis PR proposes removing it from some places (backports changes from core), while these other two proposes to add it to a few hotpaths. Would you mind clarifying direction and nuances in this thread? Thank you.
    • @spacedmonkey has replied on the PR
    • @flixos90 also advised his response would be the same, we want to avoid calling wp_get_theme() multiple times where it can be called once instead. It’s not that we shouldn’t use the function anymore, just be conscious of limiting its usage to when it’s necessary
      • @10upsimon Perhaps a discussion for elsewhere @flixos90 but has there been consideration for a singleton instance response? i.e wp_get_theme() returns a singleton instance ( ::get_instance()) as opposed to instantiating a new class with each function return statement? Is there ever a valid cause for re-instantiating the WP_Theme class? I’m sure it’s far more complex and involved than I make it out to be, and I’d assume that this has been considered.
      • @spacedmonkey and @flixos90 advised we shouldn’t use singleton. But even if we use a global, there is a potential risk: Object instances are mutable so if any change was made on one instance returned from the function, it would affect every other instance if we went with a scenario where no new entity was returned on every call. For the most part this could be a backward compatibility break. So I’m not really sure this would be a worthwhile effort
  • @clarkeemily Just to call out there are currently 15 open issues marked as ‘Needs Review‘ across all focus areas and please keep an eye out for any PRs that may need review alongside these
    • @cpal I’ve recently been looking for ways we can leverage our in-house performance/load/functional testing solution at Pressidium® to help out the core-performance team in whatever way we can but I haven’t found something totally relevant just yet. I’m happy to share details on what we currently have available in the testing realm and what is yet to come.
      After having a brief into chat with @aristath, I believe we may be able to get something going with some of the work he is currently tackling after some further discussion.
      What do you all think?? Help a noob out that’s eagerly looking to find his footing in the WP Community by throwing out some relevant suggestions if-ever/whenever you can!
      • @adamsilverstein asked if a brief overview could be provided on testing in the context of WordPress Performance
      • Pressidium is a managed/HA hosting provider and I’m tasked with performance testing that we currently use to test out client sites and services depending on the needs on the client but since we went through (and are continuing with) developing a testing infrastructure we want to give back to the WP community with it all.
      • Further discussion / introduction ongoing here in the 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/. chat

Our next chat will be held on Tuesday, November 29, 2022 at 16:00 UTC in the #core-performance channel in Slack.

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

Editor chat summary: 16 November 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, November 16, 2022, 14:00 UTC in Slack. Moderated by @bph.

Announcements and Links

Key project updates

@andrewserong posted an update on the Layout Option post

@annezazu updated the High Priority list of the issues for Phase 2 Customization 

There are quite a few issues, for which designs are available, and they are now in need of developers.

Global Styles

Editor

Navigation

Templates

Should any of these issues interest you to tackle, and you have the bandwidth, you could add yourself as assignee via the project board

Also, even if you are not yet ready to contribute, and some of us have full plates, you can still chime in on the issues and discuss the most recent approach.

Task Coordination

@getdave commented on the agenda post: He’d like to flag this bugfix for the Link UI text replacement. It would be great to get some reviews on it. Dave also has been working with other contributors on the new UX for Editing Menus in the Navigation block. Reviewers and contributors are very welcome.

@paaljoachim commented on the Agenda post: I would like to bring some attention to this comment by @aaronrobertshaw
“We want a means of setting text decoration (including none) on individual blocks as well as 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. & global styles.”

Open Floor

 No open floor discussion topics were raised during the meeting.

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Read complete transcript

Props to @paaljoachim for review

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

Dev Chat summary: Wednesday, November 16, 2022

The weekly WordPress developers chat meeting was held 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/. at 20:00 UTC.

Start of the meeting in Slack.

Announcements

Slack link.

WordPress 6.1.1 landed yesterday!

Nominations for 2023 Core Team Representatives are now open. The deadline for nominations is December 2, 2022.

Blogblog (versus network, site) posts of note

Slack link.

No other blog posts were shared.

Upcoming releases

Slack link.

For those new to dev chat, this is where any updates on the releases are shared.

The 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. is 6.2

WordPress 6.2 Development Cycle. This will be the first major release of 2023. 6.2 is in alpha and tickets are still early.

The next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. is 6.1.2

Due to upcoming holidays, these timelines were discussed:

6.1.2 planning post: mid-December 2022 or January 2023

6.2 planning post: January 2023

2023 planning post: January, likely ahead of the 6.2 planning post

Components and tickets

Slack link.

a) Components

For anyone new, there is a help / ticketticket Created for both bug reports and feature development on the bug tracker. update section each week in dev chat. Contributors can add requests to the agenda post for tickets they would like to highlight. If a maintainer can not make dev chat, they can also share their updates on the agenda.

If you are a maintainer, it is really helpful to share news about your component in dev chat live or on the agenda post. It is also a chance for all your efforts to be shared and to ask for more people to review a particular item.

No major news this week for these components:

  • Build/Test Tools
  • Date/Time
  • General
  • 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.
  • Permalinks
  • Help/About
  • Quick/Bulk Edit

b) Tickets

None were raised.

Open Floor

Slack link.

a) Removing functions during release candidates

This comment on the agenda post was discussed. It asserts that this 10/24/22 release candidate commit (54682) removed the reset() function, and asks for removing functions during release candidates to be disallowed – if it’s not already.

In the replies that followed, it was mentioned that when 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). methods or functions are changed, developers using them for tests could be sent a warning email, and that it could help if to use function_exists() to confirm functions are still available.

Props to @marybaum for leading the meeting, @davidpotter for writing the summary and to @davidbaumwald for reviewing, and to @webcommsat, @marybaum, @bph, @jeffpaul, @sergeybiryukov, @elrae, @joedolson, @desrosj, and @hellofromtonya for participating.

#6-2, #dev-chat, #summary

Performance Chat Summary: 15 November 2022

The full chat log is available beginning here on Slack.

Announcements

  • Excellent update on the 6.1.1 release, which is going out today12 out of the 30 tickets in the 6.1.1 release are focused on performance! That is a great outcome and a testament to the team’s hard work on addressing some of the follow up quirks around 6.1 performance

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

  • @spacedmonkey: No updates on object caching, has been focusing on 6.1.1 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.
    • A lot of theme.json parsing 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. have very serious performance issues
    • We have fixed a couple of them and they are making the way in 6.1.1
    • Another very relevant ticketticket Created for both bug reports and feature development on the bug tracker. is #57077 and #57114
  • @OllieJones: has a prototype of SQLite3 persistent object cache cooking; will make a module proposal soon (basically use SQLite for object caching rather than the main DB)
    • @flixos90: I wonder how much that overlaps or potentially conflicts with the proposal to use SQLite as database
    • @aristath: No overlap or conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved.… But they can definitely be combined for a performance boost
    • @flixos90: If a site can benefit from an SQLite DB speed and we implement that feature reliably, why would you not want to use that but then use it for an object cache?
    • @OllieJones: there are many installations that could benefit from a persistent object cache 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, without requiring a port of the main data to SQLite. And backup / redundancy / infrastructure would not need to change
    • @flixos90: The idea sounds very useful to me especially given wider support of SQLite, but I would still like to explore a better answer on balancing this “SQLite as cache” project with the “SQLite as DB” project and the tradeoffs between the two

Feedback requested

Measurement

N/A

GitHub project

  • No updates

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

Feedback requested

Database

@olliejones

GitHub project

  • @aristath: SQLite PR is ready for another round of tests and reviews
    • @flixos90: reviewed it a few times and it looks excellent to me. Some quirks to still address mostly. One thing I still want to explore a bit more is trying to figure out a way to have the SQLite DB prepopulated so that you don’t end up on the WP Install screen after updating the module; this wouldn’t be a blockerblocker A bug which is so severe that it blocks a release., but it would make the user experience a whole lot smoother
    • @flixos90: I would suggest we polish this over the next week and aim for a merge within the next 2 weeks? This way we can publish the first version in the upcoming Performance Lab 1.8.0 release mid December
  • @aristath will work on drafting a Make CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post on the SQLite module for once it’s in the Performance Lab plugin
    • @flixos90: Best to draft it soon, so that we can review and finalize it early; this way we can publish it immediately the same day that that release will go out (December 19)

Feedback requested

Infrastructure

@flixos90

GitHub project

  • @flixos90: Next Monday we’ll have the Performance Lab 1.7.0 release
    • At the moment, there are still 5 PRs in the milestone which need to be committed or punted by tomorrow
    • @mukesh27: PR #582 is ready for your review
      • @flixos90: Looks like that PR tackles a 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. that #578 also focuses on (although that one does a bit more)
    • @flixos90: Given the size of the database health checks PR, I think it’s a bit too early (or too late, if you look at it from another angle) to merge it this short before the release, also since it’s a new module
      • @OllieJones: ok. let’s puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) it; will iterate on it so maybe we can merge it in the next few weeks for 1.8.0
    • @mehulkaklotar: PR #571 is under reviews right now, we will be able to merge it before tomorrow
    • @pbearne: I believe they are ready but will check

Feedback requested

Open floor

  • @OllieJones: I’d like to see w.org sign up for the https://greensoftware.foundation/
    • @flixos90: What kind of effort or commitment does that entail? As mentioned on the issue that you opened about this, this would probably be best to move forward with a Make Core post proposing it; getting a sense of interest at a larger scale is one reason I’d propose writing a Make Core post

Our next chat will be held on Tuesday, November 22, 2022 at 16:00 UTC in the #core-performance channel in Slack.

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

Dev Chat summary, November 9, 2022

The weekly WordPress developers chat meeting was held 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/. at 20:00 UTC.

Start of the meeting in Slack.

1.Welcome everyone

For anyone new to dev chat, you can find out more about this weekly meeting in the handbook.

The Dev Chat summary by @webcommsat and review by @pbiron and @audrasjb.

Agenda preparation – thanks to @webcommsat and @nalininonstopnewsuk for stepping in.

Meeting facilitators: @webcommsat and @desrosj, with @jeffpaul covering 6.1.1

2. Announcements

Reminder: WordPress 6.1 “Misha” was released, November 1, 2022

There is also now a 6.1 retrospective post – thanks @priethor

What’s new in Gutenberg 14.5 release post, November 9, 2022

3. Blogblog (versus network, site) posts

A Week in Core – November 7, 2022 – thanks to @audrasjb

No other blog posts were shared.

@webcommsat: a plug from the work from marketing, please do share social media posts from WordPress.org accounts. Social posts about the release continue to be very popular. If you are interested in stats, check out the marketing team’s blog as the notes report on this weekly.

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. nominations and elections 2023

@webcommsat highlighted that teams are starting to think about team rep elections for 2023. More on this in future meetings from the current team reps @marybaum and @audrasjb. @chanthaboune is also planning to write a post on the Make/ Updates blog on team rep elections in the project, and has said teams that have a robust nomination process can get started for 2023. @jeffpaul offered to help with the nominations and elections process in core from his previous experience.

To keep this in people’s awareness and as encouragement to contributors, the team rep nominations will be on the agenda for future dev chats in the run up to the elections for 2023. Once the nomination post in published, contributors can self-nominate or nominate anyone they think would be good in this role. The post will be shared in dev chat. If people are potentially interested, they can also chat with @marybaum or @audrasjb before adding a nomination to the public post. The election list will be posted on the core blog, but as part of the process, there will be a confirmation check with anyone nominated to make sure they are happy to stand.

Background: Team Reps and what they do in the project; 2022 process for Core Team Rep nominations

Discussion followed on whether a core team rep needed to be a 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.. It was confirmed that it was not a requirement. @desrosj, and confirmed by …, “Honestly, it may be nice for both to not be a committer so that less coordination work falls on the shoulders of committers, and they have more free time to perform code reviews and commit duties. But being a committer also doesn’t disqualify you.”

4. Forthcoming releases

For those new to dev chat, this is where any updates on the releases are shared.

a) Latest 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.1

Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for 6.1 find them at the dev-notes-6-1 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.). The Field Guide for 6.1.

Check out the 6.1 retrospective post – thanks @priethor.

@desrosj: All feedback and perspectives are welcome! Even if you were a casual contributor during the cycle, please do pass along your thoughts.

b) Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: 6.1.1

WordPress 6.1.1 Planning is live.

  • Editor sync to core for tomorrow, November 10, 2022
  • 6.1.1 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. scrub is scheduled for tomorrow, November 10, 2022 at 17:30 UTC
  • 6.1.1 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). planned for Friday November 11, 2022 at 16:00 UTC
  • plan for 6.1.1 release on November 15, 2022. The release party will start at 17:00 UTC and aim to be ready for testing of the minor release package around 18:00 UTC

These will both take place in the core channel of the Make WordPress Slack.

Everyone welcome to help. @jeffpaul do you have anything to add on 6.1.1

Call for help: @jeffpaul encouraged people to help test and provide feedback, assist with patches/PRs, and/or help with commits on items in 6.1.1.

Later in the meeting, @desrosj shared there are 21 tickets currently in the workflow for 6.1. Tomorrow (November 10), @jeffpaul and @desrosj will be ‘heavy handed punting’ these tickets.
Action: They asked for any ticketticket Created for both bug reports and feature development on the bug tracker. to be updated which people felt strongly about making it in the time available for this release.

A question was raised on timings for the 6.1.1 release. The 6.1.1 planning post helps with this and is currently pinned to the top of the core blog.

c) Next major: 6.2

The Development Cycle page is up on the core blog and will be updated as we move through the cycle.

No other updates on 6.2 at dev chat.

5. Component maintainers updates / tickets / requests for help

a) Components

For anyone new, there is a help / ticket update section each week in dev chat. Contributors can add requests to the agenda post for tickets they would like to highlight. If a maintainer can not make dev chat, they can also share their updates on the agenda.

If you are a maintainer, it is really helpful to share news about your component in dev chat live or on the agenda post. It is also a chance for all your efforts to be shared and to ask for more people to review a particular item.

@sergeybiryukov: Build/Test Tools, Date/Time, General, 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., Permalinks: No major news this week.

@webcommsat: About/ Help and Bulk/ Quick Edit components – weekly focus on this will resume next week due to illness in the group. We will also be joined by two contributors who are interested in becoming maintainers or helping more with components. Timezones to enable this are being looked at.

b) Tickets

Action: @costdev requested if anyone is familiar with setting up WordPress to use FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients., testing on #56966 would be much appreciated. There is a detailed and very helpful testing note is on the ticket.

#56966: Updating plugins with WP6.1 creates .maintenance file and leaves it

No other tickets raised nor added to the agenda.

6) Open Floor

@costdev asked if the 6.1.1 release party could be held at 18:00 UTC rather than the planned 17:00 UTC as there were a lot of clashes with the Upgrade/Install component meeting during 6.1. The move would reduce disruption and mean the Upgrade/Install team could join for testing releases. They had to regularly skip the component meetings which are at 17:00 UTC to make sure the release was installing correctly.

Action: Agreed time change. Final party will still start at 17:00 UTC but the packaging and testing will move to around 18:00 UTC. @jeffpaul to update the Make/Core post timeline.

Props to: @webcommsat and @desrosj for running dev chat, @webcommsat for the summary, and to @jeffpaul and @costdev for review.

#6-1, #6-1-1, #dev-chat, #summary

Performance Chat Summary: 8 November 2022

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

Mini 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. scrub of performance issues for 6.1.1

  • See here
  • https://core.trac.wordpress.org/ticket/56923 – PR committed; should become available when @mamaduka syncs 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/ to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. on Thursday
  • https://core.trac.wordpress.org/ticket/56815 – assigned to @flixos90 for review
  • https://core.trac.wordpress.org/ticket/56900 – assigned to @peterwilsoncc for commit
  • https://core.trac.wordpress.org/ticket/56945 – @flixos90 has PR in progress at https://github.com/WordPress/wordpress-develop/pull/3536 that needs review and feedback, especially from Gutenberg team. @annezazu working to loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. someone in there.
  • https://core.trac.wordpress.org/ticket/56948 – ready for commit, just needs a final review; assigned to @peterwilsoncc
  • https://core.trac.wordpress.org/ticket/56952 – @adamsilverstein to look into
  • https://core.trac.wordpress.org/ticket/56974 – @flixos90 took a first look at the PR last week and will give it a comprehensive review today
  • https://core.trac.wordpress.org/ticket/56990 – @adamsilverstein‘s changes need review/testing
  • https://core.trac.wordpress.org/ticket/56991 – @spacedmonkey‘s fix at https://github.com/WordPress/wordpress-develop/pull/3575 needs review
  • https://core.trac.wordpress.org/ticket/57012 – ready for commit by @peterwilsoncc

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

  • @adamsilverstein: Discovered a library, jSquash, that brings image format encoding/decoding to the web. Tested a bit and oping to use it to enhance the core image 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. with modern image capabilities. If successful, would let us introduce AVIF support without depending on server-side support.
  • @mehulkaklotar: Working on #563 for Performance Lab to change default WebP quality to 82; PR needs review.

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

  • @spacedmonkey: Working mostly on 6.1.1 issues, but a few for 6.2, as well:
    • https://github.com/WordPress/wordpress-develop/pull/3544
    • https://github.com/WordPress/wordpress-develop/pull/3528
    • https://github.com/WordPress/wordpress-develop/pull/3534
    • https://github.com/WordPress/wordpress-develop/pull/3366
    • https://github.com/WordPress/wordpress-develop/pull/3365
    • https://github.com/WordPress/wordpress-develop/pull/3178
  • @tillkruess: Chatted with @johnjamesjacoby about adding a health check for the new wp_cache_supports() function to show which object caching features are supported/not supported but recommended. See https://github.com/WordPress/wordpress-develop/pull/3347. For example, get_multiple() is quite important. Any feedback on adding as a health check?
    • @spacedmonkey: Now have wp_cache_supports in core that we could use and wp_cache_supports( 'get_multiple') in all options. Instead of loading all options in one cache key, load each in their own cache key and all in single call.

Feedback requested

Measurement

N/A

GitHub project

  • No updates

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: Plugin codebase is now updated to reflect our recent modifications to the focus areas per https://github.com/WordPress/performance/pull/566, thanks to @mukesh27

Feedback requested

Our next chat will be held on Tuesday, November 15, 2022 at 16:00 UTC in the #core-performance channel in Slack.

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

#meta