Re: PostgreSQL Contributor levels

From: Christoph Berg <myon(at)debian(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org>, PostgreSQL Contributors <contributors(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL Contributor levels
Date: 2025-10-10 12:26:44
Message-ID: aOj7hFdufvlWwyiF@msg.df7cb.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-www

Re: Tom Lane
> Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> > The threshold for getting into the release notes is absolutely minimal,
> > and I think it would devalue the curation work that you are doing by
> > somehow combining the two data sets or making a third level based on the
> > release notes or something like that.
>
> +1. For example, a single bug report is enough to get you into the
> commit log and thence the release notes. There's no requirement for
> continuing effort, but I think even the lowest level of the curated
> list should imply some amount of that.

We are aware of that, and want to preserve that value. The details are
not fleshed out yet, but it will be something like two pages. A new
one "these people contributed to PostgreSQL in the last N
releases/years" and the existing one which is then the "these are the
people who work on keeping PostgreSQL alive" spotlight.

> Perhaps the release notes could be useful as a sanity check though.
> Say, if a person appears in the last three release-note lists and
> is not in the curated list, maybe that is a name to take another
> look at.

Exactly, plus making the people from there a bit more visible. Plus
the ability to combine with more data sources like conference
organizers, translators, ...

Christoph

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Laurenz Albe 2025-10-10 12:29:07 Re: PostgreSQL Contributor levels
Previous Message Christoph Berg 2025-10-10 12:16:52 Re: PostgreSQL Contributor levels