Office hours notes from a maintainer who refuses drive-by demands

They start office hours with a published agenda: triage, deep dives, and community announcements. If someone drops a unrelated production outage into chat, they acknowledge it and point to the enterprise support channel.

They batch similar questions. Three people asking about the same release note get one threaded answer they can subscribe to.

They end on time even if the queue is not empty. The remainder becomes async homework with a clear deadline.

They publish anonymized themes afterward. That post becomes the FAQ seed for the next month.

None of this is glamorous. It is the infrastructure that keeps contributors from burning out.