Producing a Documentary on Open Source: A Step-by-Step Guide

Introduction

Open-source software powers the internet, yet the stories of the people behind it often remain untold. Inspired by discussions with Cult.Repo producers Emma Tracey and Josiah McGarvie, this guide walks you through the process of creating a documentary that captures the passion, challenges, and innovations of the open-source world. Whether you're a filmmaker or a tech enthusiast, these steps will help you turn your vision into a compelling narrative.

What You Need

• Camera and audio equipment (at least 1080p video, lavalier or shotgun microphone)
• Screen recording software (e.g., OBS Studio – free and open source)
• Video editing software (e.g., DaVinci Resolve, Kdenlive)
• Access to open-source communities (mailing lists, IRC, Discord, forums)
• Permissions and licenses (understanding GPL, MIT, etc.)
• Interview subjects (maintainers, contributors, users)
• Research materials (project documentation, commit history, prior interviews)
• Cloud storage or external drives for footage backup

Step-by-Step Guide

Step 1: Define Your Documentary’s Focus

Start by narrowing down your subject. Are you highlighting a specific project (like Linux, Git, or Kubernetes) or telling a broader story about the open-source movement? Consider the human angle – the developers solving real-world problems, the communities built around code, or the impact on society. Use this focus to craft a clear logline, such as: “How a small group of volunteers built the software that runs the world.”

Step 2: Research the Community and Key Individuals

Dive into the project’s history. Read documentation, browse commit logs, and follow discussions on public channels. Identify influential figures – lead maintainers, long-time contributors, and even critics. Plan to interview people with different roles and perspectives. Take notes on jargon and technical concepts you’ll need to explain to a general audience. Reach out via private messages or community introductions; be transparent about your documentary intentions.

Step 3: Plan Your Interviews and Logistics

Decide between remote or in-person interviews. For remote, use tools like Jitsi Meet (open source) and always record locally. Prepare an interview guide with open-ended questions, but leave room for spontaneous stories. Key questions to ask:

• “What problem were you trying to solve when you started contributing?”
• “Can you describe a moment when the community came together?”
• “What challenges does open source face today?”

Schedule sessions considering time zones. Confirm consent and explain how you’ll use the footage.

Step 4: Understand Legal and Licensing Implications

Open-source projects rely on licenses that govern reuse. When using code snippets or project logos, ensure you comply with the license (e.g., GPL requires attribution and same license for derivatives). Never assume anything is free to use. Create a release form for contributors if you plan to distribute the documentary commercially. Consider licensing your film under Creative Commons if you want to give back to the community.

Step 5: Capture Engaging Footage

Film interviews against simple backgrounds with good lighting. For remote interviews, ask subjects to position themselves in a quiet, well-lit room. Record screen captures to show code being written, pull requests being merged, or bug fixes in action. Capture B-roll of developers at their workstations, open-source conference crowds (with permission), or visual representations of data flows. Use a tripod or stabilizer for steady shots.

Step 6: Edit for Narrative Flow

Organize your footage into a story arc: introduction of the problem, the people, their struggles, successes, and future vision. Start with a hook – perhaps a compelling quote or a visual of code in motion. Intersperse interviews with screen recordings and visuals. Simplify technical jargon with on-screen text or animations. Keep the runtime between 20 to 60 minutes for short documentaries. Use music (royalty-free or open-source) to set the tone.

Step 7: Review for Accuracy and Community Feedback

Before finalizing, share a private link with your interview subjects and a few trusted community members. Ask them to check factual claims, code references, and portrayal of events. Incorporate corrections graciously – this builds trust and avoids misrepresentation. Also review the audio levels and color grading for consistency.

Step 8: Release Under an Open License and Promote

Publish your documentary on platforms like YouTube, or better, on a self-hosted site using open-source video players (e.g., Video.js). License your work under Creative Commons (e.g., CC BY-SA) to align with open-source values. Announce it on relevant mailing lists, Reddit communities, and social media. Consider premiering at an open-source conference (virtually or in person) to reach the intended audience.

Tips for Success

• Build trust early. Open-source communities can be wary of outsiders. Engage genuinely, attend meetups, and contribute a small fix before asking for interview time.
• Be patient with schedules. Maintainers are often volunteers with day jobs. Offer flexible interview slots and respect their time.
• Embrace open-source tools for production. Use Blender for animations, Audacity for audio editing, and OBS for screen capture – it shows your commitment to the movement.
• Tell human stories, not just technical ones. Viewers connect with struggles, failures, and triumphs. Show the people behind the code.
• Keep licenses clear. Provide a list of all third-party assets and their licenses in the video description or credits.
• Expect feedback. The community will scrutinize your work. Embrace constructive criticism and be ready to revise.

Conclusion

Documenting open-source software requires more than just technical know-how – it demands empathy, curiosity, and a respect for collaborative creation. By following these steps, you can craft a documentary that not only educates but also honors the spirit of open source. Lights, camera, open source – your story starts now.