Crossing the Streams: Enabling Collaboration Between Products and Upstreams
summary
Describes how Red Hat enforces an upstream first workflow by making upstream docs reusable downstream, showing the Mallard topic system built for GNOME to assemble topics from many sources, and the RDO-to-Red Hat OpenStack pipeline used in product builds. Recommends small topic-based pages, running documentation sprints, and a lightweight content strategy in a box to curate community content. Emphasizes the rule every page is page one, reports that reusing upstream topics reduces duplicate work and increases contributor participation.
AI-written summary · about
chapters (9)
- 0:00Introduction and welcome
- 1:48Background and project history
- 5:19Upstream first philosophy at Red Hat
- 8:29Documentation streams examples
- 13:41Content reuse challenges
- 16:51Every page is page one
- 19:41Building community documentation
- 21:25Content strategy in a box
- 27:45Summary and resources
related talks
39mThe Documentation Dream: One Team, No Silos, Shared Goal
26mEvolution of Product Documentation
28mThe Penrose Panel: Leadership Q&A
14mCollaborative Innovation
42mEat Your Own Dogfood - How Upstream Orientation Changed the Way We Work in Open Source Management
46mMerging community and business goals
43mFOSS DOCS 101 (keep it simple, present!)
32mBridge the Gap To OSS Adoption With Documentation: A Kubernetes Story