Tag Archives: core-test

Moses Cursor Ssebunya 6:00 am on May 5, 2026
Tags: core-test, , ,   

Month in Test: April 5, 2026

Hello and welcome to another edition of Month in Test, the place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

Table of Contents

Calls for Testing 📣

Calls for Testing can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Test Handbook 📘

Merging of Test Handbook in 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/

For the last few weeks, a good number of test contributors embarked on the journey of reviewing our new Test Handbook based on GitHub. The Process has been concluded successfully with the merging.

  • We want to inform that the Test Handbook is officially synced. There might be a couple of bugs and things that are not looking good pending to be fixed.
  • Feel free to give it a check here, and if you find any bugs, go to the GitHub repository and report them.
    • You can send a PR with the fix, or simply send the issue, and we will check it

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

Here’s a roundup of active tickets that are ready for testing contributions. Did you know that contributions to the Test Team are also a fantastic way to level up your WordPress knowledge and skills? Dive in to contribute, and gain coveted props 😎 for a coming release.

1. WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Testing

a. Patch Testing 🩹

Who? All contributors (not just developers) who can set up a local testing environment. Why?
It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets (2) have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

b. Bug Reproduction

It is necessary to confirm if the bug is happening under multiple conditions and environments, using the bug reproduction report in order to validate the issue.

The following tickets (134) have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, then provide a bug reproduction report:

c. Test Team Issues

Here are the current activities being discussed in the Test Team Github:

  1. We need to review the Test Team Issues. If you have a possible solution, comment in the Issue or submit a PR.

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

👋 Want to contribute to WordPress/Gutenberg? If you have a bug or an idea, read the contributing guidelines before opening an issue. If you’re ready to tackle some open issues, we’ve collected some good first issues for you.

a. Gutenberg Bug Reproduction Testing

The following tickets (9) have been filed reporting a known bug and needs testers to manually test, then provide feedback through a bug reproduction report that the issue can be reproduced.

b. Gutenberg Patch Testing

All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets (3) have been reviewed, and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

Profile Badge Awards 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉

  • none this Month

– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

  1. WordPress Ecosystem Announcements
  2. Test Team Announcements
    • Weekly team meetings are now alternating every Thursday at 15:00 UTC as per schedule
      • Test Team Voice Chat: 1st Thursday of the Month
      • Patch Testing Scrub: 2nd Thursday of the Month
      • Test Team Chat: 3rd Thursday of the Month
      • Patch Testing Scrub – Gutenburg: 4th Thursday of the Month
  3. Call for Testing

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings. Weekly team meetings are now alternating every Thursday at 15:00 UTC as per schedule. Please mark your calendars.

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

Props to @nikunj8866 for helping review this article and offering feedback

#core-test, #full-site-editing, #gutenberg, #make-wordpress-orgupdates

Nikunj Hatkar 12:57 pm on April 27, 2026
Tags: core-test, ,   

Test Chat Summary: April 23rd, 2026

On Thursday, 23 April 2026, 03:00 PM UTC, <test-chat> started in  #core-test facilitated by @nikunj8866. The agenda can be found here.

1. Attendance

In attendance was:
@nikunj8866 @ozgursar @sajib1223 @khushdoms @juanmaguitar @huzaifaalmesbah @r1k0 @mosescursor @pavanpatil1 @sajjad67 @monzuralam @sumitsingh @mohkatz (async)

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

Review the current handbook PRs before publishing

  1. Add guide for testing Gutenberg tickets with Playground
    • @nikunj8866 reviewed PR and identified missing routes entry in handbook-manifest.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., which is required to properly register the new handbook page.
    • @khushdoms was requested to add the routes entry, with reference to an existing PR.
    • @ozgursar asked whether using ?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/-branch=trunk should be recommended when testing Gutenberg tickets in Playground.
    • @r1k0 raised a concern about including a custom report example instead of using the standard Test Reports 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. format, potential confusion for new contributors.
  2. Add weekly testing digest workflow for #core-test

Proposed new handbook pages

  1. Proposal: Update Test Team Meeting Schedule for Better Participation
    • This proposal was discussed in the previous meeting.
    • No major objections were raised during this chat.
    • If consensus continues, changes may be applied starting next month.

4. Open Floor

@juanmaguitar opened a new PR to tackle an existing issue #114.

5. Announcements

WordPress Ecosystem Announcements

Test Team Announcements

Call for Testing

6. Other Meetings

Props to @mosescursor for peer reviewing this.

#core-test, #test-chat-summary

Nikunj Hatkar 8:10 am on April 23, 2026
Tags: core-test,   

Team Chat Agenda: 23rd April, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 23 April 2026, 03:00 PM UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#test-chat-agenda

Nikunj Hatkar 5:01 am on April 21, 2026
Tags: core-test, ,   

Test Chat Summary: April 16th, 2026

On Thursday, 16 April 2026, 03:00 PM UTC, <test-chat> started in  #core-test facilitated by @nikunj8866. The agenda can be found here.

1. Attendance

In attendance was:
@ozgursar @nikunj8866 @juanmaguitar @mosescursor @huzaifaalmesbah @r1k0 @khushdoms (async) @mohkatz (async)

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

Review the current handbook PRs before publishing

  1. Add Team Organization page with active and emeritus member sections
    • The team discussed the progress of the handbook PR proposing a new Team Organization page, including sections for Active Members and Emeritus Members.
    • @ozgursar mentioned that maintaining an Active Members list could be difficult and may quickly become outdated. @juanmaguitar agreed with this concern and noted that similar lists in other teams are often hard to maintain.
    • @nikunj8866 suggested defining Active Members based on contributions over the last 2–3 months, including meeting participation, testing, and feedback. He also proposed reviewing the list periodically to keep it accurate.
    • Further discussion led to a preference for focusing on an Emeritus Members list instead. @ozgursar suggested that having only an Emeritus list would be easier to maintain.
    • @nikunj8866 added that past Team Reps could be included in the Emeritus list, recognizing their contributions.
    • The team agreed to continue the discussion in the PR comments to finalize the approach.
  2. Archive old test report pages (testing-instructions, combined-report)
    • The team reviewed the PR aimed at archiving outdated test report pages such as testing instructions and combined reports.
    • @ozgursar noted that the Test Reports 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. should be referenced, as it was not clearly visible in the updated content. @juanmaguitar clarified that the PR is focused on deprecating old content and keeping only essential references in the handbook, suggesting that additional improvements should be handled in separate issues.
    • @nikunj8866 agreed with this approach and suggested creating a new issue to address the plugin reference. The team agreed that the PR is in good shape and ready for final review and merge after the meeting.
  3. Add cross-links between setup guides and patch testing report page
    • The team discussed a PR focused on improving cross-linking between setup guides and patch testing report pages.
    • @juanmaguitar noted that there are currently no clear instructions or templates for test reports in 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/, only references to patch testing. @nikunj8866 pointed out that there is already an open issue to address this gap and suggested continuing the discussion there.
    • The team agreed that additional issues should be created to define proper guidance for test reports and improve documentation clarity.

Proposed new handbook pages

  1. Create Test (or Test Team) in WordPress GitHub Teams
    • The team discussed a proposal to create a dedicated Test Team group within the WordPress 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/ organization.
    • @juanmaguitar explained that GitHub teams can help organize contributors, making it easier to tag specific groups for testing or triage. @ozgursar compared it to a role-based grouping system.
    • @nikunj8866 raised a question about whether other Make WordPress teams are using similar setups. During the discussion, it was noted that contributors need to be part of the WordPress GitHub organization to be added to such teams.
    • @juanmaguitar created an initial team but was unable to add members due to permission limitations. The team agreed to follow up in the #meta channel to clarify how contributors can be added to the organization.

4. Open Floor

  • @mosescursor questioned whether frequent meetings might be contributing to lower attendance. @juanmaguitar noted that weekly meetings are common across other Make WordPress teams.
  • @nikunj8866 suggested returning to a more focused schedule by alternating meetings:
    • One week for patch testing scrubs
    • One week for Test Team chats
  • @juanmaguitar agreed with this approach, and the team supported the idea. @nikunj8866 created a GitHub issue #154 to continue the discussion and finalize the plan.
  • @nikunj8866 shared a call for volunteers for Table Lead and Co-Lead roles 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 WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe 2026. Contributors interested in participating or nominating others were encouraged to apply via the provided form.

5. Announcements

WordPress Ecosystem Announcements

  1. WordPress Core Dev Environment Toolkit: A Faster Path to Your First Core Contribution
  2. Twenty Twenty-Seven: Team Announcement
  3. Defining expectations for Iteration issues
  4. What’s new in Gutenberg 22.9? (8 April)
  5. Elevating Individuals
  6. What’s new for developers? (April 2026)
  7. @wordpress/build, the next generation of WordPress plugin build tooling

Test Team Announcements

Call for Testing

6. Other Meetings

#core-test, #test-chat-summary

Nikunj Hatkar 11:57 am on April 16, 2026
Tags: core-test,   

Team Chat Agenda: 16th April, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 16 April 2026, 03:00 PM UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#test-chat-agenda

Nikunj Hatkar 1:12 pm on April 15, 2026
Tags: core-test   

Month in Test: April 14, 2026

Hello and welcome to another edition of Month in Test, the place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

Table of Contents

  1. Calls for Testing 📣
  2. Test Handbook📘
    1. Merging of Test Handbook in Github
  3. Weekly Testing Roundup 🤠
    1. 1. WordPress Core Testing
      1. a. Patch Testing 🩹
      2. b. Bug Reproduction
      3. c. Test Team Issues
    2. 2. Gutenberg Testing
      1. a. Gutenberg Bug Reproduction Testing
      2. b. Gutenberg Patch Testing
  4. Profile Badge Awards 🎉
  5. Read/Watch/Listen 🔗
  6. Upcoming Meetings 🗓

Calls for Testing 📣

Calls for Testing can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Test Handbook 📘

Merging of Test Handbook in 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/

For the last few weeks, a good number of test contributors embarked on the journey of reviewing our new Test Handbook based on GitHub. The Process has been concluded successfully with the merging.

  • We want to inform that the Test Handbook is officially synced. There might be a couple of bugs and things that are not looking good pending to be fixed.
  • Feel free to give it a check here, and if you find any bugs, go to the GitHub repository and report them.
    • You can send a PR with the fix, or simply send the issue, and we will check it

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

Here’s a roundup of active tickets that are ready for testing contributions. Did you know that contributions to the Test Team are also a fantastic way to level up your WordPress knowledge and skills? Dive in to contribute, and gain coveted props 😎 for a coming release.

1. WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Testing

a. Patch Testing 🩹

Who? All contributors (not just developers) who can set up a local testing environment. Why?
It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets (8) have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

b. Bug Reproduction

It is necessary to confirm if the bug is happening under multiple conditions and environments, using the bug reproduction report in order to validate the issue.

The following tickets (134) have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, then provide a bug reproduction report:

c. Test Team Issues

Here are the current activities being discussed in the Test Team Github:

  1. We need to review the Test Team Issues. If you have a possible solution, comment in the Issue or submit a PR.

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

👋Want to contribute to WordPress/Gutenberg? If you have a bug or an idea, read the contributing guidelines before opening an issue. If you’re ready to tackle some open issues, we’ve collected some good first issues for you.

a. Gutenberg Bug Reproduction Testing

The following tickets (7) have been filed reporting a known bug and needs testers to manually test, then provide feedback through a bug reproduction report that the issue can be reproduced.

b. Gutenberg Patch Testing

All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets have been reviewed, and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

  • None this month

Profile Badge Awards 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉

– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

  1. WordPress Ecosystem Announcements
  2. Test Team Announcements
    • Weekly Patch Testing Scrub: Tuesday at 15:00 UTC (runs every week)
    • Weekly Test Chat: Thursday at 15:00 UTC (runs every week)
    • Monthly Voice Test Chat: First Thursday of each month at 15:00 UTC
  3. Call for Testing

Upcoming Meetings 🗓

🚨There will be regular #core-test meetings. The schedule is being worked on and final schedule will be shared after finalizing the discussion

Current 2026 Schedule:

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

Props to @mosescursor for helping review this article and offering feedback

#core-test

Nikunj Hatkar 5:31 am on April 14, 2026
Tags: , , core-test,   

WCAsia 2026: Contributor Day Recap

It was an incredible day of contribution, collaboration, and community spirit at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia 2026 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/ in Mumbai! The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Test Team came together with energy and enthusiasm – both in person and online – to make WordPress better through testing.

Whether you tested a patch, triaged a ticket, explored WordPress 7.0 features, or just took your very first step into open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. contribution, every bit of effort mattered. 🙌

We had a wonderful mix of contributors – passionate newcomers and experienced testers – showing up from around the globe:

  • 57.1% participated in person
  • 42.9% contributed remotely
  • And most excitingly: 78.6% were first-time Core Test contributors!

🎯 What Did Contributors Work On?

  • Several contributors tested Core patches manually on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets including #64853, #64962, #65031, #65053, and #64944
  • Multiple contributors submitted Test Handbook pull requests to improve documentation (#120, #121, #128, #133, #147, #148)
  • Many first-time contributors explored WordPress 7.0 testing via the Help Test WordPress 7.0 guide
  • A few contributors also explored AI features in WordPress and 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/ 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.

💬 Community Voices

Here’s what some of our contributors shared:

  • “Remote participation from Latvia. Completed 4 patch tests and 1 triage contribution. Great experience working through real tickets with the team.” – @gaisma22
  • “I would love to continue contributing to the Test Team.” – @mehrazmorshed
  • “Explored WordPress 7.0 and tested AI features in WP. Also learned some basic features from the Team Lead and tested the Gutenberg plugin.” – @jetaldobariya1
  • “Thanks to all the table leads.” – @Dharm1025

The average contributor experience rating was an impressive 4.6 out of 5 ⭐ – a true testament to the welcoming and collaborative atmosphere the team created.

🙌 Our Contributors

A huge thank you to everyone who showed up and made this day special: @nazmul111, @mokshasharmila13, @vriti, @huzaifaalmesbah, @iamadisingh, @gaisma22, @abhishekfdd, @umeshsingla, @mehrazmorshed, @ismail0071, @abduremon, @jetaldobariya1, @pratikmandaliya, @Dharm1025

🏅 Contributor Badges

Badges are being assigned to all eligible contributors. Thank you for your patience! Keep an eye on upcoming weekly Test Team updates on make.wordpress.org/test for badge confirmations.

🗓️ Core-test Meetings

The Test Team meets every week in the #core-test channel 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/. Check out the current meeting schedule and drop by to say hi, ask questions, or just lurk and learn!

Contributor Day may be over, but your journey with the Test Team doesn’t have to stop here. From exploring patches to writing your first test, we’re here to support you every step of the way. Check out the Test Handbook and stay tuned for more ways to contribute.

Thank you for being part of the WordPress community – you made Contributor Day at WCAsia 2026 truly special. ✨

Have you joined the test team yet?

Join the Test Team

Props @ankit-k-gupta and @pavanpatil1 for pre-publish review.

#wcasia2026, #contributor-day, #core-test, #recap

Moses Cursor Ssebunya 1:50 pm on April 2, 2026
Tags: core-test, , test-voice-chat,   

Test Team Voice Chat Agenda: 2nd April, 2026

Here is the agenda for the upcoming Test Team Voice Chat scheduled for Thursday, 2nd April 2026 at 15:00 UTC which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

Props to @nikunj8866 for helping review this article and offering feedback

#core-test, #make-wordpress-orgupdates, #test-voice-chat, #web

Erick Wambua 1:42 pm on March 25, 2026
Tags: core-test,   

Test Team Chat Agenda: 26th March, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 26 March at 17:00 GMT+3, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test, #test-chat-agenda

Nikunj Hatkar 2:23 pm on March 23, 2026
Tags: , core-test   

Core Test Team at WCAsia 2026: Contributor Day

Hello WordPress enthusiasts 👋

We’re thrilled to be gearing up for another exciting Contributor Day at WordCamp Asia (WCAsia) 2026, taking place on April 9, 2026 at the iconic Jio World Convention Centre in Mumbai, India! This year’s 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/ is packed with exciting programming – including WordPress Release Panel Discussions, workshops, and the Open-Source Library.

Here’s a sneak peek at what we have planned for the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Test Team and how you can get involved.

🕰️ Important Times to Note: (All times are in IST, UTC+05:30)

  • 8:00 AM – Registration Open and Networking Time
  • 9:00 AM – Opening Remarks
  • 9:30 AM – Family Photo
  • 9:45 AM – Contributing to WordPress / Workshop / Open-Source Library
  • 10:00 AM – The Making of a WordPress Release: Conversations with Past Release Squad Members
  • 12:00 PM – Long Break / Networking
  • 1:45 PM – Group Photo( Table Leads, Facilitators & Open-Source Books)
  • 2:00 PM – Contributing to WordPress / Workshop / Open-Source Library
  • 4:30 PM – Closing Remarks
  • 5:00 PM – Contributor Day Wrap Up

For more details, please check the official schedule page.

Remote contributors are welcome to join via the #contributor-day channel 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/.

👩🏻‍💻 Meet the Test Team Table Leads

We’re excited to introduce our Test Team Table Leads for WCAsia 2026:

In-Person Table Leads:

Their expertise and enthusiasm will be invaluable in ensuring a productive and engaging Contributor Day for all participants.

🎯 Core Test Team Goals

Our focus for the day revolves around meaningful and impactful contributions:

  • Onboard New Contributors: Provide guidance and mentorship to newcomers eager to join the Core Test Team.
  • Engage with WordPress Release Panel Discussions: Join the morning session to understand how the WordPress release cycle works, engage directly with contributors involved in the release, and experience the spirit of open-source teamwork firsthand.
  • Help with tickets that need testing (Core):
  • Help with tickets that need testing (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/):
  • Test bugs or features and report new issues.
  • Improve Documentation: Enhance the clarity and comprehensiveness of testing guidelines.

Contributors with different skills, talents, and backgrounds can get involved in a variety of ways. Table leads and experienced contributors will be there to help you get started. You are welcome!

🌐 Collaboration and Community

Contributor Day at WCAsia 2026 isn’t just about work – it’s also about building connections and fostering community spirit. The WordPress Release Panel Discussions and Open Floor session will be a wonderful opportunity to connect with contributors shaping the next chapter of WordPress, ask questions, and celebrate the collective effort behind the project.

If you are new to core test contributions and want to stay updated, please join the #core-test channel on Slack.

We hold Patch Testing Scrub and Test Team Chat every Tuesday and Thursday at 15:00 UTC. Join us in the #core-test Slack channel to participate.

🔗 Helpful Resources

To make the most of Contributor Day, please review these resources before the event:

👀 Looking Ahead

As we gear up for this exciting Contributor Day in Mumbai, we look forward to the energy, conversations, and contributions that will shape the next chapter of WordPress. Whether you’re joining us in person or remotely, your contributions – big or small – make a real difference. 💪

Interested in Contributor Day but unsure if Test is the right fit for you? Check out Make WordPress’s Find Your Team tool to discover other opportunities.

Props to @ankit-k-gupta and @pavanpatil1 for peer review of this post. 🙌

#wcasia2026, #core-test