Title: Proposal: Q4 focuses for the Core Program team
Author: Tammie Lister
Published: November 7, 2025

---

 [  ](https://profiles.wordpress.org/karmatosed/) [Tammie Lister](https://profiles.wordpress.org/karmatosed/)
2:45 pm _on_ November 7, 2025      

# Proposal: Q4 focuses for the Core Program team

This post comes from a [discussion post](https://github.com/WordPress/core-program/discussions/4)
initially posted in the GitHubGitHub GitHub is a website that offers online implementation
of git repositories that can easily be shared, copied and modified by other developers.
Public repositories are free to host, private repositories require a paid subscription.
GitHub introduced the concept of the ‘pull request’ where code changes done in branches
by contributors can be reviewed and discussed before being merged by the repository
owner. [https://github.com/](https://github.com/) for the CoreCore Core is the set
of software required to run WordPress. The Core Development Team builds WordPress.
Program team. In order to focus energy and be efficient, one focus is proposed. 
Additional opportunities for collaboration were identified and those are worth listing
to continue supporting. Anything not being focused on this quarter will be documented
to review in Q1 2026.

## Main focus: Roadmaps

This will be initially a discovery task that ends with recommendations, leading 
to documentation of a proposed format someone can follow looking to make one. Potentially
the tasks could be to:

 * Gather and document all existing roadmaps across teams.
 * Look at how they are built, maintained and communicated.
 * Suggest a lightweight process for teams that lack one.
 * Find a central place for a combined roadmap. Initially considering [roadmap/](https://wordpress.org/about/roadmap/)
   page as the location with potential iterations. This should not distract or get
   in way of each team maintaining their own roadmaps, but also provide a way for
   contributors to see what needs working on.

There might be other tasks form during this. An initial GitHub issue has been made
to enter discovery for [Roadmaps](https://github.com/WordPress/core-program/issues/12).

## Collaborations

During the initial collection of ideas for goals and focuses there were a few opportunities
for the Core Program team to collaborate. Whilst not a direct goal, these will be
continuous areas and those linked are done so as people identified to connect with
and find out how the Core Program team can continue to support.

 * **WP Credits**: this team needs feedback but also programming support as it grows
   and [@peiraisotta](https://profiles.wordpress.org/peiraisotta/) has supported
   this connection. One particular idea to work on in future is even a list of [opportunities to contribute](https://github.com/WordPress/core-program/discussions/6#discussioncomment-14677414).
 * **Five-for-the-future**: [@gusa](https://profiles.wordpress.org/gusa/) raised
   on several occasions where opportunities might arise for programming to support
   this area.
 * **Tooling for WordCamps**: this is in discovery right now. [@harmonyromo](https://profiles.wordpress.org/harmonyromo/)
   is championing this work as what direction it will take is being worked out.
 * **Improving recognition of invisible contributions:** [@estelaris](https://profiles.wordpress.org/estelaris/)
   is working on this by starting within the documentation team. [@felipevelzani](https://profiles.wordpress.org/felipevelzani/)
   also continues to do work around non-dev contributions.

## Next steps and get involved

Now there is a proposed goal to focus on, the next step is to get feedback and then
start working on this together. This post is that opportunity. Is there anything
you would like to add? Are you interested in collaborating or getting involved in
any particular area?

Props to everyone that contributed to the discussions for Q4, release and future,
helping form this focus and also those that reviewed this post: [@annezazu](https://profiles.wordpress.org/annezazu/),
[@4thhubbard](https://profiles.wordpress.org/4thhubbard/), [@peiraisotta](https://profiles.wordpress.org/peiraisotta/),
[@jeffpaul](https://profiles.wordpress.org/jeffpaul/).

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fprogram%2F2025%2F11%2F07%2Fproposal-q4-focuses-for-the-core-program-team%2F%23respond&locale=en_US)

 1. ![](https://secure.gravatar.com/avatar/62cfe0bb839a7a5882b2fc3eae5743478f7373ba68317cb6f015db40dd431802?
    s=32&d=mm&r=g)
 2.  [Gus Austin](https://profiles.wordpress.org/gusa/)  1:38 am _on_ November 8, 2025
 3. >  Improving recognition of invisible contributions: @estelaris is exploring this
    > in the Documentation Team, and @felipevelzani is focusing on non-dev contributions
    > through the dashboard work.
 4. The #five-for-the-future discussions I referenced in #coreCore Core is the set 
    of software required to run WordPress. The Core Development Team builds WordPress.-
    program have centered around an [ongoing thread](https://wordpress.slack.com/archives/C07UU2UGN81/p1758900544836299)
    about [@felipevelzani](https://profiles.wordpress.org/felipevelzani/), [@kel-dc](https://profiles.wordpress.org/kel-dc/),
    and others continuing the work started by [@courane01](https://profiles.wordpress.org/courane01/),
    [@peiraisotta](https://profiles.wordpress.org/peiraisotta/), [@harishanker](https://profiles.wordpress.org/harishanker/),
    and others on [Contribution Health Dashboards](https://make.wordpress.org/project/2024/09/12/wordpress-contribution-health-dashboards-an-experiment/).
 5. The main short-term goal is to define and document what counts as contribution 
    and to create a contribution ladder that helps visualize how contributors grow 
    and stay engaged across teams.
 6. At the same time, the posts on [Rethinking Contributor Recognition](https://make.wordpress.org/docs/2025/11/04/rethinking-contributor-recognition-in-documentation-team/)
    and [Recognising Contributors’ Work](https://make.wordpress.org/program/2025/10/26/recognising-contributors-work-discussion-notes-and-potential-opportunities/)
    share similar goals, such as improving recognition and visibility, defining contributor
    pathways, and documenting onboarding and offboarding workflows.
 7. Since all of these efforts seem to be approaching the same challenge from different
    angles, there appears to be meaningful overlap and potential opportunities for 
    collaboration between these teams.
 8. If so, could the Core Program team help enable and facilitate that collaboration?

### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/program/2025/11/07/proposal-q4-focuses-for-the-core-program-team/?output_format=md#respond)󠁿

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fprogram%2F2025%2F11%2F07%2Fproposal-q4-focuses-for-the-core-program-team%2F&locale=en_US)
to post a comment.

# Post navigation

[← This week in Core Program #7](https://make.wordpress.org/program/2025/11/03/this-week-in-core-program-7/)

[This week in Core Program #8 →](https://make.wordpress.org/program/2025/11/10/this-week-in-core-program-8/)