GeezerVison is showing github.com — Check videos against workbook after creation · Issue #122 · InnerSourceCommons/InnerSourceLearningPath
Check videos against workbook after creation #122DescriptionWhat we have left:
- Upload new video.
- Update references to new video (e.g. config.yaml, playlists).
- Rewrite question.
Rationale
The workbook contains questions based on the videos - one could consider this the take-aways.
Especially in the case of the Contributor we are creating workbook content before the videos based on the Outline and the articles.
We need to ensure that the videos and articles contain content that matches the workbook questions and makes them properly answerable.
Action items & acceptance criteria
Prior to making the videos
- Check that the Contributor video scripts have matching content for the workbook
After making the videos
- Check the Contributor videos for content from the workbook
Acceptance:
- Let someone uninvolved test themselves with the workbook based on the videos.
- Introduction
- Seen Through
- Clean + Pass
- Adapted + Pass now
- Trusted Committer
- Seen Through
- Clean + Pass
- Adapted + Pass now
- Contributor (Videos can be seen here: https://innersourcecommons.org/learn/learning-path/contributor/)
- Seen Through
- Clean + Pass
- Adapted + Pass now
- Product Owner
- Seen Through
- Clean + Pass
- Adapted + Pass now
Activityrrrutledge commented on Oct 8, 2019 We can also do this check after creating the video scripts yet still before shooting the video itself (#140) lenucksi commented on Nov 15, 2019 arnom-ms commented on Apr 2, 2020 At this point the ask is to
- Watch the video on one segment (available on our Google drive)
- After watching one segment, review the workbook questions if the question(s) for the segment can be answered after watching the video.
rrrutledge commented on Apr 16, 2020 BrittanyIstenes commented on Apr 23, 2020 Intro Review - Complete
Introduction - Video 3
- Planning role is not listed in guidance doc
- Additional resource page leads to a 404
Introduction - Video 4
- Video script is more high level than the doc, but covers all the bases
Introduction - Video 5
- Mentorship is talked about in the video first, Openness is listed first in the doc
- 10% of resource into your trusted committer is not listed in doc
- Video only focused on Mentorship and Trusted committers, but did not get back into the other principles listed in the doc
rrrutledge commented on Apr 23, 2020 lenucksi commented on Apr 29, 2020
Introduction - Video 3
- Additional resource page leads to a 404
Do we control said URL such that we could un-404 it? rrrutledge commented on Apr 29, 2020 Which URL, specifically, are we talking about? BrittanyIstenes commented on Apr 30, 2020 Ludmila-N commented on May 1, 2021
The intent here is "bug tickets" "well written issues". At least the good ones already help tremendously, so I definitely would want them. Where "well written" means: Detailed, with reproduction step, expectations and reality, possibly even a first patch or guess at a code location. Maybe we could add a small overlay on the video?
Understood, and you say this in a few seconds - so this was provably a self-correction, but it sounds like you're listing bugs along with bug tickets. I think the best option is to cut or mute these ~5 seconds and leave the rest as is. Ludmila-N commented on May 1, 2021 Reviewing Contributor videos, Contributor Ethos section:
Question 2 - no issues.
Question 1, answer 4 has the explanation that was never mentioned in the video, suggest rewriting this option:
Why 4 is incorrect: Getting your contribution accepted is an achievement to be celebrated. However, your involvement does not end there. You should plan to be available at a minimum to fulfil a 30-day warranty on your changes (and their impact), or even better: stay close to the community and help out with additional contributions.
Also "fulfill" is spelled with double L at the end. lenucksi commented on May 6, 2021
Understood, and you say this in a few seconds - so this was provably a self-correction, but it sounds like you're listing bugs along with bug tickets. I think the best option is to cut or mute these ~5 seconds and leave the rest as is.
Cutting it out sounds good. Do you happen to have taken a note of the time-code such that I can just edit it out and re-upload it?
Other than that: We'll need to update parts of the website, the playlists on YT or other material with the new video code. Can you please point me to the places that need changing @tsadler1988 @voborgus ? lenucksi commented on Jun 21, 2021 "Providing good bugs" is at 3:25, "providing good issue tickets for bugs" is at 3:29
Modified video has been uploaded to the the GDrive. We need someone to re-upload it to YT, adapt the YT playlists, add the thumbnail and modify the website parts accordingly. rrrutledge commented on Jun 21, 2021 clcoffey commented on Jun 29, 2021 lenucksi commented on Jul 5, 2021 New video is live and adapted. Remaining is adaptation of the Workbook question rrrutledge commented on Jul 9, 2021 fioddor commented on Jul 19, 2021 I've watched the Introduction videos and I was able to complete their corresponding workbook. I'm totally uninvolved in their creation, but on the other hand I already have some previous knowledge about open source communities, so take my feedback with a pinch of salt. rrrutledge commented on Jul 19, 2021 rrrutledge commented on Jul 19, 2021 @lenucksi can you update the checkboxes in the description with what has been done and what is left?
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|