On the last Kubeflow Community call we discussed what YouTube channel we should use to upload WG calls.
We can create separate YouTube Channel: Kubeflow Working Groups for all working groups + community calls, and use the main Kubeflow YouTube channel: https://www.youtube.com/@Kubeflow for release updates, summits, global announcements, etc.
That will help us to keep the main Kubeflow YouTube channel clean, and give users single place to view all recordings from other community calls.
Currently, each WG use different resources to upload videos:
Also, we should discuss how we can automate the publishing for the WG calls?
Thoughts @kubeflow/wg-training-leads @kubeflow/wg-automl-leads @kubeflow/wg-notebooks-leads @kubeflow/kubeflow-steering-committee @kubeflow/wg-pipeline-leads @kubeflow/wg-data-leads @kubeflow/wg-manifests-leads ?
On the last Kubeflow Community call we discussed what YouTube channel we should use to upload WG calls.
We can create separate YouTube Channel:
Kubeflow Working Groupsfor all working groups + community calls, and use the main Kubeflow YouTube channel: https://www.youtube.com/@Kubeflow for release updates, summits, global announcements, etc.That will help us to keep the main Kubeflow YouTube channel clean, and give users single place to view all recordings from other community calls.
Currently, each WG use different resources to upload videos:
Also, we should discuss how we can automate the publishing for the WG calls?
Thoughts @kubeflow/wg-training-leads @kubeflow/wg-automl-leads @kubeflow/wg-notebooks-leads @kubeflow/kubeflow-steering-committee @kubeflow/wg-pipeline-leads @kubeflow/wg-data-leads @kubeflow/wg-manifests-leads ?