Summary, Dev Chat, December 11, 2024

Announcements

There were no announcements today, but @mikachan posted a reminder that WordCamp Asia 2025 is looking for volunteers 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/., especially to lead CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./Core Editor/Core Performance tables. Please reach out to @Jhimross if you’d like to volunteer.

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

We are currently in the WordPress 6.8 release cycle. The call for volunteers for the 6.8 release squad closed on Dec 6 and the release squad will be put together soon based on these volunteers.

Next maintenance release: 6.7.2

There is currently no release date planned for WordPress 6.7.2. Review the next minor release milestone. @joemcgill agreed to follow up about another 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 before the end of the year.

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

The next Gutenberg release will be 19.9, scheduled for December 18. It will include the following issues.

Discussion

There were two topics for discussion today

• Any feedback or questions on the Consent API proposal
• An open discussion about WordPress and TypeScript

Consent 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. Proposal

@joemcgill noted that we’ve already gotten a lot of good feedback and asked @ironprogrammer how long we should leave the proposal open for comment.

@ironprogrammer:

“Given the coming holiday season, would it make sense to leave it open through the end of the year? The feedback has been really positive, but additional feedback from orgs/plugins working with consent would be valuable.”

@joemcgill:

If the consensus is that this should be a core feature, then ensuring the team who is going to shepherd this into a future release is properly supported would be key. Either way, I think there is value in considering the other question in the proposal—which is whether this should become a canonical 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 that is officially supported by the community. I think we can follow up with @4thhubbard about how we want to handle these kinds of requests as there really hasn’t been an established policy that I’m aware of.

@mikachan:

Through the end of the year sounds fine to me. We can make sure we follow-up (including in dev chats) towards the start of next year

WordPress and Typescript

@mikachan:

We adopted TypeScript in WordPress more than 3 years ago and our usage has evolved over time. It’s time to update our approach/guidelines. @youknowriad has opened a discussion to gather thoughts before publishing a P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs..

Next steps are to continue collecting feedback and revisiting in a future Dev Chat, if needed.

Open Floor

• @mamaduka asked for more eyes on #59425, which was recently reported in Gutenberg as well.
  • @joemcgill shared this in the #core-restapi channel.
• @jonsurrell shared this call for feedback on this PR for adding CSSCSS Cascading Style Sheets. selector-based tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) navigation to HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. and Tag Processors (#62653)
  • All feedback is welcome, but specifically, he’s looking for high-level feedback, especially from WordPress veterans. Does the implementation feel appropriate for WordPress? Are there things that are discouraged in Core?
• @joemcgill raised the need to prepare for nominations for Core Team Reps for 2025 and suggested publishing a call for nominations in the next week with the hopes of collecting responses in Jan and being able to do a transition by Feb. @mikachan and @joemcgill will take responsibility for following up on this.