The PostgreSQL License Fee
summary
Argues the real “license fee” is time: voluntary work funds PostgreSQL’s upkeep, governance and events rather than cash. Lists concrete assets and channels—1,600,000+ lines of C, 700+ contributors, mailing lists, docs, IRC/Slack/Discord, translation teams, infrastructure and nonprofits (PGDG/PGUS/PGCA)—and organizational results like a functioning code-of-conduct committee and recurring quarterly releases. Gives employer math and examples: 2 hours per week per employee → 5,000 hours for 50 employees, PGX logs 1,000 hours annually, showing the approach scales and sustains the project.
AI-written summary · about
chapters (21)
- 0:00Introduction and speaker
- 3:02What is a software license fee
- 4:06PostgreSQL’s no-fee model
- 5:12Project overview and scale
- 7:37Core team and project vision
- 9:02Writing code and becoming a hacker
- 10:06Web, infrastructure and documentation
- 11:50Answering user questions and lists
- 13:17Language-based community support
- 14:40Social media and advocacy
- 16:24Code of Conduct Committee
- 18:08Conference and user group involvement
- 21:40Conference organizing skills
- 25:09Nonprofit organizations in PostgreSQL
- 27:11Personal benefits of community work
- 28:17Employer benefits and recruiting
- 31:29Costs and company support for community time
- 33:36Real-world example with PGX
- 35:03Scaling community contributions
- 36:29How to get involved in the community
- 38:15Call to action and Q&A
related talks
51mBehind Postgres 18: The People, the Code, & the Invisible Work
05mLong Live Sustainability
25mDiscover your contribution-magic
07mKeynote: Contributing to Critical Open Source Projects: Lessons from PostgreSQL
43mHow to Contribute to an Open Source Project like Postgres?
38mOpen Source - A Blessing or a Curse?
30mCommunity meets Business
32mFibonacci Spirals and Ways to Contribute to Postgres—Beyond Code