Host Office Hours on July 26, 2026

[sumitsinghwp]

Description

This issue was discussed in the Office Hours session on June 27, 2026.

Host and moderate the next Office Hours meeting on Sunday, July 26, 2026, 14:00 UTC.

Tasks

• Prepare the agenda based on the open issues from the June 26th meeting
• Open the Zoom session and welcome participants
• Run the meeting along the published Office Hours concept
• Coordinate the note taker and the follow-up actions

Context

The June 27th Office Hours appointed Sumit to host and moderate the next meeting. The format follows the proposal.

Meeting Agenda for 26 July

Issue	Task	Owner	Status
#3415	Review the task documentation template	SAndrew	open
#3416	Prepare and publish the preferred-meeting-time poll, then confirm the day and time	sumitsinghwp	open
#3417	Publish the admin roster post (TT-Admins)	sumitsinghwp	open
#3475	Collect the TT-Admins comments on the 2026 goals	sumitsinghwp	open
#3476	TT-Admins meeting and Triage: separate or merge	sumitsinghwp	open
#3478	Host the Block Editor workshop for Note Takers	sumitsinghwp, Vasant	open
#3479	Record the screencast tutorial for Note Takers	sumitsinghwp, Vasant	open
#3480	Follow up with the Meta team on the Sensei templates	rjekic	open
#3481	Contact the Sensei developers about the lesson order	rjekic	open
#3482	Export the Help Scout tickets for the TT-Admins review	rjekic	open
#3484	Promote the issue list at the Tuesday meeting	rjekic, sumitsinghwp	open
#3486	Introduce a Last Reviewed field in the handbook	devmuhib009, rjekic	open
#3487	Define badge-hunter filter measure	devmuhib009, rjekic, sumitsinghwp	open
#3535	Schedule and host the next Office Hours meeting	to assign	open
#3536	Write and publish the meeting-formats proposal (Tuesday meeting, Office Hours, TT-Admins)	devmuhib009, rjekic, sumitsinghwp	new
#3537	Migrate the Office Hours topic list into the Learn GitHub	to assign	new
#3538	Set up prioritization for Office Hours topics	to assign	new
#3539	Draft the badge-system proposal	sumitsinghwp, rjekic	new

[rfluethi]

Update from the Office Hours on 2026-06-27: the next meeting is tentatively Sunday 26 July 2026 (as an exception) or Saturday 25 July 2026, 14:00 UTC. Sumit will confirm, and it depends on whether we continue the Office Hours.

[rfluethi]

Hi @sumitsinghwp

Is Sunday, 26 July 2026, 14:00 UTC confirmed as the final date?

If so: could you confirm that you will moderate, and let us know the main topic? It would help to announce the topic early so everyone can prepare.

We also still need a note-taker. Could you find a volunteer or assign someone?

Thanks a lot, and best regards.
Rico

[sumitsinghwp]

Hey @rfluethi, yes, the 26th is confirmed.

Please let me know when everything is final, and I’ll update the Team homepage. Could we also prepare and publish the meeting agenda as a new blog post before the meeting?

Here are some suggestions by Nikita Desai.

Maybe at the moment it's not clear to participants: "What's in it for me if I spend an hour here?"
A few suggestions that might help increase participation:
• Give each session a clear purpose instead of a generic "Office Hours" title. For example:

Office Hours: Contributor Onboarding
Office Hours: Learn Content Sprint
Office Hours: Course Review & Feedback
Office Hours: GitHub Issue Triage
A focused topic helps participants quickly decide whether the session is relevant to them.
• Publish the agenda 5–7 days in advance so participants know what to expect. This could include:

2–3 discussion topics
Any decisions that need community input
GitHub issues or tasks that will be worked on
Who would benefit most from attending (new contributors, content reviewers, administrators, etc.)
Having a clear objective and agenda for every session may make it easier for participants to see the value of joining and encourage more consistent attendance.

Just a suggestion, please ignore if already done.

[rfluethi]

Thanks for confirming, @sumitsinghwp. Sunday, 26 July, 14:00 UTC.

About the agenda blog post: I would skip it. Our published concept does not ask for a separate post for every session. It asks for an announcement at the Tuesday meeting and a reminder beforehand with the planned content. Nikita's point is still valid though. People need to know in advance what the session is about and whether it is relevant for them.
So let's do it where the people actually are, which is the Tuesday meeting in #training on Slack. Almost nobody reads this issue.
Concretely:

By Monday: you pick three topics from the project board (Office Hours Topics) and bring them along.
Tuesday, 21 July, 07:00 UTC: you put the three topics to a vote in the meeting, together with the question of whether we continue the Office Hours at all. The concept has criteria for this (an average of five participants, or three concrete outcomes per session, or a team vote), and you raised the question yourself. It belongs before the topic choice.
Wednesday, 22 July: the result is set, promotion starts in Slack, and I will update the Team homepage with the date and the topic.

That way the session has a real title instead of "Office Hours", and the announcement goes out four days ahead.
Two things from the task list in this issue are still open, and they sit with the host:

Moderation: can you confirm that you will run the session?
Note taker: we still have nobody. Could you ask for volunteers at the Tuesday meeting?

If this does not work for you time wise, please say so now and not shortly before the date.

[sumitsinghwp]

Here are metting agenda to discuss on office hours with all issue list

https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Office%20Hours%22

CC: @rfluethi @rjekic @devmuhib009