Consider a README to provide comprehensive overview of the WordPress Core Program

readme.md

@@ -1 +1,109 @@
-# Core Program
+# WordPress Core Program Team
+
+Welcome to the WordPress Core Program Team! We're focused on strengthening coordination across teams, improving efficiency, and empowering contribution. This is a home for those who span across product and project work.
+
+## About the Team
+
+The Core Program Team is strategically focused on the inter-dependencies between the many sub-teams that, when combined, make up the overall Core Team. We work on:
+
+- Efficient use of processes by contributors of all skill sets, levels, and backgrounds
+- Lowering the barrier of entry for new contributors
+- Making it easier for everyone to contribute
+- Documenting and refining processes across teams
+- Providing clearer project direction and consistency
+
+## Why This Team Exists
+
+There's a need for greater clarity, shared direction, and consistency across teams. Different approaches and undocumented processes can create friction or slow things down. Small issues often go unnoticed but add up over time, and starting new projects can be harder when knowledge isn't documented.
+
+## What We Do (and Don't Do)
+
+### What We Do
+- Help all groups understand how direction affects them
+- Facilitate support between teams
+- Document practices that work and share them across teams
+- Surface roadmaps and milestones within teams
+- Audit and recommend process improvements
+- Focus on efficiency and empowering collaboration
+
+### What We Don't Do
+- Dictate where the project is going
+- Tell teams what to do
+- Lead outcomes without team input
+
+## Get Involved
+
+Here's how you can join us:
+
+1. **Join the Conversation**: Participate in the `#core-program` channel in WordPress Slack
+2. **Read Our Mission**: Check out our [team formation announcement](https://make.wordpress.org/core/2025/09/13/welcome-to-the-core-program-team/)
+3. **Subscribe**: Get email updates on our [make site](https://make.wordpress.org/core/program/)
+
+## Communication
+
+We follow an **asynchronous communication** approach:
+
+- **Weekly Check-ins**: Monday updates in Slack sharing work plans and blockers
+- **Weekly Summary Posts**: Regular updates on the make site covering team activities and plans
+- **No Required Sync Meetings**: All communication is async-first to accommodate global contributors
+
+## Current Focus Areas
+
+- Building team handbook and documentation
+- Establishing communication practices
+- Processing community summit feedback for potential goals
+- Creating resources and guidelines for teams
+- Improving contribution recognition processes
+
+## Who Should Join
+
+Everyone is welcome! You might be a good fit if you have an interest in:
+
+- Project or product management
+- Program coordination roles
+- Cross-team collaboration
+- Process improvement
+- Making contribution easier for others
+
+## Weekly Updates
+
+We publish "This week in Core Program" posts every Monday (or as close as possible) summarizing:
+- Slack discussions and happenings
+- Work completed by team members
+- Plans for the upcoming week
+- Ways to get involved
+
+## Repository and Project Management
+
+We use GitHub for:
+- Issues and project tracking
+- Goal setting and milestone tracking
+- Coordinating cross-team work
+
+All discussions requiring broader input are also posted on the make site to avoid communication silos.
+
+## Goals and Planning
+
+Our goal-setting follows WordPress release cycles:
+- **Release Goals**: Specific objectives for each WordPress release
+- **Yearly Goals**: Annual objectives split into quarterly milestones
+- **Focus**: Aligned with project shipping cycles and community needs
+
+## Resources
+
+- **Slack Channel**: `#core-program`
+- **Make Site**: [make.wordpress.org/core/program/](https://make.wordpress.org/core/program/)
+- **Team Handbook**: Documentation of processes and practices
+- **Community Summit Notes**: Collecting and processing relevant feedback
+
+## Contributing
+
+1. Say hi in the `#core-program` Slack channel
+2. Participate in weekly check-ins
+3. Share your work and feedback in weekly summary posts
+4. Help document processes and best practices
+5. Collaborate across teams to improve efficiency
+
+---
+
+*This team is made better with each piece of feedback. Please share your thoughts and suggestions for improvement.*