You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Through the support channel, we often receive requests and/or notifications about events/workshops that communities would like to run on their hubs. While we provide information on how a community should inform us and/or ask for help, and an engineering checklist for preparing for an event - we don't have any guidance on how a support triager should handle these requests when they come in. The implicit process is that an event template issue is opened, and as a part of that the event is added to an event calendar. We also lack a process to surface these events for refinement and committed to an iteration in time for the event.
Proposal
Write a policy/runbook describing how support triagers are expected to handle event tickets and what the expectations of them are
Develop a process for surfacing these events so that they can be scheduled and committed to iterations in an appropriate length of time
Updates and actions
No response
The text was updated successfully, but these errors were encountered:
Context
Through the support channel, we often receive requests and/or notifications about events/workshops that communities would like to run on their hubs. While we provide information on how a community should inform us and/or ask for help, and an engineering checklist for preparing for an event - we don't have any guidance on how a support triager should handle these requests when they come in. The implicit process is that an event template issue is opened, and as a part of that the event is added to an event calendar. We also lack a process to surface these events for refinement and committed to an iteration in time for the event.
Proposal
Updates and actions
No response
The text was updated successfully, but these errors were encountered: