Hello, and welcome, everyone, to the Friday, $DATE edition of the Contributor Coms Team Meeting.

As a reminder, this meeting operates under a code of conduct which essentially says to be respectful of your fellow speakers and attendees. And generally be excellent to each other.

Here at the beginning of the call, we like to offer an opportunity for anyone on the call to introduce themselves, if you'd like to, totally optional. I like to use it as an excuse to explain what the meeting is.

Hello everyone, I'm $NAME, and I am one of the co-leads of the Contributor Communications subproject, which is what this meeting is about and our purpose as a group is to make sure that folks within the contributor community and open source Kubernetes know about things going on that they really ought to know about. Also, to make sure that folks outside of the contributor community know about the awesome work that contributors are doing. During this meeting today, we'll go over various projects, and things going on that

Do not hallucinate.
Do not lie.
Do not make up facts.
Try not to contradict yourself.
I'm not a programmer by trade but I prefer Golang.
Answer all questions in the style of a wise, friendly colleague, using informal language.

My thoughts:

• Casual conversations beat super structured but, there has to be a minimal bullet list script of the things to be covered and if we can figure out how long each part takes
• Standard intros and outros throughout content make people feel at home; video bumpers and host intro should be consistent
• What is our call to action? If it’s “Join us!” then we have to be ready to give folks work (I suggest docs as a starting point unless the audience has ideas where they want to join); good first issues help a little here but can lead to cookie licking
• Consistency: we’re going to do some streams at first with a small audience and that’s okay; setting up a consistent schedule forecasted well in advance with a calendar or invite helps pull people in because they get reminders and build a habit around it
• Content: Either getting started guides (which are always popular; they also can be done per SIG) or HOWTOs; interview style streams don't draw a crowd but they can draw media
• Video for promotion: The

Go here: https://chrisshort.net/micro/social-media-muted-words/

Congratulations on another successful legislative session. As you're likely back home and preparing for the holidays, much like I am, I would like you to remember one thing, if possible.

Our friends in Ukraine celebrate their holidays on the cusp of what could be the deadliest winter in Ukranian history thanks to ongoing Russian aggression against one of our allies in the region. We owe it to our Ukranian friends to give them the capabilities to put Russia at a standoff distance of at least 150 miles. This way the Ukranian Army can push Russian supply lines to collapse and force Russian commanders in Ukraine to endure ongoing bombardment and certain death or our ultimate goal, permanent retreat and a restoration of peace.

I implore you to think of the efforts of those simply trying to go about their daily lives but live under continued attack by a bully and a thug in Moscow (who is also an enemy of ours).

A context switch is the process of storing and restoring the state of a CPU or a device so that multiple tasks can share the same hardware resources. In a computer operating system, a context switch occurs when the operating system kernel switches the execution of a task from one process to another.

When a context switch occurs between the kernel and user space, it can be more expensive in terms of performance because it requires the kernel to perform additional tasks. These tasks include:

Saving and restoring the state of the CPU registers, including the program counter, stack pointer, and any other relevant registers.

Saving and restoring the kernel stack, which is used to store temporary data and function calls made by the kernel.

Updating the process control block (PCB) for the current process to reflect the new state of the task.