Run and document Office Hours on September 26, 2026
Open
Nobody has claimed this yet.
Office Hours
- Dominant language
- PHP
- Stars
- 333
- Forks
- 127
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 11
Description
Office Hours session on 2026-26-09.
Responsible Persons
- Moderation: @vasantrajput
- Minute-taking: @andrewssanya
Tasks
Before the meeting
- Select three topics and put them up for choice in the Tuesday meeting
- Announce the chosen focus topic in Slack with sufficient lead time
- Prepare the agenda based on open issues at github.com/rfluethi/wpt-office-hours/issues. Use the templates and the first meeting's notes at #3413 as reference.
- Confirm a note-taker for the meeting
- Set up and test the Zoom link
- Share the agenda link in the #training Slack channel at least 24 hours before the meeting
- Post a reminder in the #training Slack channel before the meeting
During the meeting
- At meeting start: post
<office hour meeting>+ Zoom link in Slack - Moderate the meeting following the agreed recurring agenda structure
- At meeting end: post
</office hour meeting>in Slack
After the meeting
- Write and publish the minutes of the session
Context
The document “Organizing Office Hours Meetings” provides additional information on how to organize the meeting.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with “Organizing Office Hours Meetings” and review the templates plus the first meeting’s notes in #3413. Check the open issues in wpt-office-hours to prepare the agenda, then follow the Before, During, and After meeting checklist. Done means the session is run on September 26, 2026 and its minutes are written and published.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100