Dev Chat summary, August 3, 2022

@marybaum led the chat (transcript) on this agenda.

For more background, here’s the July 27 summary.

1. Welcome

To reiterate, if you come to devchat, that’s a compliment to the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, and you are not only welcome but the main reason the chat runs when and where it does. In open-source development, every part of the software and its processes are for you. So do say hey with an emoji when you’re in the house!

2. Announcements

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/ 13.8 landed moments into the chat.

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

A module proposal on GitHub.

A week in Core.

Moving Core block styling to theme.json.

Giving FSE a more user-friendly name.

An update on the new design for the .org home and download pages.

4. Upcoming releases

The next major is 6.1.

@costdev asked the group for tickets pending a formal 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 schedule. @presskopp suggested #16838, and a brief discussion followed.

The next minor is 6.0.2.

5. Open Floor

@hellofromtonya, asking for @zieladam, pointed the group’s attention to this proposal for a canonical HTML-processing API.

#core, #dev-chat, #summary

Dev chat agenda, July 27, 2022

1. Welcome

Last week’s summary.

To continue a theme: devchat is not just for release squads or project leaders, or coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers and component maintainers. Did you know that when you sign up for a 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/. account, the first channel you join, by default, is the Core channel?

That should tell you: devchat is for everyone who has any interest in the WordPress project—which means you. And when you give your valuable time to join the meeting, that’s a pretty big compliment to the people who are there too. So if you typically come as an observer, let the group know you value that hour in the day enough to spend it with them. And say hey, with a hand-wave or some other emoji.

2. Announcements

Details on WordPress 6.1 are out!

If you have an announcement, please add it to the comments. Or show up to the chat, and you can share it live. Preferably, do both!

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

@audrasjb reports in with A week in Core.

Core Editor improvement: deeper customization with more template options, from @greenshady

@critterverse proposes A new kind of default theme.

@pbearne proposes adding a dominant color background for images.

@bacoords would like feedback on this Proof of concept: feature notifications.

And in case you missed it last week, @bph shares what’s new in Gutenberg 13.7.

4. Upcoming releases

The next major is 6.1: squad and schedule have landed! (Reprise)

@annezazu has made some suggestions for the Major Releases Handbook page. There’s a Google Doc where you can help out, in comment mode.

The next minor is 6.0.2.

5. Open Floor

Component maintainers get priority, then early tickets.

After that, the floor is yours! Just add your item to the comments, and the cohosts will recognize you.

See you at the chat!

#agenda, #core, #dev-chat

Dev Chat summary, July 20, 2022

@marybaum and @webcommsat led the meeting on this agenda.

1. Welcome

@marybaum welcomed the group and encouraged everyone who shows up for the chat to say hello with an emoji.

Devchat is not just for lead developers, coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers or other so-called special people; like everything else that happens in WordPress, devchat is for everyone. Which means you. So when you come around, say hey and let the group know you’re in the house!

2. Announcements

@webcommsat opened the floor for announcements, and @bph noted that Gutenberg 13.7 was landing at that very moment.

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

A Week in Core from @audrasjb. JB publishes this report every Monday.

@bph pointed out that comments were due that day on her post about the new developer blog.

4. Upcoming releases

The next major is 6.1.

@marybaum and @desrosj spent a few minutes going over what usually happens at the beginning of the formal part of a release cycle, and when those things might start for 6.1. Bottom line: fairly soon! With an expected launch date of October 25, 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. is likely to happen six to eight weeks before.

The next minor is 6.0.2.

Minor releases contain only 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. fixes and other maintenance code—no new features or enhancements. Their timing and execution depend utterly on the tickets in the milestone.

5. WCUS 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/.

@marybaum opened a discussion about planning Core tables for Contributor Day at WordCamp US. That day will be September 11, and several Core team folx will be on hand to lead activities.

Would you like to help plan? Let @marybaum, @adamsilverstein or @desrosj know by 23:00 UTC on Friday, July 22, and you’ll get access to a Google Doc that will become the basis for information that’s due to the WCUS Contributor team by July 29.

6. Open floor

@sergey and @webcommsat updated the participants on their respective components. @marybaum gave a shoutout to Help/About and Bulk/Quick Edit co-maintainer @nalininonstopnewsuk, who is back in action on several fronts after some time away. Welcome back, Nalini! You were sorely missed.

@azaozz slipped in at the very end to discuss tickets #55942 and #56199, which he’d very much like to see land in 6.1. He pointed out that #56199 will need some brainstorming and discussion before it can proceed.

Thanks to @webcommsat for meeting prep and cohosting.

#core, #dev-chat, #summary

Dev Chat agenda, July 20, 2022

Last week’s summary.

1. Welcome

Seriously. Devchat is NOT a meeting just for senior developers, or component maintainers, or champion coders, or people in leadership roles — though it is a good place to find people like that. Devchat is for anyone who cares about WordPress, whether you can write a line of code or not.

In short, Devchat is for you. So please say hello with an emoji — a waving hand 👋, or something that’s special for you. For example, @marybaum almost always joins a meeting with 🎾, and @sergeybiryukov signs in with a ❤️.

2. Announcements

If you have an announcement, make it here.

If you’d like to have someone at the meeting make it for you, leave it in the comments.

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

A Week in Core, from @audrasjb

Please list other posts in the comments.

4. Upcoming releases

The next major is 6.1.

The next minor is 6.0.2.

If you have an update for the group about either release, please plan to be at the chat. If participants have a question, and you are likely to have the answer, you may well get a 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.” asking if you’re in the house.

5. WCUS 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/.

What would you like to see at the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. contributor table? @marybaum has some thoughts. Let’s take a minute and talk about yours too!

6. Open floor

Component maintainers and early tickets get priority; after that, it’s up to you! If you leave your item in the comments, you will get time.

See you there!

#agenda, #dev-chat

Summary, Dev Chat, July 13, 2022

Start of the weekly WordPress developers chat 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/..

Agenda followed. Meeting led by @marybaum and @webcommsat

1. Welcome

All welcome to attend (Ed. note: yes, you!) and participate in this meeting. It happens weekly in the #Core channel at 20:00 UTC. You can also add updates or items for the meeting on the agenda published the day before.

Last week’s Dev Chat summary – meeting on July 6, 2022

2. Announcements

WordPress 6.0.1 release (July 12, 2022)

Gutenberg 13.6 release (July 7, 2022)

Gutenberg 13.7 RC (July 13, 2022)

3. Posts

Thanks to everyone who wrote or contributed to these posts.

3. Upcoming releases

  • 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. will be 6.1
  • 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. will be 6.0.2

Nothing was raised at the meeting.

If you have an update on progress towards forthcoming releases and can’t make the dev chat, you can add an update to the agenda or send it to one of the core team reps. They will share it in the meeting.

4. Open floor/ Help wanted

a) Component maintainers and tickets

We start with a check-in with contributors who help maintain the WordPress components. Find out more about the components, and you might find the perfect one for you to help maintain or be involved in resolving tickets. Chat to the core team reps if you are interested.
https://make.wordpress.org/core/components/

@afragen

@sergeybiryukov

  • Build/Test Tools: An effort on adding missing @covers tags for WordPress unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. suite has continued. More details on ticket #39265 for more details.
  • 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 

@ndiego

  • Ticket #56112: Allow remote pattern registration in 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. when core patterns are disabled. This needs testing. This issue is related to an FSE adoption blockerblocker A bug which is so severe that it blocks a release.

@webcommsat

  • Quick/ Bulk Edit: Ticket #16502 needs testing – Quick Edit contents should only be rendered if quick edit button in actions after filtering. It is in the 6.1 milestone.
  • Help/ About: Thanks to @sabernhardt for reviewing Ticket #56210 on a page design spacing issue in Core and setting the milestone for 6.0.2.

No other component maintainer or updates.

b) Other

No other items raised.

The next dev chat will be Wednesday July 20, 2022, at 20:00 UTC. Hope to see you there!

Props to @marybaum and @webcommsat for preparing and leading the meeting,
to @webcommsat for writing the summary, and to @costdev and @marybaum for reviewing it.

#dev-chat, #summary

Dev chat agenda for July 13, 2022

The summary from last week—July 6, 2022.

1. Announcements

WordPress 6.0.1 has landed!

As did, last week, Gutenberg 13.6!

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

A Week in Core

Recap of WordPress 6.0 retrospective feedback

Contributor Teams for WCUS 2022

WordPress packages publish to npm every two weeks

Proposed editorial process for the new developer blog

The Month in WordPress post for June 2022

3. Upcoming releases

The next major is 6.1.

The next minor, if there is one, will be 6.0.2.

Again, congratulations and huzzahs to the (release-)party animals who landed 6.0.1!

4. Open floor

Component maintainers and folx with 6.1 early tickets have priority. After that, the floor is yours; please note your item in the comments, especially if you cannot join the chat and would like your friendly (global) neighborhood facilitator to raise it for you.

See you then!

#agenda, #core, #dev-chat

Dev chat summary, July 6, 2022

@marybaum led the chat on this agenda.

Announcements

WordPress 6.0.1 RC 1 has landed!

Blogblog (versus network, site) posts of note

A Week in Core, July 4, 2022, from @audrasjb

Proposal: Better REST API handling in JavaScript, from @zieladam (Needs feedback; would like it by July 18)

Planning for WebP and other image formats, from @adamsilverstein

Exploration: Improving DevHub, from @tellyworth

Performance Chat summary, July 5, 2022, from @shetheliving (Ed. note: There’s so much here! Your friendly 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. isn’t going to post the summary every week, but has an idea it might be a good idea for every CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. contributor to keep up with what’s happening over on the performance playing field.)

Upcoming releases

The next major is 6.1.

@desrosj pointed the group to @priethor‘s 6.1 planning roundup and suggested there’s still time to comment.

The next minor is 6.0.1.

The 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). 1 landed on Tuesday; the final is slated for next week, on July 12. Please download and test!

#core, #dev-chat, #summary

Dev chat agenda, July 6, 2022

1. Welcome

Last week’s summary.

2. Announcements

WordPress 6.0.1 RC 1 has landed!

Got some announcements of your own? Please add them in the comments, or let @marybaum or @audrasjb know before the meeting.

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

A Week in Core, July 4, 2022, from @audrasjb

Proposal: Better REST API handling in JavaScript, from @zieladam (Needs feedback; would like it by July 18)

Planning for WebP and other image formats, from @adamsilverstein

Exploration: Improving DevHub, from @tellyworth

Performance Chat summary, July 5, 2022, from @shetheliving (Ed. note: There’s so much here! Your friendly 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. isn’t going to post the summary every week, but has an idea it might be a good idea for every CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. contributor to keep up with what’s happening over on the performance playing field.)

4. Upcoming releases

The next major is WordPress 6.1.

Need help with something? Got something to report in on? This is your time>

The next minor is WordPress 6.0.1.

WordPress 6.0.1 RC 1 has landed! Look for the final to land July 12, barring all the usual caveats.

5. Open Floor

Tickets and components have priority, then the floor is yours.

Please list your item in the comments, especially if you are not able to join the chat in real time.

See you at devchat!

#agenda, #core, #dev-chat

Dev chat summary, June 29, 2022

@marybaum led the meeting on this agenda.

For your records, last week’s summary came from @chanthaboune.

Announcements

@craigfrancis gave a big shoutout to the folx who helped him on tickey #52506, which will likely be ready to land in 6.1. (TL;dr it’s a much-needed database-access improvement).

Blogblog (versus network, site) posts of note

A Week in Core from @audrasjb

A call for testing from @afragen

And two reposts from @chanthaboune‘s summary:

There’s a discussion about how to update the wp-admin experience.

There’s a discussion on Yoda conditions (which started in the WPCS repo)

Upcoming releases

The next major is 6.1.

@bph shared @priethor‘s 6.1 planning roundup. Leave a comment there if you’d like to volunteer!

Birgit also shared this report. The current schedule, which is not confirmed, shows feature freeze is September 20, roughly eleven weeks from now.

There was some discussion.

The next minor is 6.0.1.

Here’s the plan!

Open floor

@craigfrancis asked for eyes on #54042 (PR:2191).

@sergey reported on his components.

  • Build/test tools:
    • #55652 updates npm and other dependencies to their latest versions.
    • #39265 continues progress on adding missing `@covers` tags for the WordPress unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. suite.
  • General: #56009 and #56033 are starting the process of modernizing code to support PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.2.

    On those tickets, Sergey thanked @desrosj, @jrf, @azaozz, @pbearne, @hellofromtonya, @antonvlasenko, @ironprogrammer, and @costdev.

@sabernhardt announced that a special `good-first-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 will start today at 21:00 UTC, right after the usual weekly 6.1 scrub.

And @afragen would like help testing his feature plugin that’s all about plugin dependencies. More details are here.

#core, #dev-chat, #summary

Dev Chat Summary: June 22, 2022

@marybaum led the weekly meeting at 20:00 UTC. Here is the meeting agenda.

Link to 20:00 UTC <dev-chat> in #core on Making WordPress Slack
(bonus link to the new contributor chat at 19:00 UTC)

Notable News

Folks Need Feedback!

Release Updates

Component Updates

Build/Test Tools

  • Quite a few unit tests for image functions were modernized per the current best practices#55652
  • Xdebug modes are now configured in the local Docker environment. #56022
  • Changes to the code coverage workflow can now run on pull requests to be verified before being committed. #55652

Components that Checked in with “No Update”: 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., Menu, Widgets, Bulk Edit, About/Help

Watch For

  • WordPress 6.1 kick off and plans
  • WordPress 6.0.1 kick off and plans

Interested in volunteering for upcoming WordPress releasesPlease comment below!

#dev-chat, #summary