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 bug scrub sessions. These 5.9 specific ticket scrubs will happen each week until the final release.

Alpha Scrubs:

Hosted by @audrasjb

Hosted by @chaion07 (APAC-friendly)

Beta 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 triage 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.
  • Gutenberg Design Triage: Every Tuesday 16:00 UTC in the #design channel.
  • Accessibility Scrub: Every Friday 15:00 UTC in the #accessibility channel.
  • Testing Scrub: Every Friday 13:15 UTC in the #core-test channel.
  • CSS 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? Ping @audrasjb or @chaion07 on slack 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 core 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

Francesca Marano 11:58 am on October 26, 2021
Tags:   

Nominations for Core Team Reps 2022

This post kicks off the election process with nominations to replace @audrasjb and @francina as Core team reps. We have been in the role for over a year now, so 2022 marks the time to get new folks!

The Role

In the WordPress open source project, each team has on average one or two representatives, abbreviated as reps. 

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, it’s at least two hours a week.

Here are the main tasks:

Full details on the Team Rep role is on the Team Update site.

How the election works

Please nominate people in the comments of this post. Self-nominations are welcome. The deadline is 10 November 2021.

After that, a poll will be opened for voting. It will stay open for about two weeks. The new reps will start their role on January 1st, 2022.

If you want to nominate someone in private, please reach out to @francina or @audrasjb on Slack.

Disclaimer: if you get nominated, please don’t feel like you have to say yes. The polls will only include the names of the people that are responding positively to a nomination.  So feel free to reply with a “Thank you, but no thank you”.

If you have any questions, please feel free to ask in the comments, we will be happy to reply.

Thanks to @audrasjb for the peer review.

#team-reps

Robert Anderson 11:54 pm on October 25, 2021
Tags: ,   

WordPress 5.9 Editor Update – 26 October

Gutenberg 11.9 (the last plugin release which will make its way into WP 5.9) will be cut on November 3 which is in 9 days!

The merge to Core for this release will be tricky. I’m seeking volunteers to assist with the patch. Let me know if you can help.

@mamaduka has ran an audit of our __experimental APIs. Please give it a look over.

I asked around to identity what the “must have” enhancements are for this release and have added them to the WordPress 5.9 Must-Haves project board. Please regularly check in with this project board. There are a bunch of bugs in the board, too, and you should also pay attention to them, but they’re slightly less important because bugs can be addressed after the feature freeze.

Here’s a overview of the “must have” enhancements:

🤙

#core-editor #5-9

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 Core. Let’s take a look at what changed on Trac 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 🚀

Ticket 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 Slack 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 Slack.

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.

Gutenberg plugin 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 Block 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 release 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 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.

CSS 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 blog 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 core committers of the week, too.

A Week in Core – October 18, 2021

Upcoming releases updates

Next minor release(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 Slack 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 ticket to a resolution!

Next major release

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 bug 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 (i18n) – @sergeybiryukov

Some Media Library filter 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 07:00 PM 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 patch 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 block 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 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 Wednesday, October 20, 2021 at 08:00 PM UTC.

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

Blog 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 Core 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 Slack.

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