From Fedora Project Wiki
(Created page with "This page is just a brain storm on the "How to submit a video for inclusion into Fedora videos". There's already a page up, but I feel a step by step guide is warranted to get pe...")
 
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{admon/note|Needs love!|The text is just an idea dump. Its terse, not easy to read. We need to get this into more user friendly language + format}}
This page is just a brain storm on the "How to submit a video for inclusion into Fedora videos". There's already a page up, but I feel a step by step guide is warranted to get people started easily.
This page is just a brain storm on the "How to submit a video for inclusion into Fedora videos". There's already a page up, but I feel a step by step guide is warranted to get people started easily.


Line 6: Line 8:
* Does it need a video or a screen cast?
* Does it need a video or a screen cast?
* Do you have the required hardware?
* Do you have the required hardware?
* * Webcam/Video recorder
** Webcam/Video recorder
* * Microphone
** Microphone
* * Test them using Cheese!
** Test them using Cheese!
* Do you have the required software?
* Do you have the required software?
* * Screen casting: LIST HERE
** Screen casting: LIST HERE
* * Video editing: LIST HERE
** Video editing: LIST HERE
* Plan your video
* Plan your video
* * What are you going to focus on: an entire application, a feature of an application, how to use it for a specific task?
** What are you going to focus on: an entire application, a feature of an application, how to use it for a specific task?
* * What is the targeted audience: dummies, advanced? (We should list this in the video header too!)
** What is the targeted audience: dummies, advanced? (We should list this in the video header too!)
* Write up a transcript
* Write up a transcript
* * Writing a transcript before making a screen cast helps in syncing the audio and video up properly.
** Writing a transcript before making a screen cast helps in syncing the audio and video up properly.
* * The transcript needs to be submitted to aid us in addition of subtitles.
** The transcript needs to be submitted to aid us in addition of subtitles.
* * A video will need to be transcribed later, of course.  
** A video will need to be transcribed later, of course.  
* Record the audio
* Record the audio
* * This is where the transcript comes in handy
** This is where the transcript comes in handy
* * Sit in a quiet environment. Keep a bottle of water with you.
** Sit in a quiet environment. Keep a bottle of water with you.
* * Speak clearly, pronouncing each word with as much clarity as possible.
** Speak clearly, pronouncing each word with as much clarity as possible.
* * Time your sentences/clauses correctly to sync with the activities in the video.
** Time your sentences/clauses correctly to sync with the activities in the video.
* License it correctly: CC by SA unported LINK EXPLAINING LICENSE
* License it correctly: CC by SA unported LINK EXPLAINING LICENSE
* Add a license declaration file  
* Add a license declaration file  
* Tar it all up!
* Tar it all up!
* * Video/screen cast
** Video/screen cast
* * Audio
** Audio
* * License  
** License  
* * Anything you'd want us to keep in mind while we process it for publication.
** Anything you'd want us to keep in mind while we process it for publication.
* Send it to us!
* Send it to us!
* * You can email us the material, but since we expect it to be large in size, we prefer if you upload it all someplace and email us the link instead.
** You can email us the material, but since we expect it to be large in size, we prefer if you upload it all someplace and email us the link instead.
* Wait for video to be published!
* Wait for video to be published!


Line 39: Line 41:
* Receive video from submitter
* Receive video from submitter
* Check files
* Check files
* * Video
** Video
* * Audio
** Audio
* * License declaration
** License declaration
* * Special comments
** Special comments
* Test video
* Test video
* * Is the file good?
** Is the file good?
* * Is the quality of the video good? Resolution/clarity/colours
** Is the quality of the video good? Resolution/clarity/colours
* * Does the transcript sync properly with the video?
** Does the transcript sync properly with the video?
* Test audio
* Test audio
* * Is the file good?
** Is the file good?
* * Is the audio clear
** Is the audio clear
* * Does the transcript follow the audio properly and in sync?
** Does the transcript follow the audio properly and in sync?
* Videos team reviews video and gives karma
* Videos team reviews video and gives karma
* * If karma is above threshold, proceed to processing and publishing
** If karma is above threshold, proceed to processing and publishing
* * Otherwise contact submitter with suggestions  
** Otherwise contact submitter with suggestions  
* Combine the audio, video
* Combine the audio, video
* * Test combined form
** Test combined form
* Add branding
* Add branding
* * Add starting template
** Add starting template
* * Contains title, author, targeted audience, license
** Contains title, author, targeted audience, license
* * Add ending template
** Add ending template
* * Contains author, feedback link, audience, permalink, rss feed link to channel
** Contains author, feedback link, audience, permalink, rss feed link to channel
* Translate transcripts  
* Translate transcripts  
* Compose subtitles file (srt files. LINK ON HOW TO DO THIS HERE)
* Compose subtitles file (srt files. LINK ON HOW TO DO THIS HERE)
* Compose subtitles for translations
* Compose subtitles for translations
* Videos team checks finalized video and gives it karma
* Videos team checks finalized video and gives it karma
* * If karma above threshold, publish video.
** If karma above threshold, publish video.
* * Reprocess with changes/suggestions.
** Reprocess with changes/suggestions.
* Check published video.
* Check published video.
* Market published video.
* Market published video.
Line 75: Line 77:
* Trac instance required to keep it organized?
* Trac instance required to keep it organized?
* Reward submitters/videos team helpers somehow? Can give them Badges? "Screencast ninja, vim ninja" etc?
* Reward submitters/videos team helpers somehow? Can give them Badges? "Screencast ninja, vim ninja" etc?
[[Category: Fedora_videos]]

Latest revision as of 11:07, 20 February 2012

Needs love!
The text is just an idea dump. Its terse, not easy to read. We need to get this into more user friendly language + format

This page is just a brain storm on the "How to submit a video for inclusion into Fedora videos". There's already a page up, but I feel a step by step guide is warranted to get people started easily.

Steps: submitter

  • Think up a topic
  • Does it need a video or a screen cast?
  • Do you have the required hardware?
    • Webcam/Video recorder
    • Microphone
    • Test them using Cheese!
  • Do you have the required software?
    • Screen casting: LIST HERE
    • Video editing: LIST HERE
  • Plan your video
    • What are you going to focus on: an entire application, a feature of an application, how to use it for a specific task?
    • What is the targeted audience: dummies, advanced? (We should list this in the video header too!)
  • Write up a transcript
    • Writing a transcript before making a screen cast helps in syncing the audio and video up properly.
    • The transcript needs to be submitted to aid us in addition of subtitles.
    • A video will need to be transcribed later, of course.
  • Record the audio
    • This is where the transcript comes in handy
    • Sit in a quiet environment. Keep a bottle of water with you.
    • Speak clearly, pronouncing each word with as much clarity as possible.
    • Time your sentences/clauses correctly to sync with the activities in the video.
  • License it correctly: CC by SA unported LINK EXPLAINING LICENSE
  • Add a license declaration file
  • Tar it all up!
    • Video/screen cast
    • Audio
    • License
    • Anything you'd want us to keep in mind while we process it for publication.
  • Send it to us!
    • You can email us the material, but since we expect it to be large in size, we prefer if you upload it all someplace and email us the link instead.
  • Wait for video to be published!

Steps: Fedora video team members

  • Receive video from submitter
  • Check files
    • Video
    • Audio
    • License declaration
    • Special comments
  • Test video
    • Is the file good?
    • Is the quality of the video good? Resolution/clarity/colours
    • Does the transcript sync properly with the video?
  • Test audio
    • Is the file good?
    • Is the audio clear
    • Does the transcript follow the audio properly and in sync?
  • Videos team reviews video and gives karma
    • If karma is above threshold, proceed to processing and publishing
    • Otherwise contact submitter with suggestions
  • Combine the audio, video
    • Test combined form
  • Add branding
    • Add starting template
    • Contains title, author, targeted audience, license
    • Add ending template
    • Contains author, feedback link, audience, permalink, rss feed link to channel
  • Translate transcripts
  • Compose subtitles file (srt files. LINK ON HOW TO DO THIS HERE)
  • Compose subtitles for translations
  • Videos team checks finalized video and gives it karma
    • If karma above threshold, publish video.
    • Reprocess with changes/suggestions.
  • Check published video.
  • Market published video.
  • Inform submitter.

Queries

  • Trac instance required to keep it organized?
  • Reward submitters/videos team helpers somehow? Can give them Badges? "Screencast ninja, vim ninja" etc?
Retrieved from "https://fedoraproject.org/w/index.php?title=User:Ankursinha/Videos_How_to_submit&oldid=272125"