Qt's Open Governance Model, Discussed
summary
Qt launches a public governance effort in June and moves decision and development visibility into mailing lists and public repos, with 600 contributions so far and about 150 in-house engineers to scale. The process uses a required contributor license agreement and IPR checks, proposes meritocratic maintainers, tiered platform support, CI and unit-test gates, and recommends a Gerrit-like code review with bots to automate build and style checks so patches can be triaged, reviewed, and merged reliably.
AI-written summary · about
chapters (21)
- 0:00Introduction and purpose
- 3:15What is open governance
- 7:30Requirements for openness
- 10:21Starting the discussion
- 14:59Legal requirements and IPR checks
- 15:19Patch lifecycle and current process
- 21:53Spreading knowledge and training
- 26:56No reserved topics in development
- 29:02Finding maintainers outside Nokia
- 32:44Training contributors organically
- 34:29Access to design rationale
- 35:55Face-to-face contributor gatherings
- 36:57Roadmap transparency and collaboration
- 41:57QA management for new platforms
- 47:20Impact on development speed
- 50:10Code review and testing tools
- 51:55Feedback and communication channels
- 53:18Handling conflicts and decisions
- 57:57Open discussion and next steps
- 59:07Bootstrapping the process
- 1:02:39Moving forward with open governance
related talks
34mGovernance in Open Source - KDE's model
31mFrom Closed To Collaborative: Perspectives and Lessons From Qualcomm’s Open Development Experience
34mContributing your first patch to the Qt Project
23mGood Governance Practices for Healthy Open Source Projects
09mKeynote: How Open Governance Influences Open Source & Inner Sou...
44mBuilding On-Ramps for Non-Code Contributors in Open Source
24mThe KDE Free Qt Foundation
47mPanel Discussion: A How-to Guide for Contributing to Open Source as an Employee