WordPress Contributor Toolkit 2.0: A redesigned app, in your language

TL;DR: WordPress Contributor Toolkit v2.0.0 has been released with a new interface built on the WordPress Design System, a settings dialog, a dark theme, and translations into ten languages.

The WordPress Contributor Toolkit removes the points of friction first-time contributors face before they write a line of code, especially during Contributor Days. You do not have to install GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/, Node.js, npm, or Docker on your machine.

The app started by setting up a full WordPress Core development environment. Version 1.0 added the full Core contribution workflow, from reading a TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. to sending your fix back as a pull request or 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.. Version 1.2 added the same workflow for Gutenberg.

Now, version 2.0 brings a redesigned interface, available in ten languages. The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and 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/ workflows work the same way as in 1.2.

A new look, built on the WordPress Design System

The whole window has been redesigned with the WordPress Design System: the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme., the page headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes., the site details, the cards, the dialogs and the tray at the bottom. If you have used 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, the buttons, notices and dialogs will look familiar.

A few smaller changes make the screen easier to read:

  • The sites list shows each site’s server status beside its name, so you can see which sites are running without opening them.
  • The footer’s tray buttons are labeled with their names, not only icons.
  • The next-action cue is visible on warning notices, so the button that moves you forward stands out even when something needs your attention.
  • The Trac window uses the app’s theme.

Settings in one place

Version 2.0 adds a settings dialog. Open it from the cog at the bottom right of the window, from Settings… in the app menu on macOS, or from the File menu on Windows and Linux.

The settings are in three groups:

  • General. The theme, the language, whether a site’s server and build watch start when you open it, whether what was running at quit starts again next time, and a default folder for new sites.
  • Sites. The PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher version every site’s development server runs on, and the WP_DEBUG and SCRIPT_DEBUG flags. A change applies the next time a server starts, and the site details show the values the next start will use.
  • Account. Your WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ username and the event you are at, which go into a patch you hand to a mentor, and 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 by the repository owner. https://github.com/ account the app opens pull requests with.

The theme can be light, dark, the same as your operating system, or custom: pick a background and a primary color, and the app builds every other color from them.

The app speaks your language

Every string in the interface is now translatable: the setup checklist, the 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. update, Review & submit changes, the pull request form and GitHub sign-in, the ticket and branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". notices, patch errors, the Terminal and Logs output, the mail dialog, the app menu, and the app’s own dialogs.

Version 2.0 ships in ten languages: Czech, Dutch, English (Canada), English (UK), Galician, Hungarian, Lao, Polish, Serbian and Turkish.

By default the app follows your operating system’s language. To choose another one, open Settings, pick a Language, and relaunch when the dialog offers to.

The contributor toolkit interface translated

A language ships with the app once it is at least 80% translated on translate.wordpress.org, so the list grows with each release. If yours is not there yet, the Contributor Toolkit project on translate.wordpress.org is a good first contribution in itself.

See what changed, file by file

After you apply a patch or check out a pull request, the site’s details now list the Changed files as a tree of folders, in two groups:

  • From the patch or From PR #N: the files the change itself touches. A pencil marks the ones you have edited since.
  • Your changes: every other file you have changed on that ticket or issue.

Click a file to open it in your editor, inside the site’s folder. Each file you changed has a revert button that puts back just that file, so you can undo one experiment without losing the patch you are testing. Discard your changes now removes only your own work and leaves the applied patch or pull request in place.

Trac details that stay

When you click Read details from Trac, the app now keeps what it read. Quit and reopen it, and the ticket’s summary, status, type, component, milestone and keywords are still there, with the time they were read. A refresh button beside that line reads the ticket again when you want the latest.

The ticket card has also been reorganized: the ticket’s title leads, its facts are on labeled rows, and unsubmitted work on the ticket appears as a notice with Review and submit and Discard changes buttons.

A smaller download 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://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/

At a Contributor Day, everyone downloads the app at the same time, on the same networknetwork (versus site, blog). Version 2.0 is about 350 MB smaller once installed. It no longer ships PHP builds it never loads, libraries already bundled into the interface, or Chromium language files for languages the app has no translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. for.

Other improvements

  • Sites run as a local environment, so Application Passwords can be tested over HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands..
  • Adminer opens the right database when the site uses randomized SQLite storage or a custom DB_PATH.
  • The debug.log pane no longer shows a line twice, or replays the whole file when you save it from an editor.
  • The pull request preview no longer lists trunk’s files when the site’s trunk is behind.
  • The main window can no longer be navigated away from the app or open other windows, and HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. mail is shown in a separate frame.

The full list is in the v2.0.0 release notes.

Help shape the next version

Try it on a real ticket or issue, in your own language if the app includes it, and tell us how it went:

  • Something broke? Open an issue with what you did and what happened.
  • Something felt off? Use the feedback form, or the feedback button in the app.
  • A string reads wrong in your language? Suggest a better one on translate.wordpress.org.
  • Want to talk it through? Ask in #core, or #core-editor for the Gutenberg flow, or comment below.

Resources

Props to @greenshady for review and feedback.

+make.wordpress.org/playground/ +make.wordpress.org/test/ +make.wordpress.org/community/

Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"

Dev Chat Agenda – October 21, 2026

The next WordPress Developers Chat will take place on Wednesday, October 21, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting focuses on upcoming releases and CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development, with time for discussions and open floor.

If you have requests for help with a ticketticket Created for both bug reports and feature development on the bug tracker. or another discussion topic, please post details in the comments section at the end of this agenda, or bring it up in Dev Chat during open floor.

Announcements 📢

WordPress 7.2

General

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

Open floor  🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

Props to @kirasong for review.

#7-2, #agenda, #core, #dev-chat

Dev Chat Agenda – October 14, 2026

The next WordPress Developers Chat will take place on Wednesday, October 14, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

The various curated agenda sections below refer to additional items. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

Announcements 📢

WordPress 7.2

General

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

Open floor  🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"

Dev Chat Agenda – October 7, 2026

The next WordPress Developers Chat will take place on Wednesday, October 7, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

The various curated agenda sections below refer to additional items. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

Announcements 📢

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

Open floor  🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"

Dev Chat Agenda – September 30, 2026

The next WordPress Developers Chat will take place on Wednesday, September 30, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

The various curated agenda sections below refer to additional items. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

Announcements 📢

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

  • @ericmann asked to open a conversation about the Secrets 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., TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. #66187 . A PR for integrating 2FA has been opened and broader conversation on the API approach would be valuable to establish a trajectory prior to the 7.2 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. period.

Open floor  🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"

Dev Chat summary: September 23, 2026

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 @audrasjb 🔗 See the agenda post.

Announcements 📢

7.2

7.1.x

  • WordPress 7.1.1 was released and contained 17 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 on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., 19 bug fixes for 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. It also contained 11 security fixes
  • Shortly after, WordPress 7.1.2 was released and fixed one important security issuesecurity issue A security issue is a type of bug that can affect the security of WordPress installations. Specifically, it is a report of a bug that you have found in the WordPress core code, and that you have determined can be used to gain some level of access to a site running WordPress that you should not have.

General

Discussion 💬

From @leemon

@leemon is waiting for feedback on these 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/ open issues. Some already have PRs associated with them:

  • Additional CSSCSS Cascading Style Sheets. styles are not generated for Navigation Link blocks on the frontend: #82171
  • Add Border and Spacing support to Navigation, Navigation Link and Navigation Submenu: #66392, #66483 and #68455
  • adding templateParts to child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. https://developer.wordpress.org/themes/advanced-topics/child-themes/ disables random titles of other template parts: #39166
  • slimImageObject drops metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. fields added to attachments: #64415

From @afercia

Andrea would like to get some feedback on Trac ticket #65729, specifically on the 3 different potential approaches summarized in comment 6.

@audrasjb shared his preference for adding a parameter to wp_strip_all_tags(), which is Andrea’s least favorite option as function should ideally be responsible to do only one thing. Jb agreed.

@dmsnell added that probably trying to handle this in wp_strip_all_tags() could backfire. He also argued against calling html_entity_decode() first and then wp_strip_all_tags() since this would be a pretty severe anti-pattern as it creates mis-parses which lead to data corruption or worse. This all relates back to escaping late and making sure we don’t confuse HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. markup and plaintext. To make matters worse, the type of a post title in WordPress is HTML markup, which is different from the type of an HTML page’s title, which is plaintext. so in some cases things like attachment titles should be rendered as HTML and at other times the plaintext context should be extracted from it.

More discussion happened in this Slack thread. Further discussion welcome in the related ticketticket Created for both bug reports and feature development on the bug tracker.: #65729

Also, for the Build/Test tools component, Andrea is waiting for feedback on this ticket: #65621

#7-1-x, #7-2, #core, #dev-chat

Dev Chat Agenda – September 23, 2026

The next WordPress Developers Chat will take place on Wednesday, September 23, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

The various curated agenda sections below refer to additional items. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

Announcements 📢

7.2

General

  • WordPress 7.1.1 was released and contained 17 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 on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., 19 bug fixes for 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, and 11 security fixes
  • WordPress 7.1.2 was released and fixed one important security issuesecurity issue A security issue is a type of bug that can affect the security of WordPress installations. Specifically, it is a report of a bug that you have found in the WordPress core code, and that you have determined can be used to gain some level of access to a site running WordPress that you should not have.

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

Open floor  🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"

Dev Chat Agenda – September 16, 2026

The next WordPress Developers Chat will take place on Wednesday, September 16, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

The various curated agenda sections below refer to additional items. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

Announcements 📢

7.2

General

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

Open floor  🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"

Dev Chat summary: September 9, 2026

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 @amykamala 🔗 See the agenda post.

Announcements 📢

7.1

7.1.1

  • WordPress 7.1.1 RC1 is planned on September 10.

7.2

General

Discussion 💬

@drivingralle is asking for feedback on 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/ issue 79082 / PR 79146.


@n8finch is requesting feedback on two Gutenberg PRs: 82367 and 81944.

Background (apart from what’s in the Issue and PRs): these are two features that are available in 7.1, but are incomplete:

  • Icons: being able to use keywords in the search is invaluable
  • Placeholder: would be great for this to work outside the Site Editor, in 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

@n8finch‘s team is pretty jazzed about these features, and would like to be able to use them. These PRs push the features over the finish line.


@oglekler proposed to move the new contributor meeting a bit earlier at 1 pm UTC so that it will be more convenient for people from Asia, but of course another shift in timing is something that people will need to get used to. She added that people from Asia are mostly who are attending, even if time isn’t ideal for them. Ideally we need to 2 meeting to cover all the globe.


@joefusco shared that tracking RTC’s polling cost and the Gutenberg & Presence 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. overlap in presence-api#444, for anyone following that space. Originating from this thread.


@ericmann shared that for those who didn’t see the comments on his make/core post about the Secrets API proposal, he have an initial working draft of a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins live at https://github.com/ericmann/secrets-api and would love feedback on this. His hope is this also addresses some of the feedback we’ve gotten from hosts/providers about how they can integrate with their own platforms as well.

More chances to come as it develops and we work on interop with other systems, but feedback is absolutely welcome and encouraged

#7-1-1, #7-2, #core, #dev-chat

Bug Scrub Schedule for WordPress 7.2

It’s time to get WordPress 7.2 ready for release, and help is needed to ensure it’s smooth and 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.-free. Whether you’re an experienced contributor or joining in for the first time, everyone is welcome! 🎉

Schedule Overview

Regular bug scrubs are being held twice a week with @audrasjb and @im3dabasia1 leading them. As the release date approaches and activity ramps up, the number of scrubs may be increased. These efforts will help ensure everything is on track for a smooth launch. Participation is welcome at any of these sessions, so feel free to join. Bring questions, ideas, and let’s scrub some bugs together!

Weekly Bug Scrub Schedule 🗓️

Alpha Bug Scrubs

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. Bug Scrubs

Focus: issues reported from the previous beta.

Release Candidaterelease 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). Bug Scrubs

Focus: issues reported from the previous 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)..

Where?

All scrubs happen in the #core channel on 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/. Just hop in at the scheduled time to get started! If you haven’t joined Slack yet, now’s the perfect time.

Want to Lead a Bug Scrub? 

Reach out in Slack, and assistance will be provided to get everything set up. Everyone is welcome—whether you’re a developer, designer, tester, or work on documentation, you can help! Just hop into the #core channel on Slack during any of the scheduled times. No experience? No problem—feel free to ask for help anytime! It’s a great way to contribute, learn new things, and connect with the community.

Check this schedule often, as it will change to reflect the latest information.

What about recurring component scrubs and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions?

For your reference, here are some of the recurring sessions:

Have a recurring component scrub or triage session?

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.” @audrasjb or @im3dabasia1 on Slack to have it added to this page.

Want to lead a bug scrub?

Did you know that anyone can lead a bug scrub at any time? Yes, you can!

How? Ping @audrasjb or @im3dabasia1 on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 7.2-focused? Awesome! It can be added to the schedule here. You’ll get well deserved props in Dev Chat, as well as in the #props Slack channel!

Where can you find tickets to scrub?

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Props @im3dabasia1 for proofreading and review.

#7-2, #bug-scrub, #core