Keynote: Linus Torvalds, Creator of Linux & Git, in conversation with Dirk Hohndel, VP, VMware

### Overview In this keynote interview at an open-source event in Beijing, Linus Torvalds sits down with Dirk Hohndel, Chief Open Source Officer at VMware, for an unscripted, conversational dialogue on kernel maintenance, software sustainability, git's cultural impact, and advice for prospective contributors.

### Key Topics - **Kernel Release Cadence and Coordination**: Linus addresses the atypical Monday night release of Linux 4.12 rc6, explaining the interplay between his travel schedule and strict embargoes tied to a userland security issue with a kernel workaround. - **Maintainer Model and Workflow**: Torvalds explains that his primary responsibility is not authoring original code, but rather orchestrating flow and merging changes submitted by trusted subsystem maintainers. - **Sustainability and Forking Philosophy**: Torvalds dismisses long-term concerns regarding single points of failure (the 'bus factor'), highlighting the resilience of the maintainer tier. He argues that friendly, non-acrimonious forks are fundamental to distributed development, as they allow independent proof of concept before merging upstream. - **Git's Evolution and Impact**: A discussion of Git's transition from an initial specialized tool for kernel development to an industry standard adopted across organizations and academia, maintained for over a decade by Junio Hamano. - **Guidance for Developers**: Guidance for aspiring developers to gain technical depth in specific, focused components rather than attempting to master entire systems, highlighting the technical and social benefits of open source.

### Technical Details - **Release 4.12 rc6 & Security Embargo**: Kernel releases generally take place on Sunday afternoons to accommodate weekly patch integration. The 4.12 rc6 release was deferred to Monday night to honor an embargo expiring at 3:00 p.m. Europe time, synchronizing a kernel workaround for an external user-space security vulnerability. - **Subsystem Activity (UFS)**: Outside of continuous support for new architectures and chips, Torvalds noted unexpected patch activity and fixes in legacy code, citing the Unix File System (UFS)—traditionally associated with BSD systems rather than Linux—as an example of dormant code undergoing active revision. - **Data Integrity and Git Design**: Linus noted that Git’s distributed design was purpose-built to facilitate seamless forking and merging while employing cryptographic hashing to guarantee repository integrity and prevent data corruption.

### Takeaways Open source development relies as much on sustainable release processes, social communication, and distributed contribution models as it does on raw technical execution. Rather than resisting forks, maintainers should encourage developers to independently prove out ideas and merge proven work back upstream.