Herding cats: project management in communities
summary
Fedora program management at Red Hat turns release goals into calendar dates, tracks change proposals through blocker and prioritized-bug reviews, and coordinates resources across volunteers using a mix of meetings and reports. Work includes running blocker-bug go/no-go meetings, publishing a weekly status blog that lists change statuses, holding IRC office hours for ad hoc questions, and pushing for public Kanban boards so contributors can discover schedules and responsibilities; leadership relies on influence not formal authority.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:33Housekeeping
- 0:53Project
- 1:59Iron Triangle
- 2:41Project management
- 3:20Managing schedules
- 4:36Tradeoff
- 5:01Release
- 5:55Cost
- 7:40Technical changes
- 8:53Quality
- 11:26Communicate
- 11:54Meetings
- 15:35Project management in communities
- 16:18Processing bureaucracy
- 19:31Guiding principle
- 20:20Questions
related talks
35mHerding Cats Standardizing Engineering Processes
22mYour Open Source Repo Needs A Project Manager
47mProduct Management in the Open (Source) - community and direction
49mCommunities Over Code: How to Build a Successful Project
43mHow To Get A Project Unstuck
16mFrom Kernel to Kubernetes - Agile in Open Soure
48mApache Way: Effective Open Source Project Management
47mHow To Get A Project Unstuck -- And Fixing The Skill Gaps That Got Us Here