chris-short

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

chris-short

{{EntryTitle}}<br>
{{EntryAuthor}}<br>
{{EntryPublished}}<br>
{{EntryUrl}}<br>
<br>
{{EntryContent}}<br>
<br>
From: {{FeedTitle}} via IFTTT

chris-short

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

chris-short

# L-Spine MRI 2024-07-03

## Multiple Levels

Facet degenerative changes — Facet Disease 

## L2-L3

Ligamentum flavum hypertrophy — a condition that occurs when the ligamentum flavum (LF) thickens due to stress on the spine The LF is a ligament that runs along the back of the spinal canal and is made up of elastic fibers that allow it to bend and stretch as the spine moves. When the LF thickens, it can compress the spinal cord or nerves, which can cause pain and even disability.

chris-short

1. macOS fonts

chris-short

sdb
More info...
 Error: Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/middlewared/job.py", line 426, in run
    await self.future
  File "/usr/lib/python3/dist-packages/middlewared/job.py", line 461, in __run_body
    rv = await self.method(*([self] + args))
  File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1186, in nf
    res = await f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1318, in nf

chris-short

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).

chris-short

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.

chris-short

failed to render shortcode "imgproc": failed to process shortcode: "/var/folders/4b/l7c40ks90zqbr28948qnc1hc0000gs/T/hugo_cache/modules/filecache/modules/pkg/mod/github.com/google/[email protected]/layouts/shortcodes/imgproc.html:9:34": execute of template failed: template: shortcodes/imgproc.html:9:34: executing "shortcodes/imgproc.html" at <$original.Fill>: nil pointer evaluating resource.Resource.Fill

chris-short

community/committee-steering/governance/sig-governance.md:[Marketing Council]: /communication/marketing-team/role-handbooks/council.md
community/communication/calendar-guidelines.md:> https://github.com/kubernetes/community/tree/master/communication/marketing-team
community/communication/marketing-team/CHARTER.md:[Marketing Council](/communication/marketing-team/role-handbooks/council.md)
community/communication/marketing-team/role-handbooks/storytellers.md:* Open a [Contributor Comms Requests issue](https://github.com/kubernetes/community/issues) to share your blog idea, or attend an [Upstream Marketing team](https://github.com/kubernetes/community/tree/master/communication/marketing-team) meeting to discuss it ahead of time
community/communication/marketing-team/role-handbooks/storytellers.md:  * There is not a single canonical format for documents, but we do have [guidelines for effective articles](https://github.com/kubernetes/community/blob/master/communication/marketing-team/blog-guidelines.md#how-to-wr