Monthly video meetings for the Make WordPress Training team: actionable discussion, concrete task assignment, and onboarding new contributors.
A monthly 60-minute video meeting where Training team members and contributors can:
- Ask questions and discuss ongoing projects
- Plan concrete next steps and assign tasks
- Onboard new contributors in a welcoming, face-to-face setting
Read the full proposal: docs/proposal.md Published on the Make WordPress Training blog: Proposal post – February 3, 2026
This is a temporary pilot repository. It was created to organize and document the Office Hours format during a three-month trial period running from April to June 2026. Keeping the pilot work in a separate space allows the format to be tested and refined without affecting the official Training Team infrastructure.
If the team decides to continue Office Hours after the pilot evaluation, the plan is to:
- Propose the process guide (
handbook/Organizing Office Hours Meetings.md) as a new page in the Make WordPress Training Handbook. - Submit the proposed changes to existing handbook pages for review by Team Reps and Admins.
- Transfer this repository and its issue history into the official Training Team structures at github.com/WordPress/Learn.
- Archive or close this repository once the transfer is complete.
Until then, this repository is the canonical reference for the Office Hours process. The handbook documents in /handbook/ reflect the process as it stands at the end of the pilot phase.
wpt-office-hours/
├── README.md ← This file
├── CONTRIBUTING.md ← How to propose topics, get involved
├── LICENSE ← CC BY-SA 4.0
├── docs/
│ └── proposal.md ← Full proposal with community feedback
├── handbook/
│ ├── Organizing Office Hours Meetings.md ← Process guide (draft handbook page)
│ ├── Proposed Changes to Existing Handbook Pages.md ← Proposed updates to existing handbook pages
│ └── README.md ← Directory Overview
├── templates/
│ ├── agenda.md ← Reference template for meeting agendas
│ └── meeting-notes.md ← Reference template for meeting notes
└── .github/ ← GitHub configuration (workflows, templates, security)
├── PULL_REQUEST_TEMPLATE.md ← PR Template
└── ISSUE_TEMPLATE/
├── config.yml ← Issue Config
├── document-correction.md ← Correction Template
└── topic-proposal.md ← Topic Proposal Template
The date of the next Office Hours meeting is listed on the Make WordPress Training homepage under Office Hours.
Meeting times rotate to cover different time zones. Past meeting notes are published as blog posts on make.wordpress.org/training.
Have a topic suggestion? Open a Topic Proposal issue – no GitHub experience needed.
All proposed topics are tracked on the Project Kanban Board.
- The moderator creates the meeting agenda as a GitHub issue in WordPress/Learn at least 48 hours before the meeting
- After the meeting, the note-taker posts the draft notes as a comment on the agenda issue
- Participants have ~48 hours to suggest corrections by commenting on the issue
- Once approved, notes are published as a blog post on make.wordpress.org/training
The /handbook directory contains working documents that support the integration of Office Hours into the Make WordPress Training Handbook:
See handbook/README.md for more details.
See CONTRIBUTING.md – no coding skills required. New to GitHub? There's a beginner-friendly section there too.
These Office Hours complement the work done on Learn WordPress – the platform the Training team builds and maintains. Meeting discussions often feed directly into new learning materials and contributor workflows.
The Office Hours are also a great entry point if you're attending a WordCamp or Contributor Day and want to get involved with the Training team.
Participation time is tracked via the Five for the Future program when you use the correct Slack tags at meeting start and end (see docs/proposal.md for details).
- Make WordPress Training Handbook
- Learn WordPress
- WordPress Community Code of Conduct
- Five for the Future
- WordPress Slack – join
#training
All participation is governed by the WordPress Community Code of Conduct and the Mozilla Community Participation Guidelines.
This repository is licensed under CC BY-SA 4.0, consistent with Make WordPress community content.
- Slack:
#trainingon WordPress Slack - Organizer: @rfluethi