-
Notifications
You must be signed in to change notification settings - Fork 90
Create video post issue template #509
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
pnbrown
wants to merge
8
commits into
main
Choose a base branch
from
pnbrown-patch-1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
20f0061
Create video post issue template
pnbrown 401d906
Creates Video Contribution Guidelines
pnbrown cf59221
Revise creator section in video template
pnbrown e730f87
Enhance video submission template with clarifications
pnbrown 9143668
Update video post template title placeholder
pnbrown 750876e
Fix formatting in video_template.md
pnbrown f4d1126
Refine guidelines for video contributions on Valkey
pnbrown 918ab36
minor text fixes
pnbrown File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| --- | ||
| name: 🎥 New Video post | ||
| about: Create a video post | ||
| title: "[VIDEO POST] <Put your tentative video post title here>" | ||
| 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?** | ||
| [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.] | ||
|
|
||
| **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.** | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| # 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. | ||
|
pnbrown marked this conversation as resolved.
|
||
|
|
||
| ## 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 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 | ||
|
|
||
| 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 | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.