Dev Chat Summary, April 20, 2022

Updates: new web link added to section 4 relating to the status of webfonts 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..

Notes from the weekly WordPress Developer Chat held in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel 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/..
Start of the meeting in Slack

1. Welcome

Interested in Core development? This is the meeting to join, and you are more than welcome. Add your posts and items for open floor to the published agenda, which goes out a day ahead of the meeting.

Agenda for the meeting on April 20, 2022

Dev Chat summary, from the meeting on April 13, 2022

2. Announcements

a) WordPress Beta 2 landed on April 19. 2022. Please download and test! But do remember that this version of the WordPress software is under development. So you won’t want to test it on a production siteProduction Site A production site is a live site online meant to be viewed by your visitors, as opposed to a site that is staged for development or testing.. If you came to the release party, thanks very much for contributing your time and energy.

b) The speaker deadline for WordCamp US has been extended to April 25, 2022.

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

A Week in Core, from @audrasjb (April 18, 2022)

What’s New in Gutenberg 13.0 (April 14, 2022)

How you can help test 6.0

The deadline for feedback for the latest FSE program testing call is April 21, 2022. FSE Program Testing call #13: Authoring an Author template

4. Upcoming releases

4a. Next major: 6.0

6.0 Development Cycle

Update on behalf of the release squad by @annezazu:
A big thank you to everyone who continues to help make this release happen. It’s always felt really humbling to be a part of but, for some reason today, that feeling is very magnified. 
Updates:

  • all are welcome to join the 6.0 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. 3 Release Party at April 26 2022 at 16:00 UTC in the core channel on the Make WordPress Slack
  • The best way to help is to test — a rundown of how to do so.
  • Over the last week, tons of discussions and efforts have been thrown behind the Webfonts API effort. Everyone involved deserves big props. For clarity, this API is NOT in Beta 1 or 2. Expect a Make Core post in the coming days with a status update: the people with their hands in the code are looking at several pathways forward, including not having it in the release at all.
    Update: post on Status of webfonts API for WordPress 6.0 inclusion (published April 22, 2022)
  • A post is coming shortly around the various 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) improvements coming to 6.0. Stay tuned and get excited! (This was published after dev chat – Accessibility improvements in 6.0. Thanks to @joedolson, @alexstine and @annezazu for collaborating on this post.)
  • Other features related to the release are evolving as the beta process proceeds, including removing block edit locking from the reusable block (just the ability to lock the option to edit) and various decisions for the comments blocks work.

Update from @costdev relating to core triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.

Regarding 6.0 Core Triage, Beta 3 is on the horizon—that is also soft string freeze. Get your patches uploaded or refreshed and 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.” component maintainers, committers, the relevant teams (Copy/Marketing, Docs, Accessibility, CSSCSS Cascading Style Sheets., Test Team, etc) or feel free to ping him @costdev) here or on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress./GithubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ (same username) if you need some extra eyes on your ticketticket Created for both bug reports and feature development on the bug tracker./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.. Let’s land them in 6.0.

@webcommsat: You can still join the Bug Scrubs for 6.0 – dates are on the bug schedule.

Suggestion for a handbook page for contributors new to testing during a release party. @marybaum checked, and there is not a page already. Suggested one to add to a to-do list.

5. Open Floor

a) Blog – core team activity

@audrasjb: shared a blog post from a contributor @mte90, who put together some meaningful insights about core team activity. He also offered his analysis of the “ticket queue problem” and shared his thoughts on it. Suggestions for actionable items included:

  • Create a Mentor/Reviewer role, that has duty, but is able/skilled to review the patch or help the patch author to finish it, ready to be reviewed by Component Maintainers
  • Improve the Bug triage team with other people to have less tickets to be handled by Component maintainers (when a component is assigned)
  • During WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. at the core table get people working on triage, as developers/veterans are required

Discussion in dev chat about core tables at contributor events at WordCamps continuing to focus on triage, encouraging more camps to do these kind of events.

But Camps will also need experienced devs familiar with triage and able to help take tickets forward, so the goal is not just increasing the number of people involved in isolation.

@webcommsat: Contributor days or events can be standalone events too – there have been some really good examples run by a local or grouped WordPress communities where they have focused on tickets on a particular theme. It does not necessarily mean the tickets they focus on get looked at again on trac immediately or even soon. Firms can also run events in-house or hold regular sessions as part of Five for the Future too. There are lots of chats already happening in the wider community about these kinds of contributor events, and coming to teams with requests of what to focus on. WordCamp Europe Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. in June could be a good triage opportunity.

@costdev: Might be worth either having more regular scrubs or some mob triaging streams/similar to help get through a bunch of the older tickets, especially those that needs-testing and such. These scrubs can also work well to show new contributors how things work.

@audrasjb: We can definitely try some new things, like a “Triage Week event” once a year (better name welcome. In French, we have a word for that kind of “event”:“nettoyage de printemps” (“spring cleaning” or “spring-clean”.

b) Trac tickets

@jeffpaul: Highlighted Trac Ticket #55377 on the crop area display in CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. when cropping a large site logo. This is a recently opened defect looking for feedback on the potential approach before time is spent on a patch. @costdev to review; needs some checks against existing tickets/ a reproduction report and some other changes before looking at the approach.

c) Next meeting

Wednesday April 27, 2022 at 20:00 UTC

Can you help write the summary from dev chat next week? We are short on volunteers at the moment, and you can get help doing it. Contact core team reps @marybaum and @audrasjb.

Props to @marybaum and @webcommsat for facilitating dev chat, to @webcommsat for writing the summary, and to @marybaum, @annezazu and others for reviewing it.

#6-0, #dev-chat, #summary