Mod on Call
The Mod on Call is the @Moderator responsible for closing out tickets and updating the GitHub records for the week.
How It Works​
- One @Moderator is assigned each week as the Mod on Call.
- Responsibility rotates through the Moderator team in a fixed order.
- The schedule is tracked via a Google Sheet so each Moderator knows when they are expected to handle ticket logging.
- A smaller extraction from the full schedule is pinned in đŸ“™moderators.
Schedule Swaps​
If a @Moderator cannot complete their assigned week:
- They must arrange a swap with another Moderator
- Update the roster accordingly
- Alternatively, another Moderator may volunteer to cover the assigned week instead of a swap
Responsibilities​
The Mod on Call for the week is responsible for:
- Closing out completed tickets throughout the week
- Updating the GitHub Warning Book with all logged actions
- Ensuring all records are properly documented before the week ends
Logging to GitHub
For instructions on how to log tickets to the GitHub Warning Book, see the GitHub Records page.
Example Schedule​
| Week | Date Start | Date End | Moderator | Notes |
|---|---|---|---|---|
| 47 | November 22 | November 28 | Moderator #1 | |
| 48 | November 29 | December 5 | Moderator #2 | LOA |
| 49 | December 6 | December 12 | Moderator #3 | |
| 50 | December 13 | December 19 | Moderator #4 | SICK |
| 51 | December 20 | December 26 | Moderator #5 | |
| 52 | December 27 | January 2 | Moderator #6 |
Check the Schedule
Always check the pinned Google Sheet in đŸ“™moderators to know when your week is coming up!