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
The Info field makes it easy for us to annotate the room streams, based on the preference.
Additionally, it would be nice to have a collapsible help where we can provide guidance of how to use the Info field and a flagging convention to make it easier to communicate complex states concisely, aka keep things on a single line.
Currently, it's a bit haphazard
Example: showing state of room stream cutting
Example: showing room topics and some annotation
So we have to define what it is we want to encode about each room stream, maybe come up with a set of symbols or progression that would let us know:
room topic
any technical issues with room stream - provides great training example for monitoring, remind us of A/V issues for post-mortem, point out technical issue with info in signs.xml and the schedule
reasons we can't publish room stream - mostly workshops are unusable or not recorded
has it been cut
has it been published
has room stream been unlisted, which means it has been completely dealt with
Once we come up with an encoding, we will probably need a legend or collapsible help, so we can consistently encode it correctly and others can understand the code.
The text was updated successfully, but these errors were encountered:
The Info field makes it easy for us to annotate the room streams, based on the preference.
Additionally, it would be nice to have a collapsible help where we can provide guidance of how to use the Info field and a flagging convention to make it easier to communicate complex states concisely, aka keep things on a single line.
Currently, it's a bit haphazard
Example: showing state of room stream cutting
Example: showing room topics and some annotation
So we have to define what it is we want to encode about each room stream, maybe come up with a set of symbols or progression that would let us know:
Once we come up with an encoding, we will probably need a legend or collapsible help, so we can consistently encode it correctly and others can understand the code.
The text was updated successfully, but these errors were encountered: