Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v7Vja-003o3W-LG for pgsql-www@arkaria.postgresql.org; Sat, 11 Oct 2025 09:17:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1v7VjY-00Fm6A-E3 for pgsql-www@arkaria.postgresql.org; Sat, 11 Oct 2025 09:17:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1v7VjX-00Fm5p-V7 for pgsql-www@lists.postgresql.org; Sat, 11 Oct 2025 09:17:49 +0000 Received: from mail-ed1-x532.google.com ([2a00:1450:4864:20::532]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v7VjS-001B6O-0J for pgsql-www@lists.postgresql.org; Sat, 11 Oct 2025 09:17:47 +0000 Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-639e1e8c8c8so5503343a12.1 for ; Sat, 11 Oct 2025 02:17:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=google; t=1760174260; x=1760779060; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=zNI4W0tJ44eW/TUk8eXjswXS7pxA16w1FkOcu5X7yqw=; b=F3Owytyh9EL0kmShSzi62zYF5aDi+2NFfjHK94C5G7GK4CLL6eM1V0cnkug1vt9mfo m2hnACVwBGzL/OZ3dk07UE2D4CgTPTaOSwNLvfoAcoE4bIK1yklIPEoQiFdM24C7XJ8C P5aLXTMhQZNN6tORccg9Y5Za20WLxM+2cUufC2Ej7E8kDihPwnL/GtN6l7DoXxxiaYHJ e1PApc8vMp/kHHc+OAJ6IOkCOHVNywYAD+tOGEznoidUD6APPAtlbCYwBJoA93QwsrtX RGoAPPZ0CnULIqYFrI2itjVLJ2HviCqxEXCw3mgj2iAX5KN6dQp8kSheCGz0cs1XOp+Q /qVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1760174260; x=1760779060; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=zNI4W0tJ44eW/TUk8eXjswXS7pxA16w1FkOcu5X7yqw=; b=Ksy0aOjO7x5rnlYYeOtUaIdCRo0j2mwhvPJ3vKxRPcNRy0HCYq1G0zNSOPuqvaccSy YMUB+yscEfYFboWhFLdn2B8GsBuJkjfbE4IyNi31yz/mgOhNsp21xTE2IEMZ9e9FcSrA WgV7TZTw+5oewosKaXegFi3VnzSZSf2byXWg9dX0q53F+GMmqmQ+GEUKV3vxsIlGKGiC Cz8BRBk6+jKJvMr3cvVpfO4o0kbAzPgKP0c6oRLlOGWyN9bE12kvm7p+xurs0i1xUCKf 93w50ol0I3uh5rqDYhHvV+adtqRBzdZuWlKf42HW2kSEZQiytzehfRKKLNEG8C94dGxv DpAg== X-Gm-Message-State: AOJu0YyWP6fOTbEBWYBF6sNHM+MzcNDyZCilpFKxA0sfcW0PpcUyp9Zr +yjybnFX13BK+wAz6QJlR8Jt1teGPY0QQkMHCWy2+vIhVTJwYKiY3buddXjFh38WnpfKyx4m/YL Ix6DXlaxI2UpALXSb/F43kfr5QkzkIaenLOyEihdCY0krZIbmwbsDqM5kmj1OGgRkJ44NDhh6qZ vBqQP4A7Xs8CQWnkFhGawqp3Q2t+4TSbBYqjYkcoIwT8Wpqd4EzhhezQ== X-Gm-Gg: ASbGnctFK32wBno7+VRN/1zzOYjalDLXywXAUrH3fru8SHeIp1JUuiza9ze0oykkARo QV2xBI3SM15Xc82CrOzP09iGEjjk+pUBp9ExLO6TE853T8t0wo00OPKSl4jFYTckbJY8VqdIDbZ 5nuLh+69B7VQ6j4GXyagpVmCKNkopEerT/IkbjOa6BJa2ZSB+P619Q/0uq0/GLuHzSlRnUFEnV1 b3cGX56KlKUi33ewMi0+7a6fmlH3BKLP9nDPA== X-Google-Smtp-Source: AGHT+IH1xwrjIvltdziVwrI+YtxhVeeyiF8D7uxUwXoaEEB10E+c1BHmgERGTODoAWUfaC1UncDc52thkwlfLIdJrTI= X-Received: by 2002:a05:6402:5106:b0:638:e8af:35d9 with SMTP id 4fb4d7f45d1cf-639d5c3e994mr13583482a12.23.1760174259949; Sat, 11 Oct 2025 02:17:39 -0700 (PDT) MIME-Version: 1.0 References: <190A13D4-022B-4323-B30D-027B0D931DAF@hellug.gr> In-Reply-To: From: Cornelia Biacsics Date: Sat, 11 Oct 2025 11:17:28 +0200 X-Gm-Features: AS18NWApMda68W9oz7Hy2TfYB7uvCYr_4UWLQD1y_CuA0Ptw6ZbNUAY4AY1qagY Message-ID: Subject: Re: PostgreSQL Contributor levels To: pgsql-www@lists.postgresql.org Cc: Jimmy Angelakos , Christoph Berg , PostgreSQL Contributors Content-Type: multipart/alternative; boundary="00000000000081e6600640de81cf" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000081e6600640de81cf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dear all, As part of the ongoing discussion on recognizing PostgreSQL contributors, I=E2=80=99d like to propose a structured framework that reflects both the f= ield and the extent of contributions. And as Bruce already mentioned: PostgreSQL=E2=80=99s success depends on a b= road range of contributors. It includes working on infrastructure, documentation, testing, events, and community growth and a lot more. 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. Proposed Recognition Framework (examples ...) 1. Code Contributions Recognition per major version release (PG18 Code Contributor, PG19 Code Contributor,, ...) Categories by volume or impact (example): * Bronze: 1=E2=80=934 commits or patches accepted * Silver: 5=E2=80=9314 commits or patches accepted * Gold: 15+ commits, or major feature lead / reviewer 2. Infrastructure and Operations Measured by active maintenance periods or completed initiatives. * Bronze: contributed to 1 project (e.g. CI job, website update) * Silver: ongoing work for 6+ months * Gold: long-term or leadership role in infrastructure operations 3. Documentation and Translation Based on number or size of contributions: * Bronze: 1=E2=80=932 pages / translations / updates * Silver: 3=E2=80=935 substantial updates or sections * Gold: primary authorship or large documentation refactor 4. Community and Events For conference organization, volunteer roles, or community moderation. * Bronze: contributed to 1 event * Silver: part of 2=E2=80=933 events or continuous local engagement * Gold: lead organizer, multi-event coordination, or cross-region involvement 5. Marketing and Outreach Recognizing those who expand PostgreSQL=E2=80=99s visibility and reach. * Bronze: 1 campaign or article * Silver: 3+ campaigns, regular promotional efforts * Gold: sustained leadership or strategic impact in community visibility 6. Testing and Quality Assurance Based on frequency and impact of testing contributions. * Bronze: 1 round of participation (bug reports, test feedback) * Silver: regular testing over multiple versions * Gold: maintaining or coordinating test infrastructure / major QA lead 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 =E2=80=94 from code and testing to marketing, documentation, and community engagement. When it comes to displaying the level and type of contributions: we are anyway working on digital badges which could now reflect the different levels (bronze, silver, gold). Further, I=E2=80=99d like to bring another aspect into the discussion about contributor recognition =E2=80=94 acknowledging company-level (commercial) contributions to PostgreSQL. Many companies make a significant impact by increasing PostgreSQL=E2=80=99s 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=E2=80=99s growth a= nd sustainability. A possible framework would be the following (as an example) * Bronze Partner: consistent but limited contribution (e.g., 1=E2=80=932 en= gineers involved or support for one community initiative) * Silver Partner: moderate involvement (e.g., multiple engineers, event sponsorships, or regular contributions in two categories) * Gold Partner: significant, ongoing contribution (e.g., sustained technical work + infrastructure or community sponsorship over multiple years). Kind regards, Cornelia Biacsics On Sat, Oct 11, 2025 at 10:50=E2=80=AFAM Christoph Berg w= rote: > Re: Jimmy Angelakos > > Hi Christoph, > > > > I think "Significant Contributor" fits in between "Major Contributor" > and "Contributor". > > > > "Sustained" has a time element and sounds terrible on a CV :-) , and > "Recognised" is kind of redundant, since they're all recognition levels. > > Hi, > > sorry for the long silence here, it's been holiday and conferences and > work travel here for too long. > > We liked the "Significant" idea very much and had almost already > settled on it when a new one came up: Notable Contributor. The levels > would then be: > > Major Contributor > Notable Contributor > Contributor (see the other subthread) > > How do people like that? > > Frankly, "Significant" was apparently not sticking in anyone's brain, > we constantly had to look it up again because it was competing with > the other S-words "Sustained" and "Substantial". (Though I guess that > would work out if we actually chose it.) > > Christoph > > > > > --=20 *E-Mail Disclaimer* Der Inhalt dieser E-Mail ist ausschliesslich fuer den=20 bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat= =20 dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte,=20 dass jede Form der Kenntnisnahme, Veroeffentlichung, Vervielfaeltigung oder= =20 Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten Sie, sich= =20 in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen. *CONFIDENTIALITY NOTICE & DISCLAIMER *This message and any attachment are=20 confidential and may be privileged or otherwise protected from disclosure= =20 and solely for the use of the person(s) or entity to whom it is intended.= =20 If you have received this message in error and are not the intended=20 recipient, please notify the sender immediately and delete this message and= =20 any attachment from your system. If you are not the intended recipient, be= =20 advised that any use of this message is prohibited and may be unlawful, and= =20 you must not copy this message or attachment or disclose the contents to=20 any other person. --00000000000081e6600640de81cf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,

As part of the ongoing discus= sion on recognizing PostgreSQL contributors, I=E2=80=99d like to propose a = structured framework that reflects both the field and the extent of contrib= utions.

And as Bruce already mentioned: PostgreSQL=E2=80=99s success= depends on a broad range of contributors. It includes=C2=A0working on infr= astructure, documentation, testing, events, and community growth and a lot = more.=C2=A0

I would first suggest defining=C2=A0fi= elds of contributions (as you somehow already have listed here: https://www.postgr= esql.org/about/policies/contributors/). And then define sub-levels of a= chievements (e.g. Bronze, Silver, Gold) based on the intensity or amount of= contributions in this category.=C2=A0
Recognizing contributors b= ased on the nature and level of their work would ensure fair and meaningful= appreciation across the ecosystem.

Proposed Recognition Framework (= examples ...)=C2=A0

1. Code Contributions
Recognition per = major version release (PG18 Code Contributor, PG19 Code Contributor,, ...)<= /div>
Categories by volume or impact (example):
* Bronze: 1=E2=80=93= 4 commits or patches accepted
* Silver: 5=E2=80=9314 commits or patches = accepted
* Gold: 15+ commits, or major feature lead / reviewer

2.= Infrastructure and Operations
Measured by active maintenance periods or= completed initiatives.
* Bronze: contributed to 1 project (e.g. CI job,= website update)
* Silver: ongoing work for 6+ months
* Gold: long-te= rm or leadership role in infrastructure operations

3. Documentation = and Translation
Based on number or size of contributions:
* Bronze: 1= =E2=80=932 pages / translations / updates
* Silver: 3=E2=80=935 substant= ial updates or sections
* Gold: primary authorship or large documentatio= n refactor

4. Community and Events
For conference organization, v= olunteer roles, or community moderation.
* Bronze: contributed to 1 even= t
* Silver: part of 2=E2=80=933 events or continuous local engage= ment
* Gold: lead organizer, multi-event coordination, or cross-region i= nvolvement

5. Marketing and Outreach
Recognizing those who expand= PostgreSQL=E2=80=99s visibility and reach.
* Bronze: 1 campaign or arti= cle
* Silver: 3+ campaigns, regular promotional efforts
* Gold: susta= ined leadership or strategic impact in community visibility

6. Testi= ng and Quality Assurance
Based on frequency and impact of testing contri= butions.
* Bronze: 1 round of participation (bug reports, test feedback)=
* Silver: regular testing over multiple versions
* Gold: maintaining= or coordinating test infrastructure / major QA lead

Contributors ca= n collect multiple badges across different categories, showcasing the bread= th of their involvement and celebrating their growing impact within the Pos= tgreSQL ecosystem. Which also=C2=A0adds a light gamification aspect to reco= gnition, inspiring contributors to explore multiple areas of PostgreSQL =E2= =80=94 from code and testing to marketing, documentation, and community eng= agement.=C2=A0

When it comes to displaying the level and type= of contributions: we are anyway working on=C2=A0digital badges which could= now reflect the different levels (bronze, silver, gold).=C2=A0

Furt= her, I=E2=80=99d like to bring another aspect into the discussion about con= tributor recognition =E2=80=94 acknowledging company-level (commercial) con= tributions to PostgreSQL.
Many companies make a significant impact by in= creasing PostgreSQL=E2=80=99s visibility and awareness, which ultimately he= lps the entire ecosystem thrive. Recognizing these efforts would highlight = the essential role that commercial contributors play in supporting the comm= unity=E2=80=99s growth and sustainability.
A possible framework w= ould be the following (as an example)=C2=A0
* Bronze Partner: con= sistent but limited contribution (e.g., 1=E2=80=932 engineers involved or s= upport for one community initiative)
* Silver Partner: moderate involvem= ent (e.g., multiple engineers, event sponsorships, or regular contributions= in two categories)
* Gold Partner: significant, ongoing contribution (e= .g., sustained technical work + infrastructure or community sponsorship ove= r multiple years).

Kind regards,
Cornelia=C2=A0=
Biacsics



On Sa= t, Oct 11, 2025 at 10:50=E2=80=AFAM Christoph Berg <myon@debian.org> wrote:
Re: Jimmy Angelakos
> Hi Christoph,
>
> I think "Significant Contributor" fits in between "Majo= r Contributor" and "Contributor".
>
> "Sustained" has a time element and sounds terrible on a CV := -) , and "Recognised" is kind of redundant, since they're all= recognition levels.

Hi,

sorry for the long silence here, it's been holiday and conferences and<= br> work travel here for too long.

We liked the "Significant" idea very much and had almost already<= br> settled on it when a new one came up: Notable Contributor. The levels
would then be:

Major Contributor
Notable Contributor
Contributor (see the other subthread)

How do people like that?

Frankly, "Significant" was apparently not sticking in anyone'= s brain,
we constantly had to look it up again because it was competing with
the other S-words "Sustained" and "Substantial". (Thoug= h I guess that
would work out if we actually chose it.)

Christoph





E-Mail Disclaimer
Der Inhalt dieser E-Mail ist aus= schliesslich fuer den bezeichneten Adressaten bestimmt. Wenn Sie nicht der = vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein sollten, so b= eachten Sie bitte, dass jede Form der Kenntnisnahme, Veroeffentlichung, Ver= vielfaeltigung oder Weitergabe des Inhalts dieser E-Mail unzulaessig ist. W= ir bitten Sie, sich in diesem Fall mit dem Absender der E-Mail in Verbindun= g zu setzen.

CONFIDENTIALITY NOTICE & DISCLAIMER
T= his message and any attachment are confidential and may be privileged or ot= herwise protected from disclosure and solely for the use of the person(s) o= r 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 a= nd 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 prohibit= ed and may be unlawful, and you must not copy this message or attachment or= disclose the contents to any other person. --00000000000081e6600640de81cf--