Editor chat summary: Wednesday, November 30 2022

This post summarizes the weekly editor chat meeting on Wednesday, 30 November 2022, 04:00 PM GMT+2 held in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. You can view the full transcript here.

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/ releases

Gutenberg 14.6.1 was released on Nov. 25
Gutenberg Plugin 14.7 RC1 was released on Nov. 30, 22

Key project updates

The latest update on all the phase 2 issues was also posted by @annezazu

There are three tickets that still need dev help:

Task Coordination

@bernhard-reiter shared an issue that needs help getting reproduced. This was discussed more in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. devchat:

We’re currently investigating the .is-layout-flex issue. I’ve suggested a strategy to test our tentative fix and ship a WP 6.1.2 point version that I’d like to discuss during that chat later tonight. If you’d like to help out or if you’re otherwise interested, please join the devchat in about 5.5 hours! (If you can’t make it, feel free to leave your comments below mine, or at the GitHub issue.) Thank you! ❤️

Open Floor

We spend the entirety of the open floor discussing ideas on how to make the core editor chats more valuable and engaging. Over the past year, we’ve seen less engagement and participation. So we think it’s time to rethink the format of these chats.

@get_dave, @bernhard-reiter, @bph, @priethor, and @daisyo all shared great ideas and insights. You can view the full conversation in slack.

The ideas we came up with during the open floor are:

Better updates on Key projects
Key contributors in the room
Get help/volunteers for small-scope projects
Dive into a specific feature every week so that more folks not actively working on it can give it a spin, provide feedback, and, in general, unblock it with broader testing
A more informal, less structured meeting, more like office hours
Improving collaboration with folks on what I’m working on

@daisyo summarized it nicely:

When we try to cover everything that is being worked there is never enough time to go deeper in this meeting. Compiling the conversation today I’d suggest a Weekly featured project that’s predetermined and that someone deeply knowledgeable about the history, current status, and planned future can share. This would require some coordination and preparation ahead of time, of course, and it could be that it’s not possible to do every week.

It could also end up being a forced march that nobody wants to volunteer for. In which case there is something to be said about throwing a topic (like how do we make these meetings more engaging) out and see if it resonates enough to start a conversation.

What would YOU want to get out of a core-editor meeting, that will make you come back every week for an hour?

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

Jb Audras 11:36 pm on December 5, 2022
Tags: 6.2 ( 9 ), core ( 461 ), week in core ( 200 )

A Week in Core – December 5, 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 November 28 and December 5, 2022.

35 commits
31 contributors
65 tickets created
6 tickets reopened
55 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

Build/Test Tools

Add basic e2e coverage for 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/ – #57197
Improve caching for PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. – #57148, #53841
Stylistic changes to Gutenberg e2e test – #57197

Code Modernization

Rename parameters that use reserved keywords in wp-includes/formatting.php – #56788
Rename parameters that use reserved keywords in wp-includes/functions.php – #56788
Rename parameters that use reserved keywords in wp-includes/functions.wp-scripts.php – #56788
Rename parameters that use reserved keywords in wp-includes/functions.wp-styles.php – #56788
Rename parameters that use reserved keywords in wp-includes/general-template.php – #56788
Rename parameters that use reserved keywords in wp-includes/kses.php – #56788

Coding Standards

Add visibility to methods in tests/phpunit/tests/ – #56791
Add visibility to properties in tests/phpunit/tests/ – #56791
Always use parentheses when instantiating an object – #56791
Always use strict type check for in_array() – #56791
Fix a non-snake_case function name in WP_Block tests – #56791
Fix indentation of multi-line chained method call in test_json_error_with_status() – #56791
Fix spacing for incrementors and decrementors in various files – #56791
Remove a one-time $loading variable in get_avatar() – #56791
Remove redundant semicolon after get_template_hierarchy() – #56791
Use consistent markup for line break tags on update-core.php – #57226, #56791

Comments

Make moderated or disallowed key check case-insensitive for non-Latin words – #57207

Customize

Fix a wrong condition on WP_Customize_Manager::has_published_pages() – #57198

Media

Fix the initialization of imgAreaSelect when cropping a headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. image or a site icon or logo – #54308, #55377
Fix the version string of imgAreaSelect to indicate when the second set of modifications were made – #54308

Options, 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. APIs

Improve error messages in Options Management Administration Screen – #57230

Plugins

Correctly display spaces in installed plugins search results – #57174

Query

Account for primed post caches without primed post meta/term caches – #57163

Security

Improve accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) of security policy – #57222
Remove useless span tags from SECURITY.md – #57243
Update supported WordPress versions in security policy – #57217

Bundled Themes

Twenty Seventeen: Fix comment indentation in twentyseventeen_setup() – #56791
Twenty Ten: Remove unwanted title attributes – #57199, #24766, #24203
Twenty Thirteen: Remove unwanted title attributes – #57199, #24766, #24203
Twenty Twelve: Remove unwanted title attributes – #57199, #24766, #24203
Twenty Twenty-Three: In page template, make post titles links – #57175
Twenty Twenty: Remove unwanted title attributes – #57199, #24766, #24203

Props

Thanks to the 31 people who contributed to WordPress Core on Trac last week: @jrf (16), @costdev (9), @sergeybiryukov (9), @aristath (6), @poena (6), @justinahinon (6), @sabernhardt (5), @audrasjb (4), @mukesh27 (4), @peterwilsoncc (3), @ironprogrammer (2), @ajmaurya (1), @rajanpanchal2028 (1), @alberuni-azad (1), @felipelavinz (1), @spacedmonkey (1), @ocean90 (1), @desrosj (1), @bonjour52 (1), @obenland (1), @254volkan (1), @nmutua (1), @arthur791004 (1), @alshakero (1), @syamraj24 (1), @adhun (1), @dilipbheda (1), @dlh (1), @NekoJonez (1), @TobiasBg (1), and @scruffian (1).

Congrats and welcome to our 5 new contributors of the week: @ajmaurya, @felipelavinz, @254volkan, @nmutua, @syamraj24 ♥️

Core committers: @sergeybiryukov (17), @audrasjb (9), @bernhard-reiter (3), @azaozz (2), @peterwilsoncc (2), @desrosj (1), and @ocean90 (1).

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

Bethany Chobanian Lang 1:42 pm on December 5, 2022
Tags: agenda ( 824 ), meeting ( 190 ), performance ( 145 ), performance-chat ( 110 )

Performance Chat Agenda: 6 December 2022

Here is the agenda for this week’s performance team meeting scheduled for December 6, 2022, at 16:00 UTC.

Announcements
Focus area updates
- Images
- Object Cache
Infrastructure
Open floor

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:46 pm on December 2, 2022
Tags: team reps ( 15 )

Core Team Reps for 2023: Submit Your Votes

Two weeks ago we opened up nominations for new CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps to replace @marybaum and me. Nominations have closed, so now it’s time for voting!

You can find the poll below. Since we’re aiming to elect two reps, you can vote for up to two people.

What Are Team Reps?

In the WordPress open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project, each team has on average one or two representatives, abbreviated as reps. Some teams have more than two, but for the sake of sanity sticking with two for now keeps things simpler. And for the historians out there, the role goes way back to 2012.

Historically with the Core team, 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. duration was around a year, though some reps stuck around longer if there was a particularly good fit.

Anyone who serves as a “team rep” is responsible for communicating on behalf of the Core team to the other contributor groups via weekly updates, as well as occasional cross-team chats. Reps are also consulted on 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/., to help find someone on the Core team who will be at an event who can help lead a Core table. Full details on the Team Rep role is on the Team Update site.

It is not called “team lead” for a reason. It’s an administrative role. While people elected as team reps will generally come from the pool of folks that people think of as experienced leaders, the team rep role is designed to change hands regularly.

This role has a time commitment attached to it. Not a huge amount, but it’s at least one or two hours a week.

Here are the main tasks:

Post the devchat agenda, host the chats, and summarize them. More details on coordinating devchat are available in the Core handbook.
Writing regular Core team recaps and posting it in the Updates blogblog (versus network, site).
Write the Week in Core post.
Keeping an eye on the moving parts of the team to be able to report for quarterly updates (example).

Then… let’s get ourselves two new reps!

Where Can I Vote?

Vote here!

You can vote for up to two people at the same time, but once you have submitted your vote you won’t be able to vote again.

If you have any questions, please feel free to ask in the comments. @marybaum and I will be happy to reply. Thanks!

This poll will remain open until Friday, December 16, 2022 at 23:59 UTC, after which team reps will be chosen based on the votes received.

Co-authored by @audrasjb and @marybaum.

#team-reps

David Potter 11:55 pm on November 30, 2022
Tags: 6.1 ( 89 ), 6.2 ( 9 ), dev chat ( 593 ), summary ( 634 )

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.

DevHub getting a new look post shared. @estelaris requested feedback from core team members by Friday December 2, 2022 on a second iteration of DevHub’s new look. Feedback on both accuracy and usability are important. The landing page is pretty much done, request for developers to check on the code blocks and the items on the menus. Feedback can be left in Figma or the post itself.
Proposal: Amend the Inline Documentation Standards for multi-line comments. The standards in question.
A Week in Core – November 28, 2022.

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

marybaum 4:30 am on November 30, 2022
Tags: agenda ( 824 ), core ( 461 ), dev chat ( 593 )

Devchat agenda, November 30, 2022

1. Welcome

The WordPress Developers’ chat happens every Wednesday in the #core channel of 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. If you’re keeping track, here’s last week’s summary.

2. Announcements

The final versions of WordPress 3.7 – 4.0 have landed with a notice on each that they are no longer supported. Please encourage your users to upgrade to WordPress 6.1.1, running PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 or later.

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 RC1 will land while devchat is happening. More info to come!

Nominations for the 2023 Core team reps will close Friday.

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

From @estelaris, the Docs team is looking for feedback on a second iteration of DevHub’s new look.

From @audrasjb comes the latest A Week in Core.

@azaozz proposes a change to multiline commenting standards.

4. Upcoming releases

The next major is 6.2; the next minor is 6.1.2.

December is a great time to work on the things you would most like to see land in 6.2—before the release cycle ramps up in the new year.

5. Components and tickets

If you’ve got the tickets, the devchat group has the time.

6. Open floor

Add your item to the comments!

#agenda, #dev-chat

Peter Wilson 1:12 am on November 30, 2022
Tags: releases ( 29 )

Now Available: WordPress 3.7-4.0 Final Releases

WordPress 3.7.41, 3.8.41, 3.9.40 and 4.0.38 are now available!

These releases feature an update to the upgrade notification to indicate these versions of WordPress are no longer receiving security updates. WordPress 4.1 and later will continue to receive such updates.

The next major version of release of WordPress will be version 6.2 planned for next year.

On sites running WordPress 3.7-4.0 with automatic updates enabled, the upgrade process will begin automatically.

These releases should not be used on new production websites. The latest version of WordPress is available from the downloads page.

Thank you to these WordPress contributors

These releases were led by Josepha Haden Chomphosy and Peter Wilson with Dion Hulse running mission control.

These WordPress releases would not have been possible without the contributions of JB Audras, Colin Stewart, Česlav Przywara, Robin, Jonathan Desrosiers, Linkon Miyan, Mukesh Panchal, Sumit Bagthariya, Matt Mullenweg, Josepha Haden Chomphosy, Peter Wilson, Dion Hulse and the WordPress security team.

As there was no update to the currently stable version of WordPress, version 6.1, these releases were announced here rather than on wordpress.org/news. It was announced on 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/ these version of WordPress would cease receiving security updates earlier this year.

Thanks to @costdev for proofreading this post.

#releases

Bethany Chobanian Lang 5:38 pm on November 29, 2022
Tags: core-js ( 121 ), core-media ( 94 ), hosting-community ( 22 ), meta ( 22 ), performance ( 145 ), performance-chat ( 110 ), summary ( 634 )

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

@mukesh27: Working on Regenerate thumbnail duplication webp file #575
@mxbclang: Noting a few items that are able to picked up if anyone has interest/capacity; see Needs Dev below
@adamsilverstein: fetchpriority experimental module was merged last week and is planned for release in v1.8.0 in December

Feedback requested

See above
Needs Discussion (10 issues)
Needs Dev (2 issues)

Object Cache

@tillkruess @spacedmonkey

GitHub project

@spacedmonkey: Focusing on theme.json parsing issues, so lots of code review. Working on:

Feedback requested

See above
Needs Discussion (4 issues)
Needs Review (1 issue)

Measurement

N/A

GitHub project

No updates

Feedback requested

Needs Discussion (5 issues)
Needs Review (1 issue)

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

Tree-shaking block styles on the frontend #41020
Needs Discussion (4 issues)
Needs Review (2 issues)

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

Needs Discussion (2 issues)
Needs Review (3 issues)

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

See above
Needs Discussion (5 issues)
Needs Review (3 issues)

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

Jb Audras 9:33 am on November 29, 2022
Tags: 6.2 ( 9 ), core ( 461 ), week in core ( 200 )

A Week in Core – November 28, 2022

26 commits
32 contributors
76 tickets created
0 tickets reopened
66 tickets closed

Code changes