From de52ad8b37664e18cc03ff2b2494209e82d2918d Mon Sep 17 00:00:00 2001 From: rrrutledge Date: Mon, 23 Dec 2019 05:46:25 -0800 Subject: [PATCH 1/3] How to review a video segment --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index aa283ef5..2fc8b0a0 100644 --- a/README.md +++ b/README.md @@ -34,7 +34,7 @@ We can divide up the work and collaborate on each section via folks from the com | Speaker | 20 hr | Gives the spoken video for each segment in the section. | | Speaker Reviewer | 2 hr | | | Post-Production | 10 hr | Responsible for post-production effects and editing for spoken videos. | -| Post-Production Reviewer | 1 hr | | +| Post-Production Reviewer | 1 hr | Review raw video recordings. Comments should focus on adding or editing spoken audio, slides, or banner text. | This list is not an exhaustive a description of all currently open or possible tasks. There are many additional ways to help the learning path effort (please see *How to Get Involved* section...) From 0994f56e96094fb65d6e871e2a12c500ec51f845 Mon Sep 17 00:00:00 2001 From: rrrutledge Date: Sat, 28 Dec 2019 06:35:44 -0800 Subject: [PATCH 2/3] Detailed review instructions --- CONTRIBUTING.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e78a7573..94f960f3 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -24,3 +24,23 @@ If the issue applies to the Learning Path in-general but not to any specific sec [suggestion feature]: https://help.github.com/articles/commenting-on-a-pull-request/#adding-line-comments-to-a-pull-request [incorporate suggestions]: https://help.github.com/articles/incorporating-feedback-in-your-pull-request/ [project board]: https://github.com/InnerSourceCommons/InnerSourceLearningPath/projects/1 + +# Review + +When reviewing a video: + +* Each video should teach all of the information needed to answer the corresponding workbook questions. +* The information in the video should also be harmonious with the corresponding written article, +although the article may provide additional detail not covered in the video. +* The purpose of video review is to ensure that: + * the video relates correctly to its corresponding workbook/article. + * the speaker and message are clear and easy to understand. +* Any comments for video changes should be made directly in the _Screenlight_ tool. +If review of the video prompts an idea for change in the corresponding workbook/article, +then those comments/suggestions should be made against the source text _GitHub_. +* Video comments should focus on non-visual adjustments to make, including: + * Re-recording portions of the audio. + * Adding or editing slides. + * Addition of superimposed banner text. +* Adjustments to respond to comments will be released as a new video in the same folder. +The new video will have a version number in the title. From 6e6e187dd85781de933d6b5cde860d8a3cbba237 Mon Sep 17 00:00:00 2001 From: rrrutledge Date: Sat, 28 Dec 2019 06:37:04 -0800 Subject: [PATCH 3/3] Remove review detail from README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2fc8b0a0..b9ecaa97 100644 --- a/README.md +++ b/README.md @@ -34,7 +34,7 @@ We can divide up the work and collaborate on each section via folks from the com | Speaker | 20 hr | Gives the spoken video for each segment in the section. | | Speaker Reviewer | 2 hr | | | Post-Production | 10 hr | Responsible for post-production effects and editing for spoken videos. | -| Post-Production Reviewer | 1 hr | Review raw video recordings. Comments should focus on adding or editing spoken audio, slides, or banner text. | +| Post-Production Reviewer | 1 hr | Review raw video recordings. | This list is not an exhaustive a description of all currently open or possible tasks. There are many additional ways to help the learning path effort (please see *How to Get Involved* section...)