Re: PostgreSQL Contributor levels - Mailing list pgsql-www

From Cornelia Biacsics
Subject Re: PostgreSQL Contributor levels
Date
Msg-id CALaz2Zs4rhV15xhP24NGUEvj2zSPoqOZ0asQ46xJL_GfH6FNFQ@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL Contributor levels  (Melanie Plageman <melanieplageman@gmail.com>)
List pgsql-www
Hello Melanie, thanks a lot for taking the time to look at my proposal.
Please find some comments below. 

On Sat, Oct 11, 2025 at 6:04 PM Melanie Plageman <melanieplageman@gmail.com> wrote:
Thanks, Cornelia for thinking about this and taking the time to put
together a proposal. The Contributors Committee is always happy to
have people putting work into recognizing people in the community.

On Sat, Oct 11, 2025 at 5:17 AM Cornelia Biacsics
<cornelia.biacsics@cybertec.at> wrote:
>
> As part of the ongoing discussion on recognizing PostgreSQL contributors, I’d like to propose a structured framework that reflects both the field and the extent of contributions.

In my opinion, the issue with structured frameworks is that not
everything fits in them and it makes it harder, not easier, to
recognize different kinds of contributions.
What about hosting a Postgres podcast or an educational youtube
series? Is that considered marketing for the community? What if it is
sponsored fully by your employer and includes some promotion of your
employer (i.e. it isn't really a community podcast even though it is
about Postgres)? That means the Contributors Committee has to discuss
every badge before awarding it. 

Absolutely — new things will come up as new possibilities arise. This list is subject to change over time, and I’m sure it is possible to cover many of the existing contributions on it. 
(my list contained examples) 


Or take commits -- should someone with 4 typo patches accepted get
recognized at the same level as someone who wrote 4 features or who
identified 4 critical bugs? Who defines what a lead reviewer is?

Probably not (not my field of expertise), but this is also subject to evaluation or calculation criterias.  


Or what about combinations of contributions? Aren't you a gold level
contributor if you work at the Postgres booth at conferences, author
10 commits to every release for 10 years, volunteer on multiple
organizing committees, and run a PUG? But you may not qualify as gold
in any one category.

In this case, I’d say you’d receive a Gold Code Contributor badge, and a second one (Ambassador badge or whatever name it will receive), level is based on the number of individual contributions in this category. This way, contributors can earn badges across different categories.
 

And if we stick strictly to the definitions, what about contractors
who are paid by the community to do legal work for over a year? Do
they automatically qualify for Infrastructure and Operations badges?
Or someone who is paid to design a logo for a community conference?

Are they currently listed as contributors? Then I’d say yes. But you’re absolutely right — the rules need to be defined.
Probably quite similar to how you handle this at the moment. 
 
We would have to make individual judgment calls on every one of these,
which means we can't automate it, which means it will be woefully out
of date if the Contributors Committee doesn't have one person working
full time on this.

I’ve recently seen a program for continuous personal development to maintain a certain status — and yes, in that case you have to submit proof through a system. I agree, it’s a bit of an overhead, and it probably depends on how far you really want to go with recognizing and developing the contributor program. 

> And as Bruce already mentioned: PostgreSQL’s success depends on a broad range of contributors. It includes working on infrastructure, documentation, testing, events, and community growth and a lot more.

Absolutely. It is so important to recognize all types of contribution.

> I would first suggest defining fields of contributions (as you somehow already have listed here: https://www.postgresql.org/about/policies/contributors/). And then define sub-levels of achievements (e.g. Bronze, Silver, Gold) based on the intensity or amount of contributions in this category.
> Recognizing contributors based on the nature and level of their work would ensure fair and meaningful appreciation across the ecosystem.

I'm not sure if specifically recognizing and ranking people based on
the nature of their work would ensure fair appreciation. I think there
is a chance that slicing and dicing to this level emphasizes the
difference of different types of contributions -- not their equal
importance as part of a holistic whole. Though I think the difficulty
of executing this kind of system is a bigger concern.

That being said, I understand if some people want recognition of the
area that they are active in. To that end, we are working on a feature
similar to the idea of badges.
 
It would at least make the different types of contributions more visible and tangible, in my opinion.


> Contributors can collect multiple badges across different categories, showcasing the breadth of their involvement and celebrating their growing impact within the PostgreSQL ecosystem. Which also adds a light gamification aspect to recognition, inspiring contributors to explore multiple areas of PostgreSQL — from code and testing to marketing, documentation, and community engagement.

The Contributors Committee agrees with this. We are currently working
on a project for some kind of granular badges or tags like "PGConf EU
2026 Volunteer" or "Postgres 18 Code Contributor" that people can
self-nominate and be approved for having on their contributor profile.
We weren't imagining levels for each one, but more like specific tasks
or roles people have had. We think you're right about the gamification
and also recognizing people for contributing in multiple ways and
inspiring them to get involved in more ways.

We could definitely use help with this and anyone who is interested
(especially interested in the www development component should email
us). We haven't sent an email about it yet because the idea is still
in the early stages.

Thank you. 
 

> Further, I’d like to bring another aspect into the discussion about contributor recognition — acknowledging company-level (commercial) contributions to PostgreSQL.
> Many companies make a significant impact by increasing PostgreSQL’s visibility and awareness, which ultimately helps the entire ecosystem thrive. Recognizing these efforts would highlight the essential role that commercial contributors play in supporting the community’s growth and sustainability.

If I'm understanding your idea, there is already a concept like this
called "Sponsors" [1].

Oh! Thanks for that! 
 
- Melanie

[1] https://www.postgresql.org/about/sponsors/

Overall, thank you very much for your reply. I’d be happy to discuss the details further with you and offer any additional help.

Best wishes
Cornelia  


E-Mail Disclaimer
Der Inhalt dieser E-Mail ist ausschliesslich fuer den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme, Veroeffentlichung, Vervielfaeltigung oder Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen.


CONFIDENTIALITY NOTICE & DISCLAIMER
This message and any attachment are confidential and may be privileged or otherwise protected from disclosure and solely for the use of the person(s) or entity to whom it is intended. If you have received this message in error and are not the intended recipient, please notify the sender immediately and delete this message and any attachment from your system. If you are not the intended recipient, be advised that any use of this message is prohibited and may be unlawful, and you must not copy this message or attachment or disclose the contents to any other person.

pgsql-www by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: PostgreSQL Contributor levels
Next
From: Ellyne Phneah
Date:
Subject: Request to Add My PostgreSQL Book to the Books Page