An internal disagreement among WordPress contributors recently spilled into the open, raising questions about governance, team coordination, and documentation. What began as a routine announcement about contributor collaboration escalated into heated exchanges involving authority, project structure, and community values.

---

Understanding WordPress Governance

WordPress relies on volunteer contributors from around the world. Core teams, Documentation, Accessibility, and other groups manage development tasks. Leadership comes from consensus and documented processes rather than formal legal authority.

The Core Handbook explains contributor roles and procedures:
📌 WordPress Core Handbook

Disagreements within decentralized projects are normal. Still, when internal friction appears publicly, it attracts attention beyond the community.

---

Trigger Event: Core Program Team Announcement

On September 15, 2025, Mary Hubbard announced the creation of a Core Program Team to improve coordination across contributor groups. The team aims to:

• Strengthen collaboration across Core teams
• Document practices and processes
• Support new teams with clear procedures

Hubbard clarified that the team would not set product direction. Each Core team retains autonomy.

Some contributors reacted negatively. They viewed the announcement as a sign of overreach. This response revealed ongoing tensions about governance and authority in WordPress.

---

Root of the Conflict: Documentation Team Exclusion

The tension traces back to September 10, when documentation contributor Estela Rueda posted concerns about the WordPress 6.9 release squad. She explained that the release team temporarily excluded documentation leads. Only a single “Docs Liaison” remained.

Rueda emphasized that documentation is essential:

“Documentation is not a ‘nice-to-have’ — it is a survival requirement. Removing the role signals to new contributors that docs work does not matter.”

Documentation teams ensure software is usable, maintainable, and clear for new contributors. Excluding them risks harming both code quality and community morale.
📌 WordPress Documentation Team

---

Escalation: Governance Overreach Claims

Contributor Jenni McKinnon responded publicly, claiming the Core Program Team announcement conflicted with an ongoing governance review. She argued that no actions should occur until formal approval.

Her post stated:

“Mary Hubbard holds no valid authority in this matter… Oversight rests with SSRO and verified leadership under secured protocol.”

This language confused contributors. Open source authority comes from community consensus and procedures, not legal enforcement. The public nature of the dispute drew wide attention on Slack, forums, and WordPress social media groups.

---

Documentation Team Leadership Responds

The documentation leadership later asked McKinnon to “step away” temporarily. They cited posts misaligned with the team’s intentions, including calls for broad project changes.

Leadership emphasized that the pause allows her to reassess her involvement and explore rejoining later. This decision fueled further discussion, raising questions about balancing freedom of expression with team cohesion.

---

Key Lessons from the Conflict

1. Governance in Decentralized Projects Can Be Tricky

WordPress does not follow corporate governance rules. Authority comes from community processes, handbooks, and consensus, not formal legal structures. Misunderstandings often occur when contributors apply corporate logic.

---

2. Documentation Matters More Than Often Realized

The conflict underscores a common open source challenge: teams prioritize coding over documentation. Well-maintained documentation improves usability, reduces support requests, and accelerates onboarding. Neglecting it harms the project in the long run.

---

3. Contributor Burnout Is Real

Long-term volunteers experience burnout when workloads increase without recognition or support. Proper role definition and inclusion reduce fatigue and maintain contributor health.

---

4. Public Friction Shapes Perceptions

WordPress powers over 40% of websites globally:
📌 W3Techs CMS Usage

When conflicts appear publicly, outsiders may assume systemic problems exist. Most open source projects face occasional friction. How a community resolves these disputes shows its strength.

---

Next Steps for WordPress

• Contributors continue work on WordPress 6.9 and future releases.
• The Core Program Team remains under discussion.
• Coordination occurs through Make WordPress and official Slack channels.

The project thrives because contributors care deeply about its success. Passion can cause conflict, but it also drives improvement.
📌 WordPress Community Guidelines

---

Conclusion

The recent WordPress dispute highlights the complexities of managing a large open source project. Governance, collaboration, and documentation all play critical roles. While disagreements may appear dramatic, the project continues to function and evolve, guided by thousands of dedicated volunteers worldwide.