Sarah Norris 2:49 pm on August 8, 2024
Tags: , , ,   

Summary, Dev Chat, August 7, 2024

Start of the meeting 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/., facilitated by @joemcgill. 🔗 Agenda post.

Announcements

There were no announcements this week.

Forthcoming Releases

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

We are currently in the WordPress 6.7 release cycle. WordPress 6.7 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. 1 is scheduled for Tuesday, October 1.

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

The next maintenance release will be 6.6.2 and will likely be released at the end of the month, likely August 26 with RC1 the week before.

Next 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/ release: 19.0

Gutenberg 19.0 is scheduled for August 14. RC1 was released on August 7.

Discussion

@joemcgill led with this reminder:

WordCamp US is coming up on September 17–20, and @courane01 has begun requesting table leads from all the Make teams for 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/.. We can use some time to discuss this and answer any questions folks might have.

Open Floor

#53817 was raised in the agenda comments. We discussed that this issue should be opened in the Gutenberg repo instead of TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., which @hellofromtonya offered to handle.

Next, we discussed #51525. @mathieulamiotwpmedia described where the ticketticket Created for both bug reports and feature development on the bug tracker. was up to:

We are interested in this possible enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. for a while and we built a library that we currently use based on the ticket’s discussions. Having this directly in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. would open up a few possibilities to make apply_filters typing more resilient, but it was never really clear in the ticket discussion if such approach could make it to the Core at some point.

So, we suggest 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. based on the library we built, and it would be great to get feedbacks from Core maintainers. First, to know whether or not it’s worth pursuing the effort on this, from a WP Core perspective. And if yes, what could be next steps

The ticket itself is loaded with information and context, and the patch itself might not be easy to assess right here right now ; but I thought we could bring this up here to maybe follow-up on it asynchronously. That’s it, I guess!

We discussed whether this should be included in Core, how it could be used, or if it is intended as a shared 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. that plugins and themes would use.

Finally, @swissspidy mentioned this merge proposal for Preferred Languages that resulted in some good feedback, including:

  • Concerns that core starts consuming GB packages outside of the editor
  • Tooling limitations in core (no TypeScript, no ESLint, no Jest tests)
  • Concerns about adding TypeScript to core (implications for build server etc.)
  • Need to have performance tests with fallback chain as well

@swissspidy will publish a new make/core post following this feedback.

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Props to @joemcgill for proofreading.

#6-7, #core, #dev-chat, #summary