Agenda, Dev Chat, Wednesday February 28, 2024

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

The live meeting will focus on the discussion of proposals and releases, updates on 6.5, and have an open floor section.

Additional items will be referred to in the various curated agenda sections, as below. 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 agenda.

Announcements

WordPress 6.5 Beta 3 was released on February 27, 2024. Thanks to everyone involved and who came to help test.

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

Updates from the release squad can be shared in the Dev Chat.

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: 17.8

Gutenberg 17.8 is scheduled for released today and will include the these issues.

Discussions

This week the discussion will focus on any final priority topics that need to be raised prior to 6.5 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.

Proposed topics

Feel free to suggest additional topics related to this release in the comments.

Highlighted posts

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor Updates

Props to @annezazu for collating and sharing this list.

Tickets for assistance

Tickets for 6.5 will be prioritized.
Please include detail of tickets / PR and the links into comments, and if you intend to be available during the meeting if there are any questions or will be async.

Open floor

Items for this can be shared in the comments.

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

Performance Chat Agenda: 27 February 2024

Here is the agenda for this week’s performance team meeting scheduled for Feb 27, 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

Agenda, Dev Chat, Wednesday February 21, 2024

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

The live meeting will focus on the discussion of proposals and releases, updates on 6.5, and have an open floor section.

Additional items will be referred to in the various curated agenda sections, as below. 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 agenda.

Announcements

WordPress 6.5 Beta 2 was released on February 20, 2024. Thanks to everyone involved and who came to help test.

Gutenberg 17.8 RC release is planned for today, stable release scheduled for Feb 28, 2024. Please help test.

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

Updates from the release squad can be shared in the Dev Chat.

Call to test 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. versions of the release as they come out.

Call for Testers early draft for 6.5. Discussion 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/. if you are able to help. Update – this is now closer to finalization and open for final comments.

Discussions

Check in on the experimental format we’ve been using for these meetings. has discussion on open proposals been effective? Are there topics that have not been covered that you’d like to see included?

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

A Week in Core – February 19, 2024 – props to @audrasjb

Hallway Hangout: Let’s chat about overlapping problems in the Site Editor

Merge Announcement: Interactivity API

Data Liberation Next Steps

Summary, Dev Chat, February 14, 2024

Merge Announcement: Plugin Dependencies

Tickets for assistance

Tickets for 6.5 will be prioritized.
Please include detail of tickets / PR and the links into comments, and if you intend to be available during the meeting if there are any questions or will be async.

Open floor

Items for this can be shared in the comments.

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

Agenda, Dev Chat, Wednesday February 14, 2024

(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/ 17.7 under announcements)


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

The live meeting will focus on the discussion of proposals and releases, updates on 6.5, and have an open floor section.

Additional items will be referred to in the various curated agenda sections, as below. 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 agenda.

Announcements

WordPress 6.5 Beta 1 was released on February 13, 2024. Thanks to everyone involved and who came to help test.

What’s new in Gutenberg 17.7

Discussions

Potential proposal for discussion at Dev Chat on February 14, 2024Proposal: Implement a PHP autoloader in WordPress Core.

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, February 7, 2024 – props to @webcommsat and @joemcgill

A Week in Core – February 12, 2024 – props to @audrasjb

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

  • 71 commits
  • 245 contributors
  • 82 tickets created
  • 11 tickets reopened
  • 82 tickets closed
  • 245 contributors during this period and 28 new contributors!

Core editor improvements post. This post highlights some of the power of details in 6.5 which can transform current workflows.

For the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor side, @annezazu has called out the Gutenberg issue 58773.

Improving block development documentation

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

Updates from the release squad can be shared in the Dev Chat.

Call to test 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. versions of the release as they come out.

Call for Testers early draft for 6.5. Discussion 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/. if you are able to help. Update – this is now closer to finalization and open for final comments.

Tickets for assistance

Tickets for 6.5 will be prioritized.
Please include detail of tickets / PR and the links into comments, and if you intend to be available during the meeting if there are any questions or will be async.

Open floor

Items for this can be shared in the comments.

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

Performance Chat Agenda: 13 February 2024

Here is the agenda for this week’s performance team meeting scheduled for Feb 13, 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
    • Release 2.9.0 of the 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 is scheduled for Monday February 19
    • Call for opinions on the naming of the ‘Image Loading Optimizations’ plugin [see here]
  • 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, Wednesday February 7, 2024

(Updated with 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 dependencies feature discussion request)

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

The live meeting will focus on the discussion of proposals and releases, updates on 6.5, and have an open floor section. Additional items will be referred to in the various curated agenda sections. 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.

Quick links to agenda sections

Announcements

Welcome to the two team reps for the remainder of 2024: Joe McGill (@joemcgill) and Sarah Norris (@mikachan)! With the increasing collaborative approach between coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and core-editor, it is wonderful to have reps from both parts of the team. A post formally introducing them will be published later this month.

@hellofromtonya and @webcommsat are doing a handover, and Abha (@abhanonstopnewsuk 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/. to 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.) with any updates) will continue to curate the agenda until Sarah is back on February 21.

Discussions on open core proposals and releases

As advertised last week, this week’s Dev Chat will explore the recently published proposal: What’s next for the FSE outreach program.

  • This post recommends next steps, including a rename of the channel as ‘outreach’ to use it more widely to reach site builders and extenders. It could also be used to assist several projects which could use Slack 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.

Potential proposal for discussion at Dev Chat on February 14, 2024: Proposal: Implement a PHP autoloader in WordPress Core.

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

Phase 3 media meeting agenda – this is scheduled for Thursday, 8 February 2024 at 00:00 GMT in the core-media channel on Make WordPress Slack

A Week in Core – February 5, 2024 – props 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 29 and February 5, 2024, there were.

  • 66 commits
  • 117 contributors
  • 79 tickets created
  • 8 tickets reopened
  • 56 tickets closed
  • welcome to 25 new 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. in core

New commit message requirements in Git and a Hello props Bot. Thanks to everyone who has worked on this historically and who have brought this to its latest update.

Proposal: Implement a PHP autoloader in WordPress Core. This updates the historic work on this and a proposed implementation.

6.5 release parties schedule and host

Core-editor updates

Props to @annezazu for collating and sharing this list.

  • 17.7 RC1 is set to be released this week, marking the last 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/ version to make it into 6.5.
  • Designs are continuing for the highlight grid for 6.5.
  • New marketing related issues opened for the 6.5 micrositevideo featurettes, and social media assets.
  • Font Library: work continues to merge the Font Library 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. redesign and a quick change was made to make the Font Library more discoverable, with the need for more feedback as 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 lands.
  • Pattern overrides: a PR is underway to add the block name to the pattern content data to help support future features, like shuffling patterns that are within the same categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. and a larger effort is underway to tighten up the accessibility of these non-editable bound fields.
  • Data Views: a primary filter API was added to enable set filters exposed by default in the interface for both pages (showing status) and patterns (showing sync status).
  • Link Control: work is underway to try to get in a PR that adds a “add block” UI for the navigation block link UI to help resolve feedback around how hard it is to add blocks to navigation.
  • 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. Bindings: after lots of discussions in slack, block bindings is moving forward to support custom fields and the ability to override blocks in synced patterns. The project as a whole is very open to feedback from extenders to see what can be added in the future.
  • Interactivity API/Block effects (name is in flux): the PR to officially launch this new API is very close to landing (core reviews welcome! thank you to those who have reviewed).

Developer Blogblog (versus network, site) update

Developer Blog summary, February 1, 2024 – this includes recently published posts. The following topics still need a writer:

If you are interested in taking on a topic from this list or know someone who would be a good person to writer about them, comment on the issue or in the #core-dev-blog channel.

Forthcoming 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

Updates from the release squad can be shared in the Dev Chat. In addition, there are also the following updates identified and discussed in Slack.

6.5 release updates

  1. The first draft of the Beta 1 announcement is ready for review. Please share your feedback by February 8, 13:00 UTC.
  2. For anyone following on in the 6.5 release leads channel, the latest async updates from the various areas starts at this Slack message.
    • This includes an update on the monitoring of a performance regression, which is being addressed.
    • A final decision is needed on a design concept for the feature tiles.
  3. Discussion on Patterns in Classic Themes feature and reviews to help progress this area. Update 16:06 UTC, Feb 7: this is regarded as resolved. Thank you for all those who were involved.

4. Call for Testers early draft for 6.5. Publication date is just before Beta 1. Discussion on Slack if you are able to help.

5. Next general 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 for 6.5:

Discussion on Plugin dependencies feature

You can also view discussions taking place in #core-upgrade-install channel on Slack. This has been highlighted as a potentially very valuable feature for 6.5 and was merged into ‘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.’ on Tuesday. Note this is the last dev chat before Beta 1.

Tickets to highlight for assistance

Tickets for 6.5 will be prioritized. Tickets can be referenced in the comments section of this agenda if you are unable to make the meeting and for asynchronous involvement.

Open floor

Raising awareness and amplifying the new core contributor sessions – the ticket is on the Marketing Team GitHub. It picks up a discussion in the sessions and from recent contributor days.

  • Action: comment on the ticket for any support you may be able to offer or if you can identify opportunities to amplify awareness of the sessions.

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

Phase 3 Media Meeting Agenda – February 7, 2024

The Phase 3 Media Meeting is scheduled for Thursday February 8, 2024 at 00:00 UTC in the core-media channel on Make WordPress Slack. This is a follow up to the post announcing this meeting that can be found here. If you have any topics you’d like to add to this agenda, please add them in the comments below.

Meeting agenda:

Below is an outline to drive discussion for the meeting. We will approach these topics broadly and get a sense

  • Quick round of intros.
  • Overview of the objectives for Phase 3 Media
  • 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
  • Discuss communication channels and checkpoints to be used for regular updates
  • Media Library
    • At a high level let’s discuss what the future of the Media Library looks like.
    • More global insight into media usage at the attachment level
      • Where is a media being used if at all
      • What alt attributes are being defined for it in its usage
      • Duplicate detection
  • Discuss 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. Editor’s role in editing media.
  • Back-compat relative to existing Media Library, Uploads, and Third party plugins
    • Discuss the transition process from the existing media library to the future media library. What does that look like?
    • What are the intermediary steps between where we are now and a new, fully integrated media library?
    • Will the new media library be available outside of the editor?
  • Update from William Bay on his Media Library experimentation, where Will can share some thoughts on sorting, filtering, and basic functionalities being tested in his experimental media library project.
  • Discuss the feasibility and desirability of using the Block Editor as the primary interface for media attachment editing.
    • Can we in a future state use the Block Editor as the attachment image editor using a Media Attachment Block that gives editing capabilities of the image block but updating the source image or creating new attachments.
  • Review of Phase-3-Triage Tickets
  • Open Floor for Questions and General Discussion
  • Opportunity for attendees to bring up topics not covered on the agenda, share updates, or ask questions.

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, #core-media, #meeting

Performance Chat Agenda: 6 February 2024

Here is the agenda for this week’s performance team meeting scheduled for Feb 6, 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 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