Mary Hubbard 4:53 pm on May 7, 2026
Tags: community-slack-migration   

Welcome All Languages and Communities to Make WordPress Slack

Over the past few months, there has been a lot of chatter regarding how contributors connect and collaborate across the WordPress project.

One thing is clear: our global contributor network is incredibly strong, but much of that work happens across separate 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/ instances and community hubs around the world. As Matt recently pointed out in โ€œLetโ€™s Slack Better,โ€ that separation can make it harder for contributors to discover one another, share knowledge across locales, and connect more directly with the broader WordPress project.

At the same time, these spaces reflect years of local leadership, collaboration, and community building that continue to strengthen WordPress globally.

Thatโ€™s why Make WordPress Slack is becoming more multilingual.

A more connected contributor network

Make WordPress Slack now has space for local WordPress communities to connect in their own languages, while also being part of the broader contributor ecosystem. This has been a long-standing request from many contributors, and itโ€™s the right time to move it forward.

This effort includes bringing MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for โ€˜WordPressโ€™ on meetup.com will help you find options in your area. communities, local and regional 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. Slack spaces, and flagship event communities like WordCamp Europe, WordCamp US, and WordCamp Asia into Make Slack so collaboration around events, contribution, and community support can happen closer to the rest of the project.

Why this matters

There are several benefits to welcoming local communities into the Make WordPress Slack:

  • Centralizing contributor collaboration: Contributors will be able to connect in one shared space while still maintaining room for local-language discussions.
  • Improving cross-locale collaboration: Communities will have more visibility into what others are building, organizing, translating, and solving around the world.
  • Strengthening ties with global teams: It will be easier for contributors to engage with Make teams, share updates, and participate in project-wide initiatives.
  • Providing access to Slack Pro tools: Many local Slack workspaces operate on free plans, which means limited message history and fewer collaboration tools. Expanding multilingual participation in the Make WordPress Slack helps more communities benefit from Pro-level functionality.
  • Preserving knowledge and history: Important conversations, decisions, and community knowledge are too valuable to lose. A more unified space helps us better retain and access that history over time.

Building on the strength of local communities

To be clear, this effort is not about replacing the important work that happens in local communities today. Local organizers and contributors have built vibrant spaces that reflect their own needs, languages, and cultures. That work matters deeply.

Instead, this is about creating stronger bridges โ€” making it easier for contributors from every language and locale to take part in the wider WordPress project without having to choose between local connection and global visibility.

Multilingual collaboration requires care, thoughtfulness, and shared responsibility. As this rolls out, the Community team will continue working with local leaders and contributors to make sure these spaces are welcoming, useful, and aligned with WordPress community expectations.

Whatโ€™s next

Some of this work is already underway. WordCamp Asia and WordCamp US are now active inside Make Slack, with WordCamp Europe planning to transition for the 2027 season. @nukaga is leading the Japanese WordPress communityโ€™s transition into Make Slack, with support from @dd32 and @karenalma. Karen will share a practical guide on the Community P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org with next steps and details.

Message archives from legacy workspaces will be preserved through Google Drive.

For now, I want to recognize the many contributors who have asked for this over time and the local community leaders who have continued building connections across the project, even when our systems made that harder than it should have been.

WordPress is a global project, and our contributor spaces should reflect that.

Letโ€™s connect in one place, support one another across languages and regions, and make it easier for every community to participate in shaping WordPress together. If you want to help with this effort, please let us know in the comments or join the #community-slack-migration channel in the Make WordPress Slack.

Welcome, ๆฌข่ฟŽ, เคธเฅเคตเคพเค—เคค เคนเฅˆ, Bienvenidos, Bienvenue, Bem-vindos, Benvenutiโ€ฆ!




Props to @_dorsvenabiliย @karenalma for this post

Velda 5:47 pm on April 23, 2026
Tags: core-program,   

Help us help others contribute to WordPress

If youโ€™ve ever been part of a make team or helped at a 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://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/, we need your eyes and expertise to help our newest contributors.

In support of WP Credits and this yearโ€™s goals, a few of us have started building an on-ramp for our contributor pipeline: Pathway Guides for evergreen contributions, and a Good First Issues board for one-off tasks across the project. Weโ€™d like to officially launch 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 in June, and we need help leveling up before that.

โ€œWeโ€™re tackling this now because there is a huge gap in showing up and contributing. Weโ€™ve not made it easy. We need to simplify things for folks so people can get to impactful contributions, quickly. This will lead us to folks sticking around, and hopefully being the next big thing in the project.โ€ โ€”Mary Hubbard

Any new contributor hits the same walls: onboarding info is scattered, pathways arenโ€™t clear, messages go unanswered 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/, and good work sometimes stalls in review. Teams want help, but weโ€™re losing people at the door. Hundreds of student contributors from WP Credits made this impossible to ignore. So letโ€™s make this better for everyone.

Pathway Guides

Weโ€™ve identified several evergreen contribution patterns in WordPress. For each one, weโ€™ve written a scannable guide that covers the steps involved and links to the right resources. This collection maps contribution opportunities across the project in one place.

How to help:

This project growing in a community-owned repository so every team can help. Guides map to handbooks rather than duplicate them, and feedback from guides flows back to teams for handbook improvements.

Good First Issues

Good first issues are specific one-off items that folks can pick up, finish, and close. Theyโ€™ve always existed in our repos, but until now, they were hard to find and track. A new Good First Issues board automatically collects new and updated Good First Issues from repositories across the project. Since we canโ€™t automatically import old issues, we need your help populating this board.

How to help:

  • Connect your repo if itโ€™s not already listed in the README
  • Close or update any stale Good First Issues
  • Follow up on any GFIs awaiting reviews
  • Invite new contributors by using the Good First Issues tag and including context

Spread the Word

Tell your teams and meetups about this work. More eyes and more experiences will make this better. And if you can work with students directly, consider applying to become a WP Credits mentor.

The sooner we can get guides tested and issues cleaned up, and the healthier our Good First Issues are, the stronger this is at WCEU. 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.โ€ me (Velda) in #core-program with questions or ideas for how to move this forward. Thank you for your eyes, thoughts, and any time you can share.

Props @peiraisotta, @karenalma, @annezazu, and @karmatosed, and @4thhubbard for reviews, to the many who have reviewed individual guides, to @mosescursor and @fellyph for contributing to guides, and to @clk87, @marutim, and @kel-dc for getting this started with me.

#wpcontributors
Julia Golomb 9:17 pm on February 2, 2024  

Incident Response Team: Call for Nominations

Update: The 2024 Incident Response Team cohort training is postponed from Q2, and will instead be held during Q4 of 2024.

Summary: Submit your Incident Response Team nominations by February 14, through the button below.

The WordPress Project Community Code of Conduct helps WordPress community members and contributors understand how we aspire to work together in โ€œofficialโ€ WordPress spaces. When people see behavior that doesnโ€™t match the Code of Conduct, the Incident Response Team can assist in determining if the Code of Conduct has been breached and addressing situations that are in question of doing so. The Incident Response Team does not actively search for or monitor behavior. Instead, this team is a resource to the community for when things donโ€™t go as expected.โ€‚The Incident Response Team handbook captures the teamโ€™s current practices.

The first Incident Response Team cohort was onboarded to the team in December 2022, and itโ€™s now time to train and onboard a second cohort of Incident Response Team members!

The work of taking and responding to incident reports requires a high degree of professionalism and emotional intelligence, and it is often invisible and difficult work. Because of this, individuals are vetted and need to successfully complete a 6-session, cohort-based training prior to joining the WordPress Incident Response Team. Read on for all the details!ย 

How to Join the WordPress Incident Response Team

To best serve the community, Incident Response Team members need to be able to remain calm when faced with difficult situations and possess exceptional listening and communication skills. When responding to incidents, they need to be able to maintain confidentiality* wherever possible and think objectively.

Because of this, new members join the team through a nomination, vetting, and cohort-based training process. Please complete the form below to submit your nomination of who you think would be a good candidate for this team. Nominations are due by February 14.

Note: The Community Team also offers online training for incident response, covering topics like expectations when doing this work, how to take incident reports, and how to respond to reports. This training is available on Learn WordPress for everyone who is interested.

By Feb. 14: Nominate a WordPress community member to the Incident Response Team

Nominations will go through a vetting process similar to how the Community team vets organizers. For Incident Response Team members, vetting will include:

  • Making sure they are in good standing with WordPress
  • Familiarity with WordPress and 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. practices is a plus
  • Perfunctory review of social media
  • Checking for compliance with the GPLGPL GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a โ€˜copyleftโ€™ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples.
  • Reviewing any examples of excellent communication
  • Further, it is important that the Incident Response Team be diverse to reflect our global community, and this will be a consideration for the final make up of the team.ย 

The vetting will be done by myself (@juliarosia), @adityakane, @angelasjin, and @samsuresh, and @chanthaboune will give final approval.

It is our hope that Incident Response Team members can commit to being on the team for one full year. Depending on the volume of incident reports, they can expect to contribute anywhere between 2 to 15 hours a month. In addition, to help Incident Response Team members be well prepared, they are expected to successfully complete the required training prior to joining the team.

Training for the Incident Response Team

While anyone can complete the incident response training on Learn WordPress, potential Incident Response Team members will complete additional training alongside peers in a cohort. The cohort will meet synchronously six times (one hour-ish each), across the span of seven weeks, to discuss Incident Response Team training modules and practice through role play. There will be optional, highly recommended office hours and additional opportunities to practice learned skills.ย 

In addition, Incident Response Team members will be required to complete DEI training that is applicable to WordPressโ€™ global contexts.ย 

The time commitment for this training will be approximately 2-3 hours per week at minimum, across seven weeks. Each session will be offered twice, to accommodate APAC, EMEA and AMER timezones.

As with any team, we will continue to bring on new team members over time. We aim to train and onboard a new cohort every 12 to 18 months.

Questions? Comments? Feedback?

What questions or feedback do you have? Share them in the comments below.

*A note on confidentiality: While the WordPress project tries to work transparently and in public spaces as much as possible, for the safety of community members, incident response needs to be treated confidentially wherever possible. However, anonymized, annual reports are published.

Mary Hubbard 6:41 pm on January 23, 2026  

Big Picture Goals for 2026

Iโ€™ve been here a little over a year now. In that time, Iโ€™ve seen what works, where things get stuck, and how much care and effort contributors bring to this project every day. As I shared during State of the Word, 2026 is about momentum.ย 

Momentum means building on whatโ€™s already working, being clearer about direction, and making it easier for people to participate and move forward. It means taking the energy that already exists in this community and turning it into progress that compounds.

This is my first time sharing big picture goals with the Make community. My aim is to be clear about priorities and direction, while keeping the door wide open for collaboration. WordPress works because contributors show up. 2026 is about making it easier for more people to do exactly that.

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

2026 will return to 3 releases a year coinciding with our events. With WordPress 7.0 coinciding with WordCamp Asia. 7.0 aims to offer a significant step into Phase 3: Collaboration, with real-time co-editing bringing Google Docs-style collaboration directly into the Editor.ย 

Efforts are underway to unlock powerful new workflows through the Abilities 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.-powered Command Palette and a standardized WP AI Client API, enabling plugins and hosts to integrate AI assistants in a provider-agnostic way.

Media handling will take a major leap forward in 7.0 with the graduation of client-side media processing into Core. Image resizing, compression, and format handling will increasingly happen directly in the browser, dramatically reducing server load while delivering faster, more reliable uploads for creators.

On the styling front, customization of mobile menus and responsive editing controls will finally give creators the ability to tailor layouts for different screen sizes and hide blocks by viewport, addressing a long-requested community need. The introduction of simplified pattern editing alongside new blocks like Tabs and Icon expands the creative toolkit available out of the box, making design more intuitive for a wider range of creators.

Together, these features represent a cohesive push toward a more collaborative, intelligent, and responsive WordPress experience.

[Get Involved with WordPress Core]

AI Everywhere, With Clear Guardrails and Benchmarks

WordPress will continue to invest in AI in a focused, intentional way. The goal is to make WordPress easier to use, easier to build with, and easier to contribute to, across the entire experience.

Guided by the AI building blocks, AI in WordPress will prioritize a few practical outcomes:

  • Helping people create, edit, and refine content where they already work.
  • Reducing friction in site building, configuration, and common workflows.
  • Supporting contributors and users with clearer guidance, context, and next steps.
  • Lowering the barrier to contribution by helping people find and complete meaningful work.

At the same time, the Core AI team will publish project-wide guidelines for AI usage within WordPress. These guidelines will focus on transparency, user control, data responsibility, and alignment with WordPress values. As AI becomes more embedded across the project, shared expectations matter, both for contributors and for the broader ecosystem.

[Read More from the Core AI Team]

Revamping Meetups

Meetups are the primary front door to the community. Letโ€™s be more intentional about getting new people involved quickly.

As more contributors come in through initiatives like education programs, like Campus Connect and WordPress Credits, mentors should help them find a local meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for โ€˜WordPressโ€™ on meetup.com will help you find options in your area.. Meetups are often the first place WordPress feels real. They are local, human, and reputable. Many WordCamps started as meetups, and that pathway still matters.

This year, we want to double down on meetups as places of active participation, not passive attendance. As AI tools become more common across the web, the need for shared learning increases. Meetups are where people can sit side by side, learn how these tools actually fit into WordPress workflows, and build confidence together. AI moves fast and we can develop better understanding, judgment, and together as a community.

That means prioritizing issue-focused sessions where people work together on real problems, hands-on learning tied to actual WordPress needs, and clear next steps that move people from meetup participation into contribution.

Meetups are where people build confidence, relationships, and momentum. When they work well, they turn curiosity into commitment. That is why they remain the primary front door to WordPress in 2026.

[Find a Meetup] | [Start a Meetup]

Community, Education, and the Contributor Pipeline

WordPress education programs are scaling quickly. WordPress Credits and WordPress Campus Connect have students arriving ready to participate and eager to contribute.

The project needs to be much clearer about where new contributors should go next and how they get started. Program managers can help connect student groups to Make teams, but that only works if each team is prepared to receive them.

Iโ€™d like to ask the Make teams to help make this possible by:

  • Maintaining clear onboarding materials and contribution paths.
  • Identifying approachable first issues or starter tasks.
  • Encouraging mentors who can help new contributors get oriented and moving.

Education is becoming one of WordPressโ€™s strongest growth engines. It brings in new voices, fresh perspectives, and people eager to learn. As contribution continues to grow, the long-requested Contributor Dashboard will help make that work more visible.ย 

Over time, we want to move toward WordPress Foundation credentials that help standardize how WordPress skills are understood and communicated. These credentials would reflect what someone knows, what they can do, and how they work, giving employers a clearer signal when hiring for WordPress-related roles.

[Learn More About WordPress Education Programs]

Kel Santiago-Pilarski 9:08 am on March 4, 2026  

The Contributor Dashboard Pilot is Live: Whatโ€™s Next?

Building on the initial project thread, the Contributor Dashboard pilot is now live, marking an important step toward creating a clearer view of how contributors join, participate, and grow across the WordPress project.

This post outlines proposed features for the next phase of the Contributor Dashboard pilot. Weโ€™re sharing these ideas early to gather feedback from the community before implementation begins.

Current Status

The pilot dashboard is finally ready: https://wpcontributordashboard.org/

The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. functionality is in place:

  • Three-tier data architecture (Events โ†’ Profiles โ†’ Dashboard)
  • Contributor Ladder framework
  • Activity status tracking (active/warning/inactive)
  • CSV import system for contributor activity data

Development is happening in the public GitHub repository.
View the dashboard demo video here.

Contributors from multiple Make teams are developing the Contributor Dashboard pilot. Project collaborators include @felipevelzani, @unintended8, @francescodicandia, @dd32 and @kel-dc

Proposed Features

Weโ€™re proposing two features for the next phase. Feedback is welcome on both.

1. Team-Managed Personas

Each Make team can create its own contributor personas, with custom ladders and requirements that reflect how that team actually works.

Different teams contribute in different ways, one ladder doesnโ€™t fit all. Team reps can define and manage these personas, and contributors can appear on multiple ladders based on their activity across teams.

Example use cases:

  • Polyglots can create language-specific personas for translation contributors.
  • Community can create personas for 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. or MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for โ€˜WordPressโ€™ on meetup.com will help you find options in your area. organizers.
  • Support can separate forum contributors from those seeking help.

2. Automated Engagement

Automatically recognize contributors when they reach key milestones.

Timely recognition improves retention and reinforces meaningful participation. When someone makes their first contribution, reaches a new ladder step, or stays consistently active, the system can trigger messages, props, or even swag (stickers, etc) from The Mercantile.

Recognition becomes built-in, not manual.

Feedback Requested

Weโ€™d love to hear your thoughts on these proposals. If we had to start with one of these two, which would provide the most value? Are any other things not considered that you think should be implemented and/or could bring a lot of value?

The overall goal is to create an engine focused on improving the contributor experience overall.

Please share any feedback by March 17, 2026. We plan to start implementing the new phase by this date.

Get Involved

If youโ€™re interested in contributing to these features:

Destiny Kanno 3:37 am on May 1, 2025  

Review of Blocked Community Members

In an ongoing effort to foster a healthy and inclusive community, we are conducting a thorough review of blocked community members, prioritizing individuals who were blocked between August 2024 and the present date without communication or notification. This initiative spans both the 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/ and 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/ platforms and aims to identify accounts that can be unblocked and reinstated, allowing those members to re-engage with the community.

Unblocking Criteria and Process

The decision to unblock an account will be based on a thorough evaluation of the actions that led to the initial 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.. While some blocks were justified and will be upheld, we acknowledge that mistakes may have occurred, and some members may have been unfairly blocked. Our aim is to correct any past errors and provide a clear path for those members to re-engage with the community. We believe that by working together and fostering open communication, we can move forward and build a stronger, more inclusive community for everyone.

Factors Considered During Review

  • Severity of the Infraction: The nature and severity of the situation that led to the block will be a primary consideration.
  • Time Elapsed: The length of time since the block and any subsequent behavior of the individual will be taken into account.
  • Agreement to Adhere to Community Guidelines: The individual has expressed a commitment to follow the community code of conduct and forum rules.
  • Community Impact: The potential impact of unblocking on the overall community health and well-being will be considered.

Timeline and Communication

We understand that this process may take some time due to the number of accounts under review and the need for a thorough evaluation of each case. Please note that we are prioritizing those who were banned without notice or communication, and spammers will not be notified.

We are committed to providing regular updates on the progress of this initiative and will communicate any significant developments to the community in a timely manner.

Commitment to a Healthy and Inclusive Community

This unblocking initiative reflects our commitment to fostering a welcoming, inclusive, and respectful community where all members feel valued and supported. While maintaining the health and integrity of our community is paramount, we also believe in providing opportunities for individuals to learn, grow, and contribute positively. This initiative is a step towards achieving that balance, and we are hopeful that it will contribute to a stronger and more vibrant community for all.

We appreciate your patience and understanding as we work through this process.

Kel Santiago-Pilarski 5:34 am on December 20, 2025
Tags: contributor-dashboard   

Project Thread: Contributor Dashboard Pilot Project

A Contributor Dashboard Pilot is underway within the WordPress project, building on previous community work, and responding to long-standing requests from the community for better visibility into contributor journeys โ€“ how people join, participate, and grow across Make teams.

Contribution activity, especially non-code work is spread across many tools and systems. This makes it difficult to recognize contributors, understand engagement over time, and identify where support is needed.

Project Status

This project is currently in the active pilot development phase, led by @felipevelzani, @unintended8 and @kel-dc.

A limited multi-team pilot launch is planned for the end of February 2026. This project thread will be updated as work progresses.

What Weโ€™re Building

Weโ€™re building a Contributor Dashboard that maps contributor activity across teams into a shared Contributor Ladder framework:

Connect โ†’ Contribute โ†’ Engage โ†’ Perform โ†’ Lead

The ladder is behavior-based and describes patterns of participation over time. It does not rank contributors or imply that some contributions matter more than others. All contribution types and all contributors matter.

The goal is to help teams understand participation patterns, identify where support may be needed, and improve contributor experiences over time.

Why Weโ€™re Doing This

The project addresses several challenges across the project:

  • Contribution activity is scattered or not tracked
  • Non-code contributions often lack visibility
  • Teams have limited insight into how contributors progress over time
  • Cross-team onboarding, retention, and engagement patterns are difficult to assess

How Weโ€™ll Build the Pilot Dashboard

For the pilot, weโ€™re taking a multi-team approach using a custom 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. that maps existing contribution activity from 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/ systems to ladder stages. This activity-based approach allows us to validate the model, identify data gaps, and gather cross-team insights without introducing new infrastructure or requirements for contributors.

Additional technical details and implementation notes are documented in the projectโ€™s public reference materials.ย ย 

Scope and Data

This pilot starts intentionally small and focuses on a limited set of existing contribution signals to test the dashboard and ladder approach. It does not aim to capture 100% of all contributions across Make teams.

The pilot does not replace or change Five for the Future, contributor recognition programs, or existing team processes, and it introduces no new requirements for contributors or Make teams.

Contributor privacy is a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. consideration. The dashboard uses existing WordPress.org accounts and activity data, does not display personal or sensitive information, and does not create new contributor profiles.

Hosting

  • The pilot dashboard will be hosted on Pressable to support development, testing, and iteration during the pilot phase, with the intention of moving to WordPress.org infrastructure in a future phase.
  • The custom plugin is designed to work within existing WordPress.org 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. systems and data constraints, without introducing new external dependencies.

Timeline & Milestones

โ€ข Januaryโ€“February 2026: Implementation, testing, and reviewย ย 

โ€ข End of February 2026: Pilot launch

How to Get Involved

Weโ€™re looking for contributors to help bring this pilot to life and welcome collaboration from across Make teams. For this pilot, weโ€™re especially looking for contributors who can help with the following:ย 

  • Building and improving the dashboard and plugin
  • Reviewing and validating contribution signals and ladder mappings
  • Testing the dashboard experience and reviewing insights
  • Helping iterate on documentation and communication as the pilot evolves

If youโ€™re interested in getting involved:

We welcome ideas and participation from all Make teams and contributors during the pilot and as the project evolves. Community input will help inform iteration and improvements, while the pilot proceeds unless material concerns are raised around privacy, security, or alignment with WordPress project values.

Props @4thhubbard for post review.

#contributor-dashboard

Jonathan Desrosiers 9:30 pm on December 18, 2025  

Proposal: 2026 Major Release Schedule

As 2025 comes to a close, itโ€™s time to reflect and start thinking about what the major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as โ€œX.Yโ€ -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. schedule for the 2026 calendar year will be. This year, the community came together and published two fantastic new major versions of WordPress to the world: 6.8 โ€œCecilโ€ in April and 6.9 โ€œGeneโ€ in December.

While 2025 saw just two releases, the goal is to return to 3 major releases in 2026 (roughly one every 4 months).

This cadence has proven to effectively balance the many different factors at play within the global contributor community. The 4 month release cycle also:

  • Is long enough to build out quality new features for each release.
  • Is short enough to encourage shipping iteratively rather than pursuing perfect software (release early, release often).
  • Allows for 1-3 minor releases in between when following a 6-8 week timeline.

2026 Schedule (Proposed)

Using the ideal 4 month spacing between each release and making efforts to avoid major holidays, the final release dates for the next three releases fall within close proximity to a few prominent in-person WordPress events for 2026.

Following the successful live release of 6.9 during State of the Word earlier in December, the schedule below was created to continue trying out this model.

WordPress 7.0 โ€“ Thursday, April 9th

To start off the year, 7.0 is targeted for release during Contributor Day of WordCamp Asia. This creates some unique and exciting teaching opportunities! Newer contributors can observe the release process live to learn about how to contribute, or even participate in the release process, pitching in to help ship a version to WordPress to the world on their first day contributing.

Important dates

  • 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: Thursday, February 19, 2026
  • RC1: Thursday, March 19, 2026

WordPress 7.1 โ€“ Wednesday, August 19th

This date for the public release of 7.1 coincides with the final day of WordCamp US. WCUS begins on a Sunday and ends on a Wednesday, which makes the final day more suitable for a release.

Important dates

  • Beta 1: Wednesday, July 1, 2026
  • RC1: Wednesday, July 29, 2026

WordPress 7.2 โ€“ December 8th, 9th, or 10th

To round out 2026, the community can celebrate the yearโ€™s accomplishments by releasing 7.2 on or around the annual State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what weโ€™ve done, what weโ€™re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/. address.

Important dates

  • Beta 1: October 20-22, 2026
  • RC1: November 17-19, 2026

A Few Notes

  • A call for volunteers interested in serving on the 7.0 Release Squad will be published the week of January 4th. If you are interested, please keep an eye on Make WordPress Core or subscribe for updates via email in the siteโ€™s 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..
  • While the releases are lining up with in-person events, there is no requirement to travel in order to be on a release squad. All communication and coordination will continue to happen 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/.
  • A healthy balance between in-person and distributed contributors on release day is actually preferred. This helps ensure that any unexpected technical issues such as poor/unavailable WiFi do not result in a delayed release.
  • The spacing between the three flagship WordCamps in 2026 presents a strong opportunity to be intentional with release timing. With the proposed April 9th date for 7.0, moving straight into the 7.1 cycle would significantly compress the alpha period for feature work. The eight-week window between 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 & WordCamp Europe is an excellent fit for a 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., which could help to deliver meaningful improvements with confidence and adequate breathing room.
  • During the 6.9 dry run and final release, contributors identified several opportunities to improve the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook, especially the pages aimed at documenting the release practices and processes. The live release of 6.9 notably shined a light on areas that require clarification to ensure both in-person and distributed contributor groups can synchronously collaborate more transparently and effectively. These will be collected and shared in a separate Make Core post in January.
  • The WordPress 7.2 date is the least flexible of the three with earlier dates encroaching on the major global financial holidays of Black Friday/Cyber Monday/Giving Tuesday, and later dates getting too close to major religious holidays and end of year time off.
  • Friday, Saturday, Sunday, and Monday have historically been considered unsuitable for a release to avoid spoiling weekends of those who use, build with, maintain, or support anyone with a WordPress site.

Discussion & Feedback

As always, the dates above are being proposed to allow contributors to begin planning for the rough timing of each of the 3 releases in 2026. There is some flexibility to make adjustments if necessary based on community feedback or factors that were not considered.

Do you have questions or thoughts about the release schedule as proposed? Ideas for ways to improve the Core Handbook or the release process itself? Or maybe a specific feature that youโ€™re most looking forward to in 2026? Share them below and join the conversation.

Props @annezazu, @jorbin AND @4thhubbard for helping to narrow down possible dates and/or reviewing this post.

Jonathan Desrosiers 1:55 am on June 25, 2025  

A Little (Late) Spring Cleaning

Following up on the codified criteria for a repository to live under the WordPress organization on GitHub, a comprehensive audit of all repositories under both the WordPress and bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org 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/ organizations has been conducted.

To support this effort, every repository was catalogued in a spreadsheet, along with metadata to assess which met the established criteria. This includes factors such as ongoing maintenance, alignment with an active 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/ team or initiative, and whether the repository serves a continuing purpose.

Archived Repositories

In total, 20 repositories in the WordPress GitHub organization were identified as no longer meeting the criteria for active maintenance under the organization. These include:

  • Feature plugins for projects that have already been merged into WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and are no longer providing any additional functionality.
  • Some repositories were created for short-term experimentation or one-off demonstrations. While useful at the time, they no longer serve an active purpose and were archived to reduce clutter.
  • Legacy communication efforts that are no longer relevant.

The following repositories have been archived between June 5, 2025 and June 24, 2025:

Additionally, one repository was archived under the bbPress GitHub organization: wpbbp.

Archived repositories remain publicly accessible for reference purposes. Specific reasons why each repository was closed can be found in the Archive Notes column of the spreadsheet

Closed Plugins

Archiving repositories was only one part of this effort. Since the GitHub repositories often overlap with plugins hosted on the WordPress.org Plugin Directory, all plugins maintained or supported by the wordpressdotorg user were also reviewed. Plugins tied to deprecated features, outdated support needs, or now-merged projects were closed to reduce confusion and focus contributor attention on current tools.

The following 11 plugins were closed on June 24 2025:

To preserve historical context, a new page in the Core Team Handbook has been published as a reference of all retired plugins that were officially supported by the Core team at one point. Plugins closed prior to this effort can be added retroactively as theyโ€™re identified.

Archived 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/ Channels

Beyond code and plugins, Slack was also reviewed. Slack channels associated with completed initiatives, legacy features, or inactive Core components were archived. This helps reduce noise and ensures that active discussion spaces align with the projectโ€™s current areas of focus.

feature-* and core-* component channels were considered inactive if there had been no meaningful collaboration for at least one year.

The following 30 Slack channels were archived in the WordPress.org Slack instance on June 24, 2025:

Archived Slack channels remain publicly accessible and can easily be unarchived if new maintainers come forward or if the channel is the most appropriate space for new discussions.

Looking Ahead

As the project continues to evolve, periodic audits like this help keep our resources aligned with current priorities. If you believe something was archived prematurely or have suggestions for future cleanups, please detail in the comments.

When archiving certain code bases, plugins, and channels, itโ€™s important to pause and thank the many contributors who brought them to life. Their work forms the foundation for continued progress. Every commit, idea, and conversation has helped advance WordPressโ€™s mission to democratize publishing. And for that, we say โ€œthank you!โ€

Props @4thhubbard for post review.

Mary Hubbard 2:13 pm on September 15, 2025  

Announcing the Core Program Team

This program model was first introduced with the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI Team. Building on that experience, Iโ€™d like to expand it into an experiment with the launch of theย Core Program Team. Tammie Lister has agreed to help as the first team representative.

The goal of this team is to strengthen coordination across Core, improve efficiency, and make contribution easier. It will focus on documenting practices, surfacing roadmaps, and supporting new teams with clear processes.

The Core Program Team will not set product direction. Each Core team remains autonomous. The Program Teamโ€™s role is to listen, connect, and reduce friction so contributors can collaborate more smoothly.

You can get involved by joining the #core-program 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/ channel and following updates on the Core Program Team Blog, including a the welcome post that outlines next steps.

I am excited to see how this experiment helps Core teams work together and makes contribution more accessible to everyone.

Props to @karmatosed, @dd32, @desrosj who helped move this forward.