This post comes from a discussion post initially posted in the GitHub 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 be the repository owner. https://github.com/ for the Core 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/ 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.
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 has supported this connection. One particular idea to work on in future is even a list of opportunities to contribute.
- Five-for-the-future: @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 is championing this work as what direction it will take is being worked out.
- Improving recognition of invisible contributions: @estelaris is working on this by starting within the documentation team. @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, @4thhubbard, @peiraisotta, @jeffpaul.
