Every contribution to the PostgreSQL project counts, big and small, the glamorous and the tedious. That was my soapbox for my 2025 FOSDEM PGDay lightning talk. What I shared:
It’s nice to get recognized for your work, and it’s nice to pass on that feeling and recognize others for their work as well.
Around this same time last year I gave a lightning talk at PGDay Paris, about the makeup of the contributor list on postgresql.org and how contributions like extension development, event and community organizing, and the creation of free and available training material for the longest time wouldn't get you noticed. Code contributions and patches to Core are very visible, but don’t make a community.
A small group of community members, myself included, started postgres-contrib.org to list all the non-Core, non-code contributions we can find, every week.
Now, Christoph Berg at PGConf in Athens last year, shared how PostgreSQL Core updated their definition of what makes a "Contributor". And it is great news for our cause. A much more diverse range of contributions now get recognized on postgresql.org, and it’s easy to nominate additions to this list: email the Contributors Committee (that’s Christoph, and Joe Conway, and Melanie Plageman) at contributors@postgresql.org.
The general rule is that you’ll need to show consistent effort for ~2 years. We see a role for postgres-contrib.org as proof / or archive highlighting the work of unsung heroes, and make sure they’re… sung?!
We can’t possibly know about all the work being done, so we’re asking for your help. Please submit your or your peer’s work to contact@postgres-contrib.org.
Whether it's volunteering on a talk selection committee for an event, or the code of conduct team, a video recording of your recent PUG, a tutorial you’ve recorded, we want to make sure a larger audience gets to hear about it!
Top comments (0)