The new CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Program Team is strategically focused on the inter-dependencies between the many sub-teams that when combined, make up the overall Core Team as it exists today.

This includes (though is not limited to) efficient use of processes by contributors of all skill sets, levels, and backgrounds, lowering the barrier of entry for new contributors, and making it easier for everyone to contribute. For example, setting up a new handbook or project flows in 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 be the repository owner. https://github.com/.

Why is a team necessary?

There’s a need for greater clarity, shared direction, and consistency across teams, as different approaches and undocumented processes can sometimes create friction or slow things down. Small issues often go unnoticed but add up over time, and starting new projects can be harder when much of the knowledge isn’t written down. Focusing on documenting and refining processes, while offering a clearer view of project direction will make collaboration smoother and help both existing and new contributors feel more supported.

What will this team do (and won’t it do)?

This team will not dictate where the project is going. Instead, it will aim to help all groups involved understand how any given direction affects them, how they can support other teams, and make it known when other teams can support them. Each team is doing things differently. And whilst unique differences are great, being able to unify some common processes helps contribution. In short, this team is about efficiency, focusing on empowering quicker work, shipping, and easier collaboration.

There are also a number of things this team won’t do, it won’t tell each team what to do. It will listen and work out impact before suggesting any changes. The clear goal is how to improve efficiency, make contribution easier through clarity and improve the experience for those looking to find work to engage in. The focus is on auditing, recommending, and not leading the outcomes.

Who should be here?

Everyone is welcome, but you probably have an interest in project or product management or other similar program roles. You might be doing this within a team already, you might be interested in getting involved.

What’s next?

That’s where you come in. This doesn’t happen without people joining. The start of the journey could be to:

• Document the practices that work and share them across teams. Later this team can offer suggestions for improvements through auditing, but it starts with listening and documenting the good work being done.
• Surface the roadmaps and milestones that are there within teams.

Above all it starts by providing a place for those doing the work and looking to do this work in core teams a place to belong. 

You can get involve by saying hi in the comments and also joining the 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/. #core-program.

Thank you for the edits and feedback from @desrosj and @4thhubbard.