Community: Some place to store voice recordings from our bi-weekly sessions

[bartsmykla]

Hi everyone!

At our slack channel one of our users (Niels van Brecht / @meauses) suggested to create some space and store there voice recordings from our sessions for people who can't watch videos but would like to listen them like podcasts.

I'm not aware what are requirements to place that kind of recording on Spotify or other places, but I think it would be a great to start with some bucket where we would place that kind of recordings.

What do you think about that?

Bart

P.S.
I'll try to find more information about how to place that recording on Spotify and similar.

[nielsvbrecht]

for administration and clarity purposes...
@bartsmykla as discussed I will pick this up.

[nielsvbrecht]

Hi everyone,

I've done some research the last couple of days and have some ideas on the possibilities or how we can approach this.
We can quite simply create a podcast-like setup which can be re-used or which we can host by /for other SIGs. I think that consuming it in audio would be appreciated by others.

This is what I found and how I believe we can realize it;
The zoom API, once authenticated, allows us to download the audio recording file. We should be able to automate this quite simply (we just need curl and gsutil :) I've already composed a Dockerfile). I haven't been able to test the audio download, but Zoom has the API properly documented.
We can store these audio files (.m4a) in a gcp bucket and host them from there. The size of last meetings recording was 23MB.
To be able to get listed into Google Podcasts and iTunes we need to have an rss file containing info about the episodes (meetings) and a link to the recording file which we can host in the same bucket. This rss file should/could even be versioned in GitHub and pushed to the bucket when updated after a meeting. Updating this files is adding a couple lines of the new episode (title and link to file at the least) and you're done.

For neatness we need to have a logo for the podcast which I created based on the Kubernetes logo (I simply added wg-k8s-infra below it in the same font).
Also we should create a simple index and error.html.

@bartsmykla mentioned that a vanity domain would be the way to go. Which is possible by using a DNS record in the k8s.io zone, it probably would work with the nginx redirect setup, but that would incur additional load on that environment and possibly impact performance.

To set this up properly the following is required;

• A user in Zoom that has API access (minimum to download the audio recording)
• A GCP bucket in the CNCF hosted Infra (we'd need to decide which tier we need)
• Access credentials (service account) to write to this bucket.
• We'd need to add the required files to the GitHub repo.

Let me know your thoughts about this!

[justaugustus]

This sounds like a great idea and it seems like a decent amount of thought has gone into it already!

One thing I'd like us to keep top of mind is how we do moderation here...
How do we handle a bad actor or something sensitive that has to be scrubbed from a recording?

We can do this by editing the videos on YouTube prior to publication, but how will we do the same for audio?
cc: @kubernetes/sig-contributor-experience-feature-requests @kubernetes/youtube-admins @kubernetes/code-of-conduct-committee

[justaugustus]

I think this should be brought to a SIG ContribEx meeting/the mailing list before anything happens on the implementation side.

[parispittman]

might be a weird comment but i listen to our meetings with just audio all the time in a new tab or the youtube app on my phone while i do other things.

you can also upload the audio only file to a team drive/gsuite via zoom api and our zoom admins can figure this out. we asked for a team drive for our gsuite from cncf but it didn't get implemented correctly and i need to do a loop back to figure that out.

re: bad actors: ping a youtube admin via slack and they will trim all videos that need it. we do this regularly both from aesthetics as well as when folks request for sensitive reasons.

[nielsvbrecht]

might be a weird comment but i listen to our meetings with just audio all the time in a new tab or the youtube app on my phone while i do other things.

Not weird, this is how most of us do it as well, because there is no other option.
But the downside of needing to have YouTube open, in the app or browser, is that you have to keep your phone unlocked and you cannot turn your screen off while travelling for example, and you can't have them offline either. Or you would need to have YouTube Premium.

[parispittman]

i do have youtube premium so i guess thats why i never noticed myself thanks for clarifying.

[celanthe]

Happy to help with this however possible! :) I have extensive podcasting experience. :)

[chris-short]

I'm in.

[mrbobbytables]

Follow up from contribex call today (will link when done processing):

• It is not a long term solution, but there are several web services that will convert a youtube video to mp3 (e.g. onlinevideoconverter.com).
• Zapier can automate the publishing of youtube recordings to spotify. There are some other integrations that might be possible as well (soundcloud), but that will require further investigation.

[nielsvbrecht]

Is it an idea to create a separate slack channel for any efforts related to this? Or just create a thread (in which channel?) so we can start any efforts on this topic and share any ideas and start/try-out proof of concepts.

[nikhita]

Or just create a thread (in which channel?) so we can start any efforts on this topic and share any ideas and start/try-out proof of concepts.

sig-contribex would be the right place :)

[thockin]

If we want a GCS bucket, I think that would be appropriate use of infra funds. We'll just need to script the creating of it and figure out permissions

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[spiffxp]

/kind feature
/lifecycle stale
/sig contributor-experience
I transferred this over from k8s.io because this seems a more appropriate venue for a contribex-related issue

[parispittman]

someone with access to contributors@ in contribex can create a public drive for you there. could you figure out how to get them to there?

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.