Introduction to WordCamp US 2026 Contributor Day
WordCamp US 2026 takes place in Phoenix, Arizona, from August 16 to August 19, 2026. The event begins on Sunday, August 16, with Contributor Day—a dedicated session where community members gather to contribute directly to the WordPress Open Source Project. Flagship Contributor Days offer both in-person collaboration and structured remote participation for contributors across the globe.
At WCUS 2026, the Make WordPress Hosting team will host a dedicated table led by team contributors @jazzs3quence and @amykamala. Contributors will focus on core infrastructure projects, including PHPUnit-based distributed testing tools, the test reporter software, and infrastructure handbooks.
The Strategic Role of the Make WordPress Hosting Team
The Hosting team serves as a technical bridge between web hosting providers and WordPress Core developers. The primary mission of the team is to facilitate automated testing of pre-release WordPress versions on actual server environments to ensure hosting compatibility, performance optimization, and seamless update rollouts.
Over 70 hosting providers participate in the team’s distributed testing network. Automated test data is collected from diverse hosting environments and fed back to WordPress Core engineers, helping identify bugs, regression errors, and platform incompatibilities before official releases. Outside of flagship events, the Hosting team holds weekly meetings on Slack every Wednesday at 09:00 UTC and 18:00 UTC in the #hosting channel.
Contributor Day Schedule and Execution Timeline
For contributors attending in person in Phoenix, AZ, the Contributor Day schedule follows a structured sequence designed to maximize productive coding, testing, and documentation sprints:
- 08:00 – Registration and Check-in
- 09:00 – Contributor session kickoff
- 11:45 – Group photo
- 12:00 – Lunch break
- 13:30 – Continuation of contributor sessions
- 16:30 – Wrap-up and team project summaries
Prerequisites and Environment Setup for Contributors
To participate effectively at the Hosting table—whether on-site or remotely—contributors must establish several standard accounts and developer tools prior to working on tickets:
- A registered WordPress.org account.
- An active account on the WordPress Slack workspace (accessing the
#hostingand#contributor-daychannels). - A GitHub account linked to development workflows.
- A local development machine equipped with Git version control software and a local text or code editor.
Because codebases and handbooks are hosted across GitHub repositories under the WordPress organization, proficiency with standard Git commands and repository branching is required for code contributions.
Distributed Testing Architecture and Test Runner Enhancements
The core software infrastructure managed by the Hosting team consists of a custom PHPUnit Test Runner and Reporter toolset. This software enables hosting platforms to execute automated test suites against pre-release WordPress builds and upload diagnostic results back to a central public matrix.
During WCUS 2026 Contributor Day, a major technical goal is expanding the Test Runner to handle multi-environment reporting. This improvement focuses on enabling test runs against explicit target server configurations, including specific versions of PHP, MySQL, and MariaDB.
The engineering roadmap for this feature involves two distinct steps:
- Reviewing, testing, and merging an existing Pull Request (PR) that implements multi-environment support in the Test Runner repository.
- Updating the PHPUnit Test Reporter software to process, classify, and render these multi-environment test payloads on the public results platform.
Additionally, participating hosting providers are advised to audit existing active test runners, as maintenance and troubleshooting support will be provided directly at the Contributor Day table.
Handbook Documentation Priorities: Hosting and Advanced Administration
Contributors who prefer non-coding roles can work directly on technical documentation. The Hosting team maintains two official handbooks on WordPress.org: the Hosting Handbook and the Advanced Administration Handbook.
The primary documentation priority for WCUS 2026 is creating accurate PHP 7.0 and PHP 7.1 compatibility documentation within the Hosting Handbook. Contributors will also work through open backlog issues and pull requests across both repositories, helping clarify server configurations, security baselines, and operational practices for site administrators and web hosts.
Standardized GitHub Workflow and Branching Conventions
To maintain clean commit histories and track event contributions, all developers must adhere to strict repository guidelines when addressing issues in the PHPUnit Test Runner, PHPUnit Test Reporter, Hosting Handbook, or Advanced Administration Handbook repositories:
- Forking: Fork the target repository under your personal GitHub account.
- Assignment: Select an open issue, comment on the ticket stating your intent to work on it, and assign the ticket to yourself (or request a team lead assign it if you lack org-level permissions).
- Branch Naming: Create a dedicated branch off the primary branch. The branch name must include a
WCUS26prefix, the issue number, and your GitHub username. For example:WCUS26-393-jazzs3quence. - Cloning/Syncing: Clone your fork to your local dev environment or pull the latest changes into your local tracking branch prior to committing modifications.
Code Review, Platform Verification, and Merge Protocols
Submitting changes for inclusion in official Make WordPress Hosting repositories requires strict code review standards:
- Reviewers: When opening a Pull Request, assign or tag designated team representatives for review, such as
@kittenkamala,@zunaid, or@jazzsequence. - Approval Threshold: Every PR requires a minimum of two formal approvals and must be rebased or fully up to date with the base branch prior to merging.
- Hardware/Hosting Platform Verification: Any proposed changes to the PHPUnit Test Runner or Reporter software must be actively executed and verified on a live hosting platform prior to final merge approval.
- Audit Trail Commenting: Testers and reviewers must post explicit feedback comments on the PR, detailing the findings, exact hosting platform/specs used for verification, and the string mention
WCUS CD 2026.
Remote Contribution Workflow
Contributors unable to travel to Phoenix can participate fully in Contributor Day operations remotely. Remote collaboration synchronizes on Sunday, August 16, 2026, at 16:00 UTC in the official #hosting Slack channel.
Remote participants must check in by commenting on the dedicated GitHub tracking issue titled Roll Call: WCUS 2026 Contributor Day. Team leads will triage remote contributors, facilitate ticket selection, and assign review pairings throughout the event windows.
Frequently asked questions
When and where is WordCamp US 2026 Contributor Day held?
WordCamp US 2026 Contributor Day takes place on August 16, 2026, in Phoenix, AZ, starting with registration at 08:00 local time. Remote contributions occur synchronously at 16:00 UTC in the #hosting Slack channel.
Who is leading the Make WordPress Hosting table at WCUS 2026?
The Hosting table at WCUS 2026 Contributor Day is led by @jazzs3quence and @amykamala.
What software projects is the Hosting team focusing on during Contributor Day?
The team is focusing on multi-environment support for the PHPUnit Test Runner (for PHP, MySQL, and MariaDB versions), updating the PHPUnit Test Reporter, and documentation updates for the Hosting Handbook and Advanced Administration Handbook.
What branch naming convention is required for WCUS 2026 Git contributions?
Branches must be named using the WCUS26 prefix followed by the issue number and GitHub username, such as WCUS26-393-jazzs3quence.
What are the pull request merge requirements for Hosting team code updates?
Pull requests require at least 2 approvals, must be fully up to date with the base branch, and test software changes must be verified on an actual hosting platform with results noted in a PR comment containing 'WCUS CD 2026'.
Primary reference: Review the original announcement for exact release details. This article is an independent explanation and does not reproduce the source text.
