Audio recordings of CNCF Security Papers
Description: Many members of the cloud native community either cannot read through our papers or have trouble making time to read through them. This is a proposal to initiate audio recordings for sections of CNCF Security Papers produced by this group and make them available to the community to increase accessibility.
Impact: Support and extend our community
- Some members of our community experience long COVID symptoms that interfere with their ability to read deliverables of the group.
- We would like our information to be welcoming to the visually impaired. In other circumstances, providing critical content in written form only may be excluding a community of security and cloud native professionals. While screen readers and text-to-software can assist in this, it is not conversational and in some cases difficult to cover technical terms, making it less appealing.
Scope: the scope can be separated into different parts, which ideally be contributed by a few different people
- a few community members to read sections of a paper in their native language as it is written (or translated to). It is suggested these be broken into heading sections of the paper, to make digesting the content presented time-bound and easier to pick up.
- a place to host the recordings. It is recommended we engage the CNCF to determine their ability to assist, working with a Security TAG member to coordinate requirements.
See also:
- CNCF Slack channel: #tag-security-audio
- project plan/schedule - planing in progress
TO DO
- [x] SIG Leadership Representative: Sarah Allen (@ultrasaurus)
- [X] Project leader: Chase Pettet (@chasemp) @ragashreeshekar
- [x] Voices: Chase Pettet (@chasemp), Sarah Young (@sarah-yo), Emily Fox (@TheFoxAtWork), @ashutosh-narkar, @TheFoxAtWork, @raesene, @Boes-man ? TBD more?
- [x] Editing: Alex Floyd Marshall (@apmarshall)
- [X] Create Slack channel for coordinating project #tag-security-audio
- [X] Kick-off meeting (July 9, 2021)
- [x] Figure out volunteers can upload audio recordings, accessed by other volunteers for production/QA (@ultrasaurus submitted servicedesk ticket#857 -- shared Google Drive folder ask @chasemp if you need access
- [ ] see google doc for detailed schedule and recording assignments
What a great idea. +1. I would be willing to be recorded if that's a need.
My first "real" job was as an audio engineer, and I still do a fair amount of audio editing on the side. Would be happy to engineer for these recordings if/as needed.
+1! Nice! I used to be a DJ in another life and now I'm helping @dcomas with the Cloud Native Security Talk Podcast. Happy to help here and also do the same with the pt-BR translation as well once that's done!
I updated the description a bit to emphasize outreach to visually impaired, as well as some formatting as lists :)
I'm also part of the target audience, and would be delighted to test drive the content when it is ready!
I volunteered to be SIG Leadership Representative and added in list of other helpers. @magnologan said he could lead if no one volunteers before he finishes his current projects for the group. This could get started sooner if there's someone else willing to take a leadership role in pulling this together. I'm sure we could get CNCF staff help if there are logistical requirements or expenses -- we just need someone to take the lead on figuring out the TODO list and project managing.
I'm reaching out to our APAC members to see if this is of interest.
Good thought! I will mention this in the next meeting!
As I've discussed with @ultrasaurus on Slack over DM, I'd love to take the lead on this, but I'm currently with too many projects that I'd like to finish, such as the Security Pals pilot program the translation of the CNSWP to pt-BR. So, if there are no leads by June, then I can probably take it. =)
If I wanted to JDI and record the thing, does that raise objections? (this would be a first outing fraught with learning I imagine) If not I'll have time next week.
I thought about it as well. The group should define how to break up the body of the papers into manageable chunks. multiple voices with quality recording also engages listeners (so as to not fall asleep on variety)
@TheFoxAtWork that makes sense. Maybe I'll take the summary section and just do that as a conversation piece / to get the ball rolling.
@chasemp if you record the whole thing, I would listen to it! Then the audio engineer can take whichever section they like best from yours (or multiple sections).
btw: @sarah-yo also volunteered to record! I like the idea of having a diversity of voices from different English-speaking countries.
@chasemp has volunteered as project leader 🥇
According to our governance process, the next step to move this from a "proposal" to a "project" is to raise it for discussion at one of our meetings.
@chasemp can you put it on the agenda for an upcoming meeting?
@ultrasaurus Sure can.
Also, in the spirit of brainstorming possible solutions in the spirit of making something quickly available and iterating. I thought it might be fun to have a live reading with multiple readers queued up and then @apmarshall could edit the audio recording after (with potentially re-recording bits as needed).
Happy to volunteer !
@matthewflannery says we can blue steel, I am in.
Also happy to voice.
I am getting my bearings for issues in github, as the assignee am I meant to be able to edit the description?
At the moment, I either cannot or don't understand how :D
@chasemp it's a bit hard to find (or maybe I was incorrect about permissions). Do you have a three-dot menu with edit option in top-right of description area?

I'll be pushing this proposal to Project and placing in the Planned and Scheduled
I'd be happy to try and contribute some voice reading, if that's helpful, I've got an accent I don't think we have yet (west coast Scotland)
@chasemp I would recommend putting together a tentative schedule and creating a slack channel "#tag-security-audio" to begin coordination. Be sure to invite commenters on the issue.
@chasemp it's a bit hard to find (or maybe I was incorrect about permissions). Do you have a three-dot menu with edit option in top-right of description area?
Indeed, I see the menu but have no rights beyond a normal comment (quote & reply)
@chasemp I would recommend putting together a tentative schedule and creating a slack channel "#tag-security-audio" to begin coordination. Be sure to invite commenters on the issue.
Channel is created. Anyone here who I could find in slack I added. I'll tinker with a schedule, and a potential breakdown.
FWIW there is a group that does audiobooks for works in the public domain and they have a good primer on beginning recording with free tools here
@chasemp I sent a note to #tag-security-triage slack channel about this. Maybe things changed in github or I just got confused and forgot. I'll try to keep the description up-to-date. Free to ping me on slack if I fall behind and miss something!
@Boes-man sorry I don't understand the blue steel reference. Perhaps https://www.dictionary.com/e/fictional-characters/blue-steel/ ? If so, feel free to make whatever facial expression you like while doing audio recording! I'll put you down as a voice volunteer. Not sure what your real name is -- pls join the CNCF slack channel #tag-security-audio if you aren't already there
/cc @matthewflannery
I'm happy to collaborate as well, Indian accent :D
Getting the wheels turning here. In the tag-security-audio channel is a document linked and a doodle poll for a kickoff meeting for those interested.