This repository has been archived by the owner on Nov 28, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Video Plan
taxles edited this page Jun 20, 2014
·
5 revisions
This is a team effort where we can generate awesome code AND an awesome team video, but the video has to be under 3 minutes (= 180 seconds) which is tight so we need a plan.
Denise (my wife) is happy to do the editing (mainly from home, see below) and she will also attend GoveHack2014 Sunday afternoon to do the final edits.
Headings for this plan are:
- [Status Board] (statusBoard)
- Proposed Plan
- My Requests
- Media Management
- Video Preparation = Test Runs
- Preparation Shot Structure
- Connection Use Cases at GovHack2014
- Ten Point Guide transcribed from "How to make your 3 min Govhack project video"
This is what I see as important for the video.
- Once you have loaded any media files please do not edit them by changing the file name (or path) as Denise will experience rather painful broken media link. - If you have an update to an existing media file please just reload the new file with _Update_1 appended to the original file name. Denise will see the old and new and do the adjustment. - We will use the [GovHack2014PreparationVideo] (https://drive.google.com/folderview?id=0B44XovW7TkdgaHlhRHNOdHJJWE0&usp=sharing) Google Drive Folder for sharing (which is only accessible by collaborators). - Al will invite other members to join the Google Drive Folder. - To help Denise know "what goes where" (for she isn't a mind reader nor coder) we need a media management system. - To help us prepare I have generated Google Drive sub-folders using the Preparation Shot Structure. - Once we have some practice I reckon we will have an idea how we want to number and name the media files. Once you are connected could you please provide representative test media (footage, screen captures, selfies, etc.) so: - we get to practice the video workflow and media management, - Denise gets a feel for the material she will be editing, and - you get to see the sort of video we can generate. This is just a 'preparation plan' as only at GovHack2014 can we add specifics re: features, benefits, etc 1. Intro: Team Name, Members, Photos, ... 2. Hack: Its Aim and benefit. Who does it benefit? Whose life does it make better? What value does it add to our society? 3. Progress: Architecture, sketches, diagrams, screen shots, ... 4. Hack Internals - Data Sets - Technologies - Programming language(s) - Host 5. Hacking Expertise. Who generated what interesting hack features 6. Other Key Team Expertise - Denise on Video, ... 7. Missing Features (if we had mode time...) 8. Positive Ending **We all have reliable and fast internet connections** at GovHack2014 and we all are sharing media files via Google Drive which Denise is assembling in the background. **Unreliable and/or Slow Internet Connection.** My laptop acts as a central location for the media and only that machine utilises the Google Drive connection. **No effective internet connectivity for media files.** I drive home and load the media onto her machine there. 0. Submit a 3 minute video demonstrating their hack, to better assist with the judging process. These videos will go online. 1. Key thing to remember, the video cannot be longer than 3 minutes. 2. Some brief tips on how to make video: - Aim for brevity and clarity, the aim is to get your message across to the judges as quickly and clearly as you can. - You don’t need to have a detailed script but if you at least start with an outline to make sure you include all the key things: - Introduce your team - Give the name of the team - The name of the hack - The name of each of the team members - Show a photo of team or a brief video clip - You should tell us about your hack, what does it do, what does it aim to do - What data sets did you use - What technologies did you use - What programming languages - Where did you host it - Any interesting technical features that highlight the technical expertise that went into your hack - If you have other key areas of expertise that went in such as user experience design, visual design or user research, or if you combined a number of disparate data sets, make sure you tell us about these as well. - Use a mix of screen shots, video and voiceover to show your hack. 3. Plan your demonstration. 4. Make sure you show each of the key features. 5. If you have missing features, describe what you would do next, tell us what is missing. 6. Explain the benefit or value of your hack. 7. Who does it benefit? Whose life does it make better? What value does it add to our society? 8. You might cover all of this in a voiceover that accompanies some screen shots or video demonstrating your hack. 9. Include some progress shots of how your hack progressed over the weekend. These can be photos you take, or screen grabs of the work in progress. If you have done lots of sketches and diagrams on a white board, photos of those are really interesting as well. 10. The main thing is to focus on the facts and a demonstration of what you have done.