Skip to content

Clarify formats, roles and responsibilities, and revive the TT-Admins meeting #3644

Open

Description

@rfluethi

Description

Discussed in the Office Hours on August 22, 2026 #3640. The responsibilities of the groups and meeting formats are not clearly separated, access rights cannot be handed over, and the TT-Admins meeting effectively does not take place. As long as that is the case, work waits on individual people.

Work steps

  • Record the purpose of the Office Hours: answer questions, discuss important topics, end with clear tasks and clear ownership
  • Establish that every session either creates issues or names who writes a proposal for the blog
  • Introduce topic groups with sub-issues, so the person owning a topic can assign work
  • Establish that owners of larger topics report on progress at the Tuesday meeting on a regular basis
  • Schedule and announce the TT-Admins meeting with a fixed day and a fixed time
  • Record the agenda of the TT-Admins meeting: go through open issues, assign people and topics, set reminders, with closing issues as the goal
  • Plan for longer first sessions, with the format shrinking into a standup over time
  • Record the access rights per system: GitHub, make.wordpress.org/training, Learn WordPress, Sensei
  • Identify and remove inactive administrators and team reps
  • Define the roles and responsibilities of the groups in the handbook

Context

Without clear scopes it stays unclear which topic belongs where, and without a working TT-Admins meeting the issue backlog does not move. One example from the session: labels could be applied right away, but the rights to do so are missing, so the work then waits on a single person.

Activity

  1. rfluethi commented on Sep 26, 2026

    @rfluethi
    Author

    Update from the Office Hours on September 26, 2026 (#3641). The session made several work steps of this issue more concrete. Here is what is new:

    TT-Admins meeting. @sumitsinghwp will invite all team reps and TT-Admins by email in the coming week. It starts monthly and on Zoom, rather than with a fixed weekly slot. It was also suggested to hold a short admin meeting right before the weekly meeting and select the tickets for the Tuesday meeting there.

    Recurring tasks and goal. The named tasks are triage of new issues on GitHub, reviewing Help Scout feedback and creating issues from it, and the meeting itself. The group's first goal is to reduce the number of open issues.

    Ownership. The group itself decides on the format and process of the TT-Admins meeting. The team reps explain and support.

    Short description of the Office Hours. A short description is needed that can be shared with newcomers: what the format is, who can take part, who can moderate and how to get Zoom access. @rfluethi will provide a draft.

    Definition in the handbook. The work step on roles in the handbook is extended: the sessions and the subgroups, such as the TT-Admins or the local Training Teams, should be described with their tasks, goals, members and contact person. This needs to happen soon, because otherwise the people behind these formats lose motivation.

    Suggested additional work steps:

    • Publish the short description of the Office Hours and link it from the handbook
    • Describe the sessions and subgroups in the handbook: tasks, goals, members, contact person
  2. rfluethi commented on Sep 26, 2026

    @rfluethi
    Author

    Suggested description for the Office Hours meeting:

    Long

    What are the Office Hours?

    The Office Hours are a one-hour video call on Zoom, once a month. This is where the team discusses bigger, cross-cutting questions: what needs to change and how. Each session has a topic announced in advance, and there is room for your own questions as well. Whatever is agreed on becomes an issue in the WordPress/Learn repository and is published in the recap on make.wordpress.org/training.

    Who can join?

    Everyone. No registration and no prior experience needed. You'll find the Zoom link in the #training channel on Make WordPress Slack. Questions about content in your language or about your local group are explicitly welcome.

    What if no one in the room can help?

    We note the question and pass it on to the right person. You leave with a name you can reach out to.

    Who moderates?

    Anyone on the team; you don't need to be a Team Representative. The moderator gives everyone the floor, proposes three topics in the weekly Tuesday meeting, and announces the chosen one. If you'd like to moderate, let us know in #training. As moderator, you get access to the team's Zoom account through the TT-Admins (@tt-admins in #training).

    When is the next session?

    Date, time (UTC), topic, moderator, and Zoom link are posted in #training on the Monday before each session.

    What doesn't belong here?

    Going through individual issues, unless they belong to the current topic. That is the job of the TT-Admins meeting.


    Read the full proposal: proposal.md

    Published on the Make WordPress Training blog: Proposal post, February 3, 2026

    Short

    Office Hours: one hour on Zoom once a month, open to everyone. We discuss cross-cutting questions of the Training Team. Each session has an announced topic, and your own questions are welcome, including about your language. If no one can help, we connect you with the right person. Anyone on the team can moderate. Date, time, topic, and Zoom link are posted in #training on the Monday before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions