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
Speakers are often confused that their video is already online.
Changing email text to tell them, and also showing in the web ui that their talk was approved with a certain info, changes, etc at that URL would help.
The text was updated successfully, but these errors were encountered:
The description of the issue is quite terse, so I am not sure I fully understand.
Speakers are often confused that their video is already online.
What's causing the confusion? Is it the last email of the process, the one with subject "RELEASED: Your FOSDEM 2019 talk titled <talk_title>"?
Or are they simply surprised that somoeone else has reviewed their video before them?
Changing email text to tell them
The current email does say the talk has been "transcoded and uploaded to ". We can work on the content to make things clearer, but the issue description makes it sound as if the email doesn't say anything. Or maybe I am misunderstanding.
also showing in the web ui that their talk was approved with a certain info, changes, etc at that URL would help.
I agree that a link straight to the video file is probably not the best option, but creating a whole page just for this might be overkill. Before doing that, I would try linking to the session page that contains the video (e.g. https://fosdem.org/2019/schedule/event/open_source_design_in_trenches/). A simple layout change in the session page (displaying the video above the session description, as shown in the attached image), might help convey that the video is now published and publicly avaialable.
Speakers are often confused that their video is already online.
Changing email text to tell them, and also showing in the web ui that their talk was approved with a certain info, changes, etc at that URL would help.
The text was updated successfully, but these errors were encountered: