Jb Audras 10:10 pm on October 25, 2021
Tags: , , ,   

A Week in Core – October 25, 2021

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 October 18 and October 25, 2021.

  • 14 commits
  • 9 contributors
  • 37 tickets created
  • 5 tickets reopened
  • 31 tickets closed

The Core team is currently working on the next point (5.8.2) and major (5.9) releases 🛠

Worth noting that each feature slated to the 5.9 milestone has been validated, that the Twenty Twenty-Two Theme development is on the way, and the 5.9 bug scrub schedule has been published 🚀

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.

We can note that there has been a decrease in the number of commits. Hopefully this will increase again quickly.

Code changes

Build/Test Tools

  • Use the correct workflow name in notifications on workflow_run – #53363
  • Restore 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/. notifications for older branches – #53363
  • Add @ticket references for page_on_front canonical tests – #53363
  • Adjustments as a follow up to [51921] – #53363
  • Modify the Slack notifications workflow to be a reusable one – #53363
  • Fix syntax for passing secrets to a called workflow – #53363
  • Pass required secrets to the Slack notifications workflow – #53363

Coding Standards

  • Rename $theHeaders variable to $processed_headers in WP_Http_Curl::request() – #53359
  • Rename the $arrHeaders variable to $processed_headers in WP_Http_Streams::request() – #53359
  • Escape id attributes in WP_Customize_Control::render_content() and ::print_template() – #54295
  • Improve escaping in wp_login_form() – #54279
  • Improve escaping in wp-admin/theme-install.php – #54277

Docs

  • Use sign-up & signup consistently in wp-signup.php – #54041, #53399

Help/About

  • Don’t output empty tags on Credits screen – #54275

Props

Thanks to the 9 people who contributed to WordPress Core on Trac last week: @audrasjb (3), @sabbirshouvo (3), @mukesh27 (3), @jeffpaul (1), @henry.wright (1), @SergeyBiryukov (1), @sabernhardt (1), @afragen (1), and @sayedulsayem (1).

Core committers: @sergeybiryukov (7), @desrosj (6), and @peterwilsoncc (1).

#5-8-2, #5-9, #core, #week-in-core

Paal Joachim Romdahl 6:43 pm on October 25, 2021
Tags: , , ,   

Editor Chat Agenda: 27 October 2021

Facilitator and notetaker: @andraganescu

This is the agenda for the weekly editor chat scheduled for Wednesday, October 27 2021, 04: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/..

  • 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/ 11.8 will be released Wednesday.
  • WordPress 5.9 “Go, no go” date and priorities.
  • WordPress 5.9 Feature Go/No-Go | October 14, 2021
  • Whats next in Gutenberg: Mid-September 2021.
  • Updates based on updated scope for site editing projects:
    • Navigation 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. & Navigation Editor.
    • Template editor.
    • Patterns.
    • Styling.
    • Mobile Team.
  • Task Coordination.
  • Open Floor.

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

Paal Joachim Romdahl 9:19 am on October 25, 2021
Tags: , , , ,   

Editor chat summary: 20 October, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on  Wednesday, October 20 2021, 04:00 PM GMT+1. in Slack. Moderated by @paaljoachim.

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 releases

Gutenberg 11.8.0 RC Thanks to @vcanales for tackling the release.
What’s new in Gutenberg 11.7 release notes. Thanks to @zieladam for writing the notes and handling the release.

Highlights:

  • Navigation 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 Navigation Editor Advances.
  • Global Styles and Full Site Editing improvements.
  • Columns Block for tweaking gaps and margins.
  • Link control – Create a page directly inside the link control.
  • A default alignment option – none.
  • + various other enhancements.

WordPress 5.9 Planning Roundup

Proposed WordPress 5.9 Schedule, scope, leads and how to help.

5.9 Priorities

Preliminary road to 5.9.

Full site editing Go/No-Go

WordPress 5.9 feature full site editing Go/No-Go.

Navigation Editor and Block

Summary: Navigation Editor and Block hallway hangout

What’s next in Gutenberg.

What’s next in Gutenberg: Mid-September.

Key project updates

Based on the scope for Site Editing projects.

Template Editor

Update from @noisysocks

Global Styling

Update from @jorgefilipecosta

Patterns

Patterns explorer in modal PR by @ntsekouras.
Exploring a modal system for selecting patterns.

Navigation Block & Navigation Editor

Update from @get_dave

  • The Nav Editor will not be included in WordPress 5.9 – this is because: changes to the block are required for the editor to be a success (see below). We need to allow sufficient time to test the editor before any 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. and allow for community feedback.
  • Following the Hallway Hangout a summary was posted. The outcome was:
  • In the short term, contributor efforts will switch to the Nav block in order to resolve some of the underlying architectural issues
  • Specifically separating the navigation’s presentation from its data in order to make navigations reusable. This serves both the Nav Editor project and the WordPress 5.9 release in general.
  • The Navigation Editor will ultimately focus on manipulating the data of a navigation which is why the above work is a prerequisite for the project’s success.
  • Work on the Nav Editor will resume after WordPress 5.9. We will continue to focus on backwards compatibility whilst looking ahead to the world of blocks.
  • It’s unlikely that we will pursue a new “Classic Menu” block. Rather focusing on the Navigation block (or its data).
  • To this end @talldan has two important Nav block PRs which everyone is encouraged to test and provide feedback on.
  • Link to the Github Navigation Block & Navigation Editor issue.

Mobile Team

Update from @mattchowning

  • Shipped:
    Trigger embed bottom sheet when an embeddable url is pasted into a paragraph block
    Add ability to customize the text and background color in the search block
  • Fixes
    Small fixes for embed block and help screen
    Improve automatic dimming of cover block
  • In Progress
    Adding more tests for the Embed block
    GSS Font size, line height, colors

Task Coordination

@santosguillamot

The main idea is to end up with a Comment Query 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. similar to the existing Query Loop we have for posts. You can check out the scope of the project in its tracking issue. This has been the progress so far:

@mamaduka

@joen

  • Focused on bringing home the navigation block, and making a bunch of tiny PRs to shore up the numerous mostly small glitches.

@annezazu

@ntsekouras

@bph

  • Started plugin/theme outreach regarding Gallery Block Refactor 15 top plugins, responses 10, I’ll do a second attempt to reach the non-responsive. TY @Glen Davies
  •  I will connect with 12 more plugin developers this week, and tackle theme authors.
  • Awesome Live Q & A w/ Helen, Mark and Riad – Discussion “How we make building blocks easier.  Recording on YouTube
  • Developer Hours. We’ll start coordinating schedule and promotion next week.

@get_dave

@paaljoachim

Open Floor

@welcher

@priethor

  • WordPress 5.9 Feature Freeze is planned for November 9th. Last Gutenberg release to be included in 5.9 is 11.9 RC.
  • Check the WordPress 5.9 Must-Haves project board. Contributors are encouraged to add items and bugs that seem necessary to include in this major release.

@clorith


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

Dan Farrow 4:56 pm on October 21, 2021
Tags: ,   

CSS Chat Summary: 14 October 2021

The meeting took place here on Slack. @wazeter facilitated and @danfarrow wrote up these notes.

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

  • @wazeter shared the planning document and noted that we’re in the final stages of migrating existing colour properties to CSS custom-properties
  • @dryanpress is working on reducing the huge number of custom properties in customize-control.css, a process which has revealed hex values shared by multiple properties. These could effectively be replaced by additional theme properties
  • @wazeter noted that sometimes in larger files it’s better to avoid find-and-replacing colour values and instead to go through logical property groupings e.g. box-shadows, then background etc.
  • @wazeter shared a link to every-layout.dev which outlines an approach to CSS architecture which could be relevant to this project, and which demonstrates the need for a good set of default custom properties
  • This led to a conversation about the next steps, in particular the documentation and Table of Contents (TOC) which will accompany the custom-property roll-out

Thanks everybody!

#core-css, #summary

Jb Audras 9:41 pm on October 20, 2021
Tags: , , , ,   

Dev chat summary – October 20, 2021

@audrasjb led the chat on this agenda. You can also read the Slack logs.

Highlighted blogblog (versus network, site) posts

Bringing to your attention some interesting reads and some call for feedback and/or volunteers:

Worth mentioning:

Thanks to the 30 contributors of the past week, including 7 new contributors! Kudos to the 5 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers of the week, too.

A Week in Core – October 18, 2021

Upcoming releases updates

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.(s)

Please note that 5.8.2 was deferred due to the lack of ready-to-ship tickets. WP 5.8.2 RC is scheduled on Tuesday November 2, 2021. With a final release on Wednesday, November 10, 2021.

Reminder: @desrosj and @circlecube are co-leading the 5.8.x releases. The 5.8.x point releases are coordinated in the #5-8-release-leads 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/. channel. This channel is public and will be archived once 5.9 is released.

From @desrosj: If there is anything you’d like to see released prior to 5.9, please make sure to flag it and help bring the ticketticket Created for both bug reports and feature development on the bug tracker. to a resolution!

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.

First announcement, it’s a GO for the main 5.9 features: WordPress 5.9 Feature Go/No-Go | October 14, 2021 🎉

@audrasjb and @chaion07 published the 5.9 Bug scrub schedule.
Please note that anyone can run 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. scrub. Checkout Leading Bug Scrubs in the core handbook.

@chanthaboune added that a Release Squad will be announced soon.

Twenty Twenty-Two was introduced a couple week ago. As usual, there is a public repository on GitHub so feel free to help testing the theme, and to contribute to this project.

Component maintainers updates

Build/Test Tools – @sergeybiryukov

A readme file for end-to-end (e2e) tests was added to WordPress core. It provides instructions of how to run the tests locally and links to documentation. This should hopefully result in more contributors writing e2e tests. See ticket #53550 for more details.

General – @sergeybiryukov

Work has continued on various coding standards fixes in core. See tickets #54177, #54277, #54278, #54284 for more details. Thanks to @sabbirshouvo, a new contributor, for improving escaping in various parts of core!

Internationalization (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.) – @sergeybiryukov

Some Media Library filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. strings now have a context for better translations. See ticket #54238 for more details.

Help/About – @marybaum

Scrubs continue weekly, hosted by @marybaum and @webcommsat. Three tickets will wind up contributing to big changes long-term; a couple of tickets are minor markup changes, so they should be good to go this week.

This component will have another scrub scheduled on Monday October 25, 2021 at 19:00 UTC, focused on tickets slated for 5.9.

Open Floor

@audrasjb asked for an update concerning the new Performance team proposal. @chanthaboune: “There are a few questions that I’m synthesizing into a comment. Performance is, of course, an important thing for the WordPress project as a whole. There were some questions on implementation, though.”

@janthiel asked for a review of #53450. @audrasjb moved it for 5.9 consideration. This ticket will need dev-feedback and a technical review.

@costdev is working on the changes from assertEquals() to assertSame() in the test suite for 5.9 and the “Stage 1” pull request is ready for review: #53364.

@tobifjellner asked for a review of #54300. @audrasjb moved it for 5.9 consideration and added a 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. proposal.

#5-8-x, #5-9, #dev-chat, #summary, #twenty-twenty-two

Ryan Welcher 5:38 pm on October 20, 2021
Tags: ,   

Check out & contribute to the updated Gutenberg Examples

This week, a major portion of the work to update the Gutenberg Examples repository was completed. The repository 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. examples, while accurate, were out of date and didn’t reflect the most current approach to block registration.

These examples can be used in many ways. You can read through them to learn how to create blocks, check out the repository and modify them to see how they work, or use them as a starting point for your own blocks.

All example blocks now use block metadata files and leverage the most recent version of the Block API. Updates were also made to the developer experience to introduce ESlint and Prettier configurations that can be used by IDEs, and to leverage the most recent version of the @wordpress/scripts package.

Share your examples

While the existing examples cover a lot of topics and use cases, it would be great to expand the list and help more folks do more with blocks. In particular, examples covering more advanced block related topics or topics that are not strictly related to creating blocks but still part 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/ developer toolkit, such as SlotFill, are very much needed.

If you’re looking for a way to contribute and grow community knowledge, please consider opening an issue or pull request with your example suggestion.

Special thanks to @mkaz and @gziolo for their help with code review and to @annezazu, @mkaz, @chanthaboune, @sparklingrobots, and @audrasjb for reviewing this post

#developer-documentation, #gutenberg

Francesca Marano 11:05 am on October 20, 2021
Tags: , , ,   

Dev Chat Agenda for October 20, 2021

Here is the agenda for this week’s developer meeting to occur on October 20, 2021, at 20:00 UTC.

Please note that depending on your timezone, the time may have changed with the end of daylight saving time.

Blogblog (versus network, site) Post Highlights and announcements

Bringing to your attention some interesting reads and some call for feedback and/or volunteers:

Next releases status update

Have you been working on 5.9 related issues? Let everyone know!

Components check-in and status updates

  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

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

#5-9, #agenda, #core, #dev-chat

Paal Joachim Romdahl 3:23 pm on October 19, 2021
Tags: , , ,   

Editor Chat Agenda: 20 October 2021

Facilitator and notetaker: @paaljoachim

(Let me know if you would like to become a part of the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor meeting facilitators and notetakers team.)

This is the agenda for the weekly editor chat scheduled for Wednesday, October 20 2021, 04: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/..

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

Jb Audras 10:53 pm on October 18, 2021
Tags: , , ,   

A Week in Core – October 18, 2021

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 October 11 and October 18, 2021.

  • 16 commits
  • 30 contributors
  • 29 tickets created
  • 5 tickets reopened
  • 17 tickets closed

The Core team is currently working on the next point (5.8.2) and major (5.9) releases 🛠

Worth noting that each feature slated to the 5.9 milestone has been validated, that the Twenty Twenty-Two Theme development is on the way, and the 5.9 bug scrub schedule has been published today 🚀

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

Coding Standards

  • Add public visibility to methods in src directory – #54177
  • Add a leading zero in the CSSCSS Cascading Style Sheets. declarations printed by the print_emoji_styles() function – #54284
  • Consistently escape form action URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org in wp-admin/update-core.php – #54278

Cron

  • Fix malformed cron array in wp_schedule_single_event() when _get_cron_array() returns false – #53950
  • Remove errant false values in cron array when upgrading to 5.9+ – #53950

Docs

  • Improve documentation for the tax_input parameter of wp_insert_post() – #54264
  • Update WP_Date_Query documentation to reflect changes in accepted column names – #54248
  • Update documentation for the date_query_valid_columns filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. – #54248 – #53550

Embeds

  • Add Wolfram Notebook as a trusted oEmbed provider – #53326

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

  • Add safeguard for invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. return from get_attached_file() in wp_delete_attachment() – #52241
  • Fix autovivification deprecation notice in recurse_dirsize() – #53635
  • Fix infinite 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. on Windows for clean_dirsize_cache() – #52241

Internationalization

  • Add context for some Media Library filter strings: – #54238

Media

  • Display the unsaved changes dialog in image edit form using jQuery .text() function – #54232

REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.

  • Add text-field and textarea-field as available schema formats for string sanitization – #49960
  • Correct the order of the parameters documented for WP_REST_Server::respond_to_request() – #53399

Props

Thanks to the 30 people who contributed to WordPress Core on Trac last week: @jrf (6), @audrasjb (4), @hellofromTonya (3), @jdy68 (2), @peterwilsoncc (2), @ocean90 (2), @mukesh27 (2), @johnjamesjacoby (2), @dimadin (2), @SergeyBiryukov (2), @TimothyBlynJacobs (1), @costdev (1), @sebastienserre (1), @janthiel (1), @isabel_brison (1), @desrosj (1), @josephdickson (1), @ekojr (1), @joegasper (1), @bartoszgrzesik (1), @teachlynx (1), @drosmog (1), @sjlevy (1), @codezen8 (1), @sergeybiryukov (1), @raubvogel (1), @dingo_d (1), @sabbirshouvo (1), @sabernhardt (1), and @justinahinon (1).

Congrats and welcome to our 7 new contributors of the week: @ekojr, @joegasper, @bartoszgrzesik, @teachlynx, @drosmog, @sjlevy, and @codezen8 ♥️

Core committers: @hellofromtonya (7), @sergeybiryukov (7), @johnbillion (1), @pento (1), and @rachelbaker (1).

#5-8-2, #5-9, #core, #week-in-core

Jb Audras 3:00 pm on October 18, 2021
Tags: ,   

Bug Scrub Schedule for 5.9

With 5.9 well underway, we’re ready to schedule the 5.9 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 sessions. These 5.9 specific ticketticket Created for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.

Alpha Scrubs:

Hosted by @audrasjb

Hosted by @chaion07 (APAC-friendly)

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. Scrubs:

Focus: issues reported from the previous beta.

RC Scrubs:

Focus: issues reported from the previous RC

Check this schedule often, as it will change to reflect the latest information.

What about recurring component scrubs and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions?

The above 5.9 scheduled bug scrubs are separate and in addition.

For your reference, here are some of the recurring sessions:

  • Twenty Twenty-Two Triage: Every Monday 15:00 UTC in the #core-themes channel.
  • 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/ Design Triage: Every Tuesday 16:00 UTC in the #design channel.
  • 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) Scrub: Every Friday 15:00 UTC in the #accessibility channel.
  • Testing Scrub: Every Friday 13:15 UTC in the #core-test channel.
  • CSSCSS Cascading Style Sheets. Scrub: First Thursday of every month 20:00 UTC in the #core-css channel.
  • Upgrade/Install Component: Every Tuesday at 17:00 UTC in the #core-auto-update channel.
  • Help/About Component: Every Monday, 19:00 UTC in the #core channel.

Want to lead a bug scrub?

Did you know that anyone can lead a bug scrub at anytime? Yes, you can!

How? 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.” @audrasjb or @chaion07 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/. and let us know the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 5.9-focused? Awesome! We’ll add it to the schedule here. You’ll get well deserved props in the weekly Dev Chat, as well as in the #props Slack channel!

Where can you find tickets to scrub?

  • Report 5 provides a list of all open 5.9 tickets:
    • Use this list to focus on highest priority tickets first.
    • Use this list to focus on tickets that haven’t received love in a while.
  • Report 6 provides a list of open 5.9 tickets ordered by workflow.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Questions?

Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to @audrasjb or @chaion07 on slack.

Thanks @jeffpaul for proof-reading.

#5-9, #bug-scrub