Dev Chat agenda, January 31, 2024

The next WordPress Developers Chat will take place on Wednesday January 31, 2024 at 20:00 GMT in the core channel on Make WordPress Slack.

Announcements

WordPress 6.4.3, security and maintenance release, went live on January 30, 2024. It features 5 bug fixes on Core16 bug fixes for the Block Editor, and 2 security fixes.

Post dev chat: What’s new in Gutenberg 17.6 published.

Discussions

These will focus on open proposals in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and release items.

This week will provide a discussion opportunity during Dev Chat to explore this open core proposal relating to major release Field Guides.

Proposed for next week’s Dev Chat a look at the just published proposal: What’s next for the FSE outreach program.

  • This post recommends what could be next. One suggestion is to rename the channel as ‘outreach’ and use it in a wider way to reach site builders and extenders. Another use of this channel could be to assist several projects which could use 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/. support in the WordPress space for discussion, clarification, and overall ruminating on future features coming to WordPress. 
  • Timescales:
    • Feedback deadline: February 12, 2024.
    • A Hallway Hangout is scheduled on February 20, 2024, at 15:00 UTC to further discuss this proposal, the comments, and the next steps.

Could you help curate a Call for Volunteers to review the open proposals on Make/Core and create a list of unresolved ones to discuss during Dev Chat meetings?

Highlighted posts

Dev Chat summary from January 22, 2024. Props to @webcommsat and @ironprogrammer for running the meeting and summary.

A Week in Core – January 29, 2024 – props to @audrasjb for pulling this together.

Changes on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between January 22 and January 29, 2024:

  • 48 commits
  • 64 contributors
  • 60 tickets created
  • 4 tickets reopened
  • 67 tickets closed
  • welcome to two new contributors to core this last week

Core-editor updates

Props to @annezazu for collating and sharing this list.

  • Design draft shared for the highlight grid for 6.5.
  • Section Styling: this work has been punted due to some blockers in resolving CSSCSS Cascading Style Sheets. specificity questions.
  • Font Library: biggest work continues to be the Font Library: refactor REST API which was merged into Gutenberg following this merge criteria for this feature and had a quick PR to follow up on feedback. Outside of that, a discussion is underway around making the font library more discoverable.
  • Pattern overrides: there are some current questions around how this features ties to the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Renaming 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. and how the internal block ids are generated and used. Right now, we can find the block names through block ids, but we cannot do the same the other way around.
  • Data Views: a recap of what’s planned and stable for 6.5 has been shared along with a PR to add sync status by default for Patterns, matching the current experience.
  • Link Control: A bigger PR was merged for Implementing new UX for invoking rich text Link UI by requiring explicit activation before displaying the Link UIUI User interface interface.
  • Block Bindings: the experimental flag was removed along with an outline of next steps for Gutenberg RC, Beta, and what’s out of scope for 6.5 (including when to backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch.). For out of scope, this includes a UI for users to add bindings. A ~4 min video walks you through the current status in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.!

General updates

An issue was opened for Media workflows around patterns that any media minded folks will find interesting. 

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

Any updates, 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 list or updates on 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?

Beta 1 for WordPress 6.5 scheduled for February 13, 2024.

Reminder: Proposed Phase 3 media library planning meeting will take place on Thursday, 8 February 2024 at 00:00 GMT in the #core-media
channel. 

Existing 6.5 links

Latest 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.4.3

WordPress 6.4.3 is now live.

Tickets to highlight for assistance

Tickets for 6.5 will be prioritized.

Open floor

#agenda, #core, #dev-chat

Performance Chat Agenda: 30 January 2024

Here is the agenda for this week’s performance team meeting scheduled for Jan 30, 2024 at 16:00 UTC. If you have any topics you’d like to add to this agenda, please add them in the comments below.


This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Dev Chat agenda, January 24, 2024

(Update from new Contributor Meeting added)

The next WordPress Developers Chat will take place on Wednesday, 17 January 2024 at 20:00 GMT in the core channel on Make WordPress Slack.

Discussions

These will focus on open proposals in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and release items.

  • Interactivity API and building interactive blocks has moved past the proposal stage and is aimed at being a key feature planned for 6.5. Now that it’s near complete and planned for 6.5:
    • is there anything actionable in the proposal?
    • or is it considered done / closed?

Next week’s dev chat, a discussion opportunity is identified for this open proposal on core relating to major release Field Guides.

Could you help curate a Call for Volunteers to review the open proposals on Make/Core and create a list of unresolved ones to discuss during Dev Chat meetings?

Highlighted posts

Summary from the experimental new style Dev Chat from January 17, 2024@webcommsat and @hellofromtonya

A Week in Core – January 24, 2024 – props to @audrasjb for creating this.

On TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between January 15 and January 22, 2024:

  • 35 commits
  • 62 contributors
  • 67 tickets created
  • 10 tickets reopened
  • 72 tickets closed
  • and a welcome to three new contributors

Performance team roadmap for 2024 is out and covers priorities.

Team reps update. The nomination period has been extended for the Core Team Reps 2024 edition to Wednesday, 31 January 2024 at 23:59 GMT. Full details are on the original nominations post where nominations can be added.

New core contributor meeting – if you were not able to attend and would like to find out more, check out the link to the meeting in Slack on January 24, 2024 which includes useful information on getting started and the contributor mentorship program. The deadline for applications for the second cohort for the program is Wednesday, February 7, 2024.

Core-editor updates

Core Editor Improvement: Robust Revisions in the Site Editor.

Props to @annezazu for sharing this list.

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

Any other updates?

Phase 3 media library meeting will take place on Thursday, 8 February 2024 at 00:00 GMT in the #core-media
channel. The Media Component team is coordinating a meeting with the Editor team and other interested stakeholders to work on planning for the proposed Phase 3 Media Library.

Core-editor improvement – revisions in the site editor. This is a useful post for understanding some of the changes and new features to current revision functionality in the Site Editor aimed for 6.5 and the wider work in this area. 

WordPress 6.5 release squad formation as at January 18, 2024. Additional discussion on size of the squad can be found in the comments on this post.

Important milestones in the Editor for 6.5 – useful post for contributors working or wishing to support the 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/ repository with the scheduled 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 for WordPress 6.5 scheduled for February 13, 2024.

Existing 6.5 links

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

Any other updates?

Earlier today there were four open tickets – update in 6.4 release leads channel.

Tickets to highlight for assistance

Tickets for 6.5 and 6.4.3 will be prioritized.

Open floor

#6-4, #6-5, #agenda, #dev-chat

Performance Chat Agenda: 23 January 2024

Here is the agenda for this week’s performance team meeting scheduled for Jan 23, 2024 at 16:00 UTC. If you have any topics you’d like to add to this agenda, please add them in the comments below.


This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Phase 3 Media Meeting: February 7, 2024

Date and time: February 7, 2024 at 24:00 UTC
Location: #core-media
Duration: 1:00 hr

The Media Component team is coordinating a meeting with the Editor team and other interested stakeholders to work on planning for the proposed Phase 3 Media Library. There are a few issues already open about the Media Library proposal, but this major development depends on close coordination between the Media and Editor teams to work effectively together.

In a recent Media Component meeting it was suggested that there should be a dedicated meeting time to kick off a round table discussion about some of the opportunities and challenges ahead in the development of Phase 3. The Media Component Maintainers hope to find areas of focus where contributors can lean in to align efforts with folks working on Phase 3.

In previous meetings the team has gone through the backlog of over 600 issues and categorized tickets as phase-3-media-triage for discussion around how Phase 3 could potentially solve these tickets alongside a rebuild of the Media Library. Some of these tickets are an opportunity to change lower level issues like db structure, but the redesign is a good time to address these possibilities.

Relevant Pull Requests, Issues, and Posts:

Phase 3: Collaboration > Media Library

PR Dataview: media view

Proposed meeting agenda:

  1. Introductions
  2. Brief presentation on the goals and vision of Phase 3 redesign for the Media Library
  3. Discussion on alignment of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Media focus to help the process
  4. Agree on communication channels and checkpoints for regular updates
  5. Review of Phase-3-Triage Tickets

A more detailed agenda will be published prior to the meeting.

If you would like to join this meeting please join the #core-media channel February 7, 2024 at 24:00 UTC. This time seems to align with most of the world as a decent hour to meet for stakeholders and folks active in Media.


This meeting happens in the #core-media channel. To join the meeting, you’ll need an account on the Make WordPress Slack. Props @joedolson for helping prepare and proofread this post.

#agenda, #media, #media-library, #meeting, #phase-3

Dev Chat Agenda, January 16, 2024

The next WordPress Developers Chat will take place on Wednesday January 17, 2024 at 20:00 UTC in the core channel on Make WordPress Slack.

Dev Chat evolving

Using the weekly curated agenda post for live and asynchronous usage, this meeting will begin an experiment to dedicate time to current proposals in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and to help specifically with progressing releases.

  • Through the summaries of the discussions and 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/. links, those unable to join live, will continue to be able to read and contribute asynchronously.
  • The links in the various agenda sections below will not be shared in full in the meeting, but be available for pre and post-reading. Anything for particular discussion can still be highlighted.
  • If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this post.

Discussions

These are some of the current proposals in core for awareness and which may be suitable for further discussion in Dev Chats.

  • Proposal: Default Theme Task Force for 2024
    •  This focuses on considering how the team approaches the maintenance of the default themes to make them easier to maintain, and more future-compatible. With the release of Twenty Twenty-Four, there are now 14 default themes maintained by the project.
  • Proposal: improve the editor tech workflow for major releases
    • This proposal is focused on a workflow for merging 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/ into Core
    • This could be an ideal time to discuss to discuss and experiment based on 6.4 learnings for the benefit of 6.5.
    • As Dev Chat now has a combined input from the Gutenberg and Core meetings, there is opportunity for discussing this further during the meetings and for a deeper discussion on what could be done in 6.5.
  • Interactivity API and building interactive blocks has moved past the proposal stage and is aimed at being a key feature planned for 6.5. An update has been requested to share with Dev Chat.

Could you help curate a Call for Volunteers to review the open proposals on Make/Core and create a list of unresolved ones to discuss during Dev Chat meetings?

Announcements

6.4.3 – next maintenance release – the post includes the planned schedule, the dates of the 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. scrubs, and the final release date of 30 January 2024.

Highlighted posts for information

These will not be re-shared in full in the meeting itself to enable time for discussions in a new experimental approach to Dev Chat.

Dev Chat Summary from January 10, 2024.

New versions for the default themes for the Twenty Twenty-OneTwenty Twenty, and Twenty Seventeen are now available for download. 

A Year In Core: 2023 – just a few highlights from this detailed post. Props to @sabernhardt and @audrasjb.

  • In 2023, the WordPress Core team shipped 2211 commits (2597 in 2022). 2751 tickets were opened, 2545 tickets were closed, and 365 were reopened.
  • Also, 1079 people contributed to WordPress source code using TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. (988 in 2022), and 472 people made their very first contribution to WordPress Core (398 in 2022).

A Week in Core – January 15, 2024 – props to @audrasjb. On Trac, between January 8 and January 15, 2024:

  • 37 commits
  • 64 contributors
  • 51 tickets created
  • 6 tickets reopened
  • 58 tickets closed
  • 8 new contributors to core!

Team reps update. The nomination period has been extended for the Core Team Reps 2024 edition to January 31, 2024 at 23:59 UTC . Full details are on the original nominations post where nominations can be added.

Call for mentors/ mentees for Contributor Mentorship program’s second cohort – deadline for applications, February 12, 2024

The Feature Projects page has had an update and worth checking out for the latest statuses. Feature Projects are intended to concentrate a group of people together, to explore potential ideas for WordPress Core.

Data Liberation in 2024 

What’s new for developers? (January 2024) on the Dev Blogblog (versus network, site).

Core-editor updates

Thanks to @annezazu.

For information

  • New tracking issue: Section Styling, Colorways, and Typesets for WP 6.5.
  • Font Library: biggest work for now is the Font Library: refactor REST API which needs feedback. Please help review if you have experience with the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/..
  • Pattern overrides: work is ready to test starting with making paragraph blocks overrideable. Up next, headings, buttons and images are expected to be added soon as blocks that can have overrides.
  • Navigation: customize the navigation overlay with a template part, enabling a separate menu experience for mobile, has been punted from 6.5 by contributors.
  • Design tools: PR merged to add backgroundSize feature with implicit repeating backgrounds to add more functionality to the Group blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.’s background image support that was added in 6.4. Needs PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher backports.
  • Data Views: Templates is now stabilized with Pages, Patterns, and additional views in Templates added in as experimental. Questions around extensibility came up recently — extensibility is very much part of the plan with the focus currently being on stabilizing the base APIs.
  • Add appearance tools support for classic themes: this work has been completed and merged into Core trunk. This opens a world of design options that, up until this point, have been only available with Block Themes, or themes using 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..
  • Interactivity 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.work continues for a public launch with 6.5 including a recently merged PR to render the root interactive blocks in Server Directives Processing.
  • Block bindings API: block bindings prototype is being split into smaller PRs to move work forward in smaller chunks with the PR that sets the basis for the API recently merged (this doesn’t add a UIUI User interface to create the bindings).

New (thanks to @bph)

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

Please also view the updates relating to 6.5 related updates under the core-editor heading above.

A release squad announcement is expected shortly.
Next milestone: 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 Feb 13, 2024.

New links on 6.5 since last week:

Recording of hallway hangout: Let’s explore 6.5

Early opportunities to test WordPress 6.5

Note update on the Font Library API design proposal with a particular note for REST API folks to view as per this comment. The navigation overlay has been punted from the 6.5 roadmap by the contributors working on this feature.

Any other updates on the Font Library?

Could you help with running a bug scrub around a particular area, component, or towards 6.5? More information on running scrubs. More dates for 6.5 bug scrubs will also be added once a squad is in place.

Existing 6.5 links

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

  • As shared above in Highlighted Posts, the next maintenance release will be 6.4.3.
  • Milestone: RC1 January 25, 2024
  • Release slated for: January 30, 2024
  • Bug scrubs and more information is in the link above.
  • 6.4-release-leads channel on Slack

Gutenberg releases

17.5 can be downloaded from the Gutenberg plugins page.

Update: A “What’s new in Gutenberg 17.5” has been published – thanks @scruffian and everyone who worked on 17.5.

Tickets to highlight for assistance

Priority will be given to tickets relating to 6.5.

Open floor

You can post suggestions in the comments box. Please indicate if you are intending to be at the meeting for any queries.

Thanks to @hellofromtonya for discussion on the core proposals lists and @annezazu for sharing the core-editor updates.


#agenda, #core, #dev-chat

Performance Chat Agenda: 16 January 2024

Here is the agenda for this week’s performance team meeting scheduled for Jan 16, 2024 at 16:00 UTC. If you have any topics you’d like to add to this agenda, please add them in the comments below.

  • Announcements
    • Welcome to our new members of #core-performance
    • Performance Lab 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 release today for version 2.8.0
  • Priority projects
  • Open floor

This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Dev Chat agenda, January 10, 2024

The agenda for the first dev chat after the seasonal break is below. The meeting takes place on 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/. on January 10, 2024 at 20:00 UTC .

(Update: 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/ testing requests have been added under the Releases heading.)

Welcome and housekeeping

All welcome.

Announcements

What’s new in Gutenberg 17.4

Reminder: call for volunteers for 2024 major releases.

Highlighted Posts

Posts during the break were highlighted in the following post. Many of the items in that post are still relevant, including a reminder that the core 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. nomination period had been extended until January 12, 2024 at 23:59 UTC, to give more time for Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. to consider and nominate other contributors and/or themselves. Nominations post for 2024 core team reps.

In the last few days, there have been the following new posts:

A Week in Core – Jan 8, 2023 – big thanks to @audrasjb

On TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between January 1 and January 8, 2024:

  • 19 commits
  • 20 contributors
  • 26 tickets created
  • 2 tickets reopened
  • 21 tickets closed

Phase 3, agency outreach recap @s1m0nd on an outreach exercise to enterprise WordPress agencies specializing in enterprise projects, inviting them to a series of informal show-and-tell sessions.

Update from the Developer Blogblog (versus network, site)

New design is live.

What’s new for developers, December 2023.

Writers are invited for the following articles on the WordPress Developer Blog:

To volunteer or ask further queries, comment on the GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ tickets linked. If you need further assistance, post a message in the in the #core-dev-blog channel.


Core-editor update

Props to @annezazu for this update from January 2, 2024.

For information:

Release updates

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

Existing links:

Gutenberg updates

Thanks @bph for sharing.

  • Gutenberg plugin 17.5 RC1 is now available for testing
  • WordPress 6.5 Roadmap: a few features are already available in Gutenberg 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 and could use some testing and feedback (the links below are tracking issues)

Tickets for assistance

Tickets can be highlighted for this section of the agenda, priority will be given to 6.5 release items.

Open floor

#6-5, #agenda, #core-editor, #dev-chat

Performance Chat Agenda: 9 January 2024

Here is the agenda for this week’s performance team meeting scheduled for Jan 9, 2024 at 16:00 UTC. If you have any topics you’d like to add to this agenda, please add them in the comments below.


This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Performance Chat Agenda: 2 January 2024

Here is the agenda for this week’s performance team meeting scheduled for Jan 2, 2024 at 16:00 UTC. If you have any topics you’d like to add to this agenda, please add them in the comments below.


This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

#agenda, #meeting, #performance, #performance-chat