Documenting Open Source: A Filmmaker's Guide to Capturing the Stories Behind the Code

Overview

Open-source software powers much of the modern internet—from the Linux kernel running on servers to the JavaScript libraries that animate your browser. Yet the people behind these innovations often remain invisible. Documenting open-source projects presents a unique opportunity to humanize technology, celebrate community collaboration, and preserve the history of how our digital world was built.

This guide draws inspiration from the work of Cult.Repo producers Emma Tracey and Josiah McGarvie, who have created documentaries spotlighting the developers and maintainers behind major open-source technologies. Whether you are a filmmaker, a tech enthusiast, or an open-source contributor yourself, this tutorial will walk you through the essential steps to produce a compelling documentary about open-source software and its creators.

Prerequisites

Before diving into production, ensure you have the following:

• Basic filming equipment: A camera (DSLR or mirrorless with video capability), microphone (lavalier or shotgun), and lighting kit. A smartphone with good video can work for interviews, but audio quality is paramount.
• Interview subjects: Access to open-source maintainers, contributors, or community leaders. Reach out via project mailing lists, IRC, Discord, or GitHub.
• Research skills: Ability to understand the project's technical context without being a domain expert. You'll need to ask meaningful questions.
• Editing software: Any non-linear editor (e.g., DaVinci Resolve, Adobe Premiere Pro, Final Cut Pro) with basic audio and color correction capabilities.
• Release agreements: Standard model release forms and, if possible, contributor agreements to use code snippets or screenshots.
• Time commitment: Documentaries require weeks to months of production, even for short formats.

Step-by-Step Instructions

Step 1: Choose Your Project and Angle

Open-source is vast—from essential infrastructure like OpenSSL to niche hobby projects. Identify a project that has a compelling story: a sudden security fix, a maintainer burnout, a community split, or a triumphant release. Research the project's history, key contributors, and recent events. For example, the Cult.Repro documentaries often focus on the people rather than the code itself. Your angle could be “The human cost of maintaining free software” or “How a diverse community built a tool used by millions.”

Action: Write a one-paragraph logline summarizing your documentary's focus.

Step 2: Prepare Interview Questions

Interviews are the backbone of your documentary. Develop open-ended questions that elicit stories, not just facts. Examples:

• “How did you first become involved with this project?”
• “Can you describe a moment when you almost gave up?”
• “What do you wish people understood about maintaining open-source software?”
• “How has the community changed over the years?”

Avoid technical jargon that might alienate a general audience. Ask follow-ups that reveal emotion and motivation. Emma Tracey and Josiah McGarvie often ask about the “aha” moments that led to lasting contributions.

Step 3: Schedule and Conduct Filming

Record interviews in a quiet environment with good lighting on the subject's face. Use a three-point lighting setup if possible. For remote interviews (common with open-source contributors spread globally), use platforms like Zoom or OBS to record separate audio and video tracks. Ensure you have a backup recording. Capture B-roll footage of the contributor writing code, attending a meetup (even virtual), or working in their natural environment. Screenshots of pull requests, commit history, or live coding sessions can also serve as visual aids.

Pro tip: Ask subjects to share their screen while walking through a contribution process—this can become powerful visual storytelling.

Step 4: Gather Supplemental Content

Collect code snippets, old mailing list threads, screenshots of bug reports, and any archival media. Obtain permission before using them. You might also include brief animations explaining the technology at a high level (keep under 30 seconds). Use tools like OBS Studio to capture terminal sessions or GitHub activity. Always credit the project and contributors.

Step 5: Edit for Narrative Flow

Structure your documentary like a story: introduce the project and its importance, present the people (their backgrounds, struggles, triumphs), climax with a challenge or critical moment, and conclude with the impact or future. Use music sparingly to underscore emotion. Include intertitles with names and affiliations. Keep the runtime between 10–20 minutes for online audiences, though longer formats work for festival submissions.

Technical note: Export in 1080p, 24fps or 30fps, with AAC audio at 320kbps. Use descriptive filenames for assets.

Step 6: Publish and Engage the Community

Upload to YouTube, Vimeo, or your own site. Share on social media, tag the project's official accounts, and post to newsletters like This Week in Rust or Changelog. Encourage comments and feedback. Consider creating a short “making of” video or a blog post with transcripts. The Cult.Repro producers often host live Q&A sessions after release.

Common Mistakes

Mistake 1: Assuming Technical Knowledge

Don't assume your audience knows what “fork” or “merge conflict” means. Explain concepts with analogies. If you must use jargon, add a brief on-screen definition.

Mistake 2: Ignoring Audio Quality

Viewers will forgive shaky video but not poor audio. Use a dedicated mic and monitor levels during recording. In remote interviews, ask subjects to use a headset and record in a quiet room.

Mistake 3: Focusing Too Much on Code

Code is abstract; people are relatable. Show the human side—late-night debugging, community arguments, personal sacrifices. The documentary “The Code” about the Linux kernel succeeded because it focused on Linus Torvalds' personality.

Mistake 4: Skipping Permissions

Open-source licenses allow code use, but you may need permission for logos, photos, or direct quotes. Always get signed releases for on-camera participants.

Mistake 5: Overproducing

Open-source communities value authenticity. Avoid excessive dramatization. A simple talking-head interview with natural B-roll often resonates more than slick, corporate-style editing.

Summary

Creating a documentary about open-source software is a rewarding way to highlight the people behind the code. Start with a compelling angle, prepare thoughtful interviews, gather rich supplemental material, and edit with a narrative focus. Avoid technical gatekeeping, prioritize audio quality, and always respect the community you document. By following this guide, you can produce a film that not only educates but also inspires appreciation for the collaborative spirit of open source. As Emma Tracey and Josiah McGarvie have shown, every commit has a story—your job is to tell it.