From 20f0061e04f26b6c9c869680515548d6a47b98c5 Mon Sep 17 00:00:00 2001 From: Nigel Brown Date: Wed, 22 Apr 2026 11:44:50 -0400 Subject: [PATCH 1/8] Create video post issue template Added a template for new video post issues to streamline submissions. Signed-off-by: Nigel Brown --- .github/ISSUE_TEMPLATE/video_template.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/video_template.md diff --git a/.github/ISSUE_TEMPLATE/video_template.md b/.github/ISSUE_TEMPLATE/video_template.md new file mode 100644 index 00000000..d49b3625 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/video_template.md @@ -0,0 +1,24 @@ +--- +name: 🎥 New Video post +about: Create a video post +title: "[VIDEO POST] " +labels: 'video-post, untriaged' +assignees: '' +--- + +**New Video Post** + +This is an issue created to propose a video posted to our YouTube page. Make sure to fill out all the fields so the team can best plan to sequence, edit, and publish your post in a timely manner. +Please replace everything in `[]` before submitting. + +**What is your proposed topic?** +[Please include a 1-2 sentence description of the content of the video]. + +**Who is creating this video post?** +[Github alias of who will be creating and responsible for addressing updates on the blog.] + +**What is your ideal publishing date?** +[Please list a date that is at least 5 business days from today. Due to other pending video posts, review time, and project events, publish dates are best effort.] + +**Is this video dependent on something else?** +[Examples: the video needs to be published before an event, the video publishing date depends on a software release date, etc.] From 401d906aef96ed258345b033df21a552c3f9f463 Mon Sep 17 00:00:00 2001 From: Nigel Brown Date: Wed, 29 Apr 2026 14:26:26 -0400 Subject: [PATCH 2/8] Creates Video Contribution Guidelines Uses blog submission guidelines as framework. Signed-off-by: Nigel Brown --- VIDEO_CONTRIBUTION_LIFECYCLE.md | 43 +++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 VIDEO_CONTRIBUTION_LIFECYCLE.md diff --git a/VIDEO_CONTRIBUTION_LIFECYCLE.md b/VIDEO_CONTRIBUTION_LIFECYCLE.md new file mode 100644 index 00000000..1b1a30d0 --- /dev/null +++ b/VIDEO_CONTRIBUTION_LIFECYCLE.md @@ -0,0 +1,43 @@ +# Contributing a Video to the Valkey YouTube Channel + +You are welcome to contribute a video for Valkey YouTube Channel. +The contribution model is lightweight, transparent, and uses well-understood open source processes. + +## Step 1: Ideation + +The first step is to share your idea with the Valkey community through a GitHub issue. +In the issue articulate what topic you want to create a video about and a general overview. +The community will evaluate your idea to understand if it fits into the Valkey story on the Valkey YouTube page and doesn’t overlap with existing or in-process content. +The maintainers will provide feedback as needed. + +Strictly speaking, you can forego this step and contribute a video directly as a pull request. +However, if you don’t get the feedback from the community, you run the risk of doing work that doesn’t translate efficiently (or at all) into a video. + +## Step 2: Creating the Video + +A few video tips: + +1. It may be helpful to create a script, write up, treatment, or description to share with the community before making the video +2. Highly technical is fine but understand that the Valkey YouTube Channel is watched by a variety of skill levels: the best posts make complex topics easy to understand. +3. The Valkey YouTube Channel is not a commercial space; you can talk about services and products as long as a) you’re not actively selling/promoting and b) the subject matter is directly related to the use of Valkey. + 1. Acceptable Example: A video that describes the lessons learned about operating Valkey at scale gleaned from a Valkey service provider. + 2. Unacceptable Example: A video that describes the advantages of running Valkey through a specific service. +4. Talk about Valkey. +There are a ton of things to say about Valkey without venturing into comparisons with other products and projects. +5. Have a call-to-action. +What do you want your viewers to do next after they finish your video? The call-to-action can be something like asking a users to contribute, try some sample code, or come to an event. +You can even just invite viewers to consume related content. + +## Step 3: Write about the video + +Videos on YouTube need to have a description. + +You may opt to add a bio about whoever is creating the video. +The bio should be 1-2 paragraphs in length and should tell the viewer who you are. +Additionally, use the space to link yourself to the community: what makes you a person the viewer should watch and spend time on. + +## Step 4: From creation to publishing + +After your video is made, the content moderators will review the post. +They may have feedback for you and ask you to make changes. +Once everyone is satisfied with the post, the YouTube admins upload it to the YouTube Channel From cf5922122adf548e0f29a830acc72c9e91d532a4 Mon Sep 17 00:00:00 2001 From: Nigel Brown Date: Wed, 29 Apr 2026 14:28:37 -0400 Subject: [PATCH 3/8] Revise creator section in video template minor text fixes Signed-off-by: Nigel Brown --- .github/ISSUE_TEMPLATE/video_template.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/video_template.md b/.github/ISSUE_TEMPLATE/video_template.md index d49b3625..a653e373 100644 --- a/.github/ISSUE_TEMPLATE/video_template.md +++ b/.github/ISSUE_TEMPLATE/video_template.md @@ -14,8 +14,8 @@ Please replace everything in `[]` before submitting. **What is your proposed topic?** [Please include a 1-2 sentence description of the content of the video]. -**Who is creating this video post?** -[Github alias of who will be creating and responsible for addressing updates on the blog.] +**Who is creating this video?** +[GitHub alias of who will be creating and responsible for addressing updates on the video.] **What is your ideal publishing date?** [Please list a date that is at least 5 business days from today. Due to other pending video posts, review time, and project events, publish dates are best effort.] From e730f87e8e854fd50f802e2781af43a7f2262fa0 Mon Sep 17 00:00:00 2001 From: Nigel Brown Date: Thu, 14 May 2026 17:26:48 -0400 Subject: [PATCH 4/8] Enhance video submission template with clarifications Updated the video template to clarify submission instructions and added a confirmation checkbox for content review. Signed-off-by: Nigel Brown --- .github/ISSUE_TEMPLATE/video_template.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/video_template.md b/.github/ISSUE_TEMPLATE/video_template.md index a653e373..0054534f 100644 --- a/.github/ISSUE_TEMPLATE/video_template.md +++ b/.github/ISSUE_TEMPLATE/video_template.md @@ -9,7 +9,7 @@ assignees: '' **New Video Post** This is an issue created to propose a video posted to our YouTube page. Make sure to fill out all the fields so the team can best plan to sequence, edit, and publish your post in a timely manner. -Please replace everything in `[]` before submitting. +Please replace everything in `[]` before submitting. **What is your proposed topic?** [Please include a 1-2 sentence description of the content of the video]. @@ -22,3 +22,5 @@ Please replace everything in `[]` before submitting. **Is this video dependent on something else?** [Examples: the video needs to be published before an event, the video publishing date depends on a software release date, etc.] + +- [] **Please check to confirm that your content has been reviewed by all necessary groups at your company, including, but not limited to legal, marketing, public relations/communications and other engineering teams. By checking yes, you understand that the Linux Foundation is not responsible for ensuring these teams review.** From 914366866e74519544cf3d61c20fac2ae55e0041 Mon Sep 17 00:00:00 2001 From: Nigel Brown Date: Thu, 14 May 2026 17:35:21 -0400 Subject: [PATCH 5/8] Update video post template title placeholder Signed-off-by: Nigel Brown --- .github/ISSUE_TEMPLATE/video_template.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/video_template.md b/.github/ISSUE_TEMPLATE/video_template.md index 0054534f..6c775497 100644 --- a/.github/ISSUE_TEMPLATE/video_template.md +++ b/.github/ISSUE_TEMPLATE/video_template.md @@ -1,7 +1,7 @@ --- name: 🎥 New Video post about: Create a video post -title: "[VIDEO POST] " +title: "[VIDEO POST] " labels: 'video-post, untriaged' assignees: '' --- From 750876e7d35a4a305bbf012a21238ad14b47f1b8 Mon Sep 17 00:00:00 2001 From: Nigel Brown Date: Thu, 14 May 2026 17:36:38 -0400 Subject: [PATCH 6/8] Fix formatting in video_template.md Signed-off-by: Nigel Brown --- .github/ISSUE_TEMPLATE/video_template.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/video_template.md b/.github/ISSUE_TEMPLATE/video_template.md index 6c775497..cb374e28 100644 --- a/.github/ISSUE_TEMPLATE/video_template.md +++ b/.github/ISSUE_TEMPLATE/video_template.md @@ -23,4 +23,6 @@ Please replace everything in `[]` before submitting. **Is this video dependent on something else?** [Examples: the video needs to be published before an event, the video publishing date depends on a software release date, etc.] -- [] **Please check to confirm that your content has been reviewed by all necessary groups at your company, including, but not limited to legal, marketing, public relations/communications and other engineering teams. By checking yes, you understand that the Linux Foundation is not responsible for ensuring these teams review.** + + +- [ ] **Please check to confirm that your content has been reviewed by all necessary groups at your company, including, but not limited to legal, marketing, public relations/communications and other engineering teams. By checking yes, you understand that the Linux Foundation is not responsible for ensuring these teams review.** From f4d1126b1cf69ae5a07c533c5ea8556465387d6f Mon Sep 17 00:00:00 2001 From: Nigel Brown Date: Thu, 14 May 2026 17:37:43 -0400 Subject: [PATCH 7/8] Refine guidelines for video contributions on Valkey Consolidate points about discussing Valkey and call-to-action in video contributions. Signed-off-by: Nigel Brown --- VIDEO_CONTRIBUTION_LIFECYCLE.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/VIDEO_CONTRIBUTION_LIFECYCLE.md b/VIDEO_CONTRIBUTION_LIFECYCLE.md index 1b1a30d0..3da48dd5 100644 --- a/VIDEO_CONTRIBUTION_LIFECYCLE.md +++ b/VIDEO_CONTRIBUTION_LIFECYCLE.md @@ -22,11 +22,8 @@ A few video tips: 3. The Valkey YouTube Channel is not a commercial space; you can talk about services and products as long as a) you’re not actively selling/promoting and b) the subject matter is directly related to the use of Valkey. 1. Acceptable Example: A video that describes the lessons learned about operating Valkey at scale gleaned from a Valkey service provider. 2. Unacceptable Example: A video that describes the advantages of running Valkey through a specific service. -4. Talk about Valkey. -There are a ton of things to say about Valkey without venturing into comparisons with other products and projects. -5. Have a call-to-action. -What do you want your viewers to do next after they finish your video? The call-to-action can be something like asking a users to contribute, try some sample code, or come to an event. -You can even just invite viewers to consume related content. +4. Talk about Valkey. There are a ton of things to say about Valkey without venturing into comparisons with other products and projects. +5. Have a call-to-action. What do you want your viewers to do next after they finish your video? The call-to-action can be something like asking a users to contribute, try some sample code, or come to an event. You can even just invite viewers to consume related content. ## Step 3: Write about the video From 918ab36617f42cc007b7eea4851197b30d7fc3bb Mon Sep 17 00:00:00 2001 From: Nigel Brown Date: Tue, 26 May 2026 13:04:27 -0400 Subject: [PATCH 8/8] minor text fixes Corrected grammatical error in the call-to-action section. Signed-off-by: Nigel Brown --- VIDEO_CONTRIBUTION_LIFECYCLE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VIDEO_CONTRIBUTION_LIFECYCLE.md b/VIDEO_CONTRIBUTION_LIFECYCLE.md index 3da48dd5..5450b3cc 100644 --- a/VIDEO_CONTRIBUTION_LIFECYCLE.md +++ b/VIDEO_CONTRIBUTION_LIFECYCLE.md @@ -23,7 +23,7 @@ A few video tips: 1. Acceptable Example: A video that describes the lessons learned about operating Valkey at scale gleaned from a Valkey service provider. 2. Unacceptable Example: A video that describes the advantages of running Valkey through a specific service. 4. Talk about Valkey. There are a ton of things to say about Valkey without venturing into comparisons with other products and projects. -5. Have a call-to-action. What do you want your viewers to do next after they finish your video? The call-to-action can be something like asking a users to contribute, try some sample code, or come to an event. You can even just invite viewers to consume related content. +5. Have a call-to-action. What do you want your viewers to do next after they finish your video? The call-to-action can be something like asking a user to contribute, try some sample code, or come to an event. You can even just invite viewers to consume related content. ## Step 3: Write about the video