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

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.