Replies: 4 comments
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
(Based on conversations with @flynnliz)
After the main scheduling effort, Sessions are moved from a SchedWait to Sched state by an action called "Send Notifications".
Beyond that point, scheduling new sessions (for things like AD Office Hours) becomes cumbersome. It is hard to remember to go back and rerun "Send Notifications" and there are some new ways we are using Session (with non wg/rg groups) that the workflow is likely ignoring.
What would a better workflow look like during the period from when the bulk of the wg/rg Sessions are marked Scheduled through the meeting?
Beta Was this translation helpful? Give feedback.
All reactions