public inbox for [email protected]
help / color / mirror / Atom feedFrom: Laurenz Albe <[email protected]>
To: Cornelia Biacsics <[email protected]>
To: [email protected]
Cc: Jimmy Angelakos <[email protected]>
Cc: Christoph Berg <[email protected]>
Cc: PostgreSQL Contributors <[email protected]>
Subject: Re: PostgreSQL Contributor levels
Date: Sat, 11 Oct 2025 20:06:31 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CALaz2ZsLQLbw6Pv714DyO8rTJfLF=nhC0BmHV4OhsurkrhLVKg@mail.gmail.com>
References: <[email protected]>
<[email protected]>
<[email protected]>
<CALaz2ZsLQLbw6Pv714DyO8rTJfLF=nhC0BmHV4OhsurkrhLVKg@mail.gmail.com>
On Sat, 2025-10-11 at 11:17 +0200, Cornelia Biacsics wrote:
> 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.
That sounds complicated.
Also, I am afraid that splitting up contributions in categories will
do the opposite of what we want: people will think that code contributors
are a better category than conference organizers. And I thought we don't
want that.
Ultimately, it is a value judgement who is a valuable contributor, and
we shouldn't try to hide that behind formalisms. The process will always
be some variant of "Hey, I think Cornelia should be on the list." -
"I agree, let's put her on the list."
Yours,
Laurenz Albe
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: PostgreSQL Contributor levels
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox