MIME-Version: 1.0
References: <aJ9ur1eSnk5pp9aD@msg.df7cb.de>
 <190A13D4-022B-4323-B30D-027B0D931DAF@hellug.gr>
 <aOj5NNxXdghSX66R@msg.df7cb.de>
 <CALaz2ZsLQLbw6Pv714DyO8rTJfLF=nhC0BmHV4OhsurkrhLVKg@mail.gmail.com>
 <CAAKRu_ZZsJVYdjvhPVSBQiB+oV7yy-fC7Hno6JgVFJ43utOpXw@mail.gmail.com>
In-Reply-To: 
 <CAAKRu_ZZsJVYdjvhPVSBQiB+oV7yy-fC7Hno6JgVFJ43utOpXw@mail.gmail.com>
From: Cornelia Biacsics <cornelia.biacsics@cybertec.at>
Date: Sun, 12 Oct 2025 10:32:06 +0200
Message-ID: 
 <CALaz2Zs4rhV15xhP24NGUEvj2zSPoqOZ0asQ46xJL_GfH6FNFQ@mail.gmail.com>
Subject: Re: PostgreSQL Contributor levels
To: Melanie Plageman <melanieplageman@gmail.com>
Cc: pgsql-www@lists.postgresql.org,
	PostgreSQL Contributors <contributors@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000170b820640f1fd49"
Archived-At: 
 <https://www.postgresql.org/message-id/CALaz2Zs4rhV15xhP24NGUEvj2zSPoqOZ0asQ46xJL_GfH6FNFQ%40mail.gmail.com>
Precedence: bulk

--000000000000170b820640f1fd49
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFPM Melanie Plageman <melanieplageman@g=
mail.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=E2=80=AFAM Cornelia Biacsics
> <cornelia.biacsics@cybertec.at> wrote:
> >
> > As part of the ongoing discussion on recognizing PostgreSQL
> contributors, I=E2=80=99d like to propose a structured framework that ref=
lects 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 =E2=80=94 new things will come up as new possibilities arise. Th=
is list
is subject to change over time, and I=E2=80=99m sure it is possible to cove=
r 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=E2=80=99d say you=E2=80=99d 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=E2=80=99d say yes. But =
you=E2=80=99re
absolutely right =E2=80=94 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=E2=80=99ve recently seen a program for continuous personal development =
to
maintain a certain status =E2=80=94 and yes, in that case you have to submi=
t proof
through a system. I agree, it=E2=80=99s a bit of an overhead, and it probab=
ly
depends on how far you really want to go with recognizing and developing
the contributor program.

> And as Bruce already mentioned: PostgreSQL=E2=80=99s 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 =E2=80=94 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=E2=80=99d like to bring another aspect into the discussion a=
bout
> 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=
 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=E2=80=99d be happy to discus=
s the
details further with you and offer any additional help.

Best wishes
Cornelia

--=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.

--000000000000170b820640f1fd49
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hello Melanie, thanks a lot for taking th=
e time to look at my proposal.</div><div>Please find some comments below.=
=C2=A0</div><div dir=3D"ltr"><br></div><div class=3D"gmail_quote gmail_quot=
e_container"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Oct 11, 2025 at =
6:04=E2=80=AFPM Melanie Plageman &lt;<a href=3D"mailto:melanieplageman@gmai=
l.com">melanieplageman@gmail.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">Thanks, Cornelia for thinking about this a=
nd taking the time to put<br>
together a proposal. The Contributors Committee is always happy to<br>
have people putting work into recognizing people in the community.<br>
<br>
On Sat, Oct 11, 2025 at 5:17=E2=80=AFAM Cornelia Biacsics<br>
&lt;<a href=3D"mailto:cornelia.biacsics@cybertec.at" target=3D"_blank">corn=
elia.biacsics@cybertec.at</a>&gt; wrote:<br>
&gt;<br>
&gt; As part of the ongoing discussion on recognizing PostgreSQL contributo=
rs, I=E2=80=99d like to propose a structured framework that reflects both t=
he field and the extent of contributions.<br>
<br>
In my opinion, the issue with structured frameworks is that not<br>
everything fits in them and it makes it harder, not easier, to<br>
recognize different kinds of contributions.<br>
What about hosting a Postgres podcast or an educational youtube<br>
series? Is that considered marketing for the community? What if it is<br>
sponsored fully by your employer and includes some promotion of your<br>
employer (i.e. it isn&#39;t really a community podcast even though it is<br=
>
about Postgres)? That means the Contributors Committee has to discuss<br>
every badge before awarding it.=C2=A0<br></blockquote><div><br></div><div>A=
bsolutely =E2=80=94 new things will come up as new possibilities arise. Thi=
s list is subject to change over time, and I=E2=80=99m sure it is possible =
to cover many of the existing contributions on it.=C2=A0</div><div>(my list=
 contained examples)=C2=A0</div><div><br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">
<br>
Or take commits -- should someone with 4 typo patches accepted get<br>
recognized at the same level as someone who wrote 4 features or who<br>
identified 4 critical bugs? Who defines what a lead reviewer is?<br></block=
quote><div><br></div><div>Probably not (not my field of expertise), but thi=
s is also subject to evaluation or calculation criterias.=C2=A0=C2=A0</div>=
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Or what about combinations of contributions? Aren&#39;t you a gold level<br=
>
contributor if you work at the Postgres booth at conferences, author<br>
10 commits to every release for 10 years, volunteer on multiple<br>
organizing committees, and run a PUG? But you may not qualify as gold<br>
in any one category.<br></blockquote><div><br></div><div>In this case, I=E2=
=80=99d say you=E2=80=99d receive a Gold Code Contributor badge, and a seco=
nd one (Ambassador badge or whatever name it will receive), level is based =
on the number of individual contributions in this category. This way, contr=
ibutors can earn badges across different categories.</div><div>=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
And if we stick strictly to the definitions, what about contractors<br>
who are paid by the community to do legal work for over a year? Do<br>
they automatically qualify for Infrastructure and Operations badges?<br>
Or someone who is paid to design a logo for a community conference?<br>
<br></blockquote><div>Are they currently listed as contributors? Then I=E2=
=80=99d say yes. But you=E2=80=99re absolutely right =E2=80=94 the rules ne=
ed to be defined.<br>
Probably quite similar to how you=C2=A0handle=C2=A0this at the moment.=C2=
=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>
We would have to make individual judgment calls on every one of these,<br>
which means we can&#39;t automate it, which means it will be woefully out<b=
r>
of date if the Contributors Committee doesn&#39;t have one person working<b=
r>
full time on this.<br>
<br></blockquote><div>I=E2=80=99ve recently seen a program for continuous p=
ersonal development to maintain a certain status =E2=80=94 and yes, in that=
 case you have to submit proof through a system. I agree, it=E2=80=99s a bi=
t of an overhead, and it probably depends on how far you really want to go =
with recognizing and developing the contributor program.=C2=A0</div><div><b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
&gt; And as Bruce already mentioned: PostgreSQL=E2=80=99s success depends o=
n a broad range of contributors. It includes working on infrastructure, doc=
umentation, testing, events, and community growth and a lot more.<br>
<br>
Absolutely. It is so important to recognize all types of contribution.<br>
<br>
&gt; I would first suggest defining fields of contributions (as you somehow=
 already have listed here: <a href=3D"https://www.postgresql.org/about/poli=
cies/contributors/" rel=3D"noreferrer" target=3D"_blank">https://www.postgr=
esql.org/about/policies/contributors/</a>). And then define sub-levels of a=
chievements (e.g. Bronze, Silver, Gold) based on the intensity or amount of=
 contributions in this category.<br>
&gt; Recognizing contributors based on the nature and level of their work w=
ould ensure fair and meaningful appreciation across the ecosystem.<br>
<br>
I&#39;m not sure if specifically recognizing and ranking people based on<br=
>
the nature of their work would ensure fair appreciation. I think there<br>
is a chance that slicing and dicing to this level emphasizes the<br>
difference of different types of contributions -- not their equal<br>
importance as part of a holistic whole. Though I think the difficulty<br>
of executing this kind of system is a bigger concern.<br>
<br>
That being said, I understand if some people want recognition of the<br>
area that they are active in. To that end, we are working on a feature<br>
similar to the idea of badges.</blockquote><div>=C2=A0</div><div>It would a=
t least make the different types of contributions more visible and tangible=
, in my opinion.</div><div>
<p></p></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
&gt; Contributors can collect multiple badges across different categories, =
showcasing the breadth of their involvement and celebrating their growing i=
mpact 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, an=
d community engagement.<br>
<br>
The Contributors Committee agrees with this. We are currently working<br>
on a project for some kind of granular badges or tags like &quot;PGConf EU<=
br>
2026 Volunteer&quot; or &quot;Postgres 18 Code Contributor&quot; that peopl=
e can<br>
self-nominate and be approved for having on their contributor profile.<br>
We weren&#39;t imagining levels for each one, but more like specific tasks<=
br>
or roles people have had. We think you&#39;re right about the gamification<=
br>
and also recognizing people for contributing in multiple ways and<br>
inspiring them to get involved in more ways.<br>
<br>
We could definitely use help with this and anyone who is interested<br>
(especially interested in the www development component should email<br>
us). We haven&#39;t sent an email about it yet because the idea is still<br=
>
in the early stages.<br></blockquote><div><br></div><div>Thank you.=C2=A0</=
div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
&gt; Further, I=E2=80=99d like to bring another aspect into the discussion =
about contributor recognition =E2=80=94 acknowledging company-level (commer=
cial) contributions to PostgreSQL.<br>
&gt; Many companies make a significant impact by increasing PostgreSQL=E2=
=80=99s visibility and awareness, which ultimately helps the entire ecosyst=
em thrive. Recognizing these efforts would highlight the essential role tha=
t commercial contributors play in supporting the community=E2=80=99s growth=
 and sustainability.<br>
<br>
If I&#39;m understanding your idea, there is already a concept like this<br=
>
called &quot;Sponsors&quot; [1].<br>
<br></blockquote><div>Oh! Thanks for that!=C2=A0</div><div>=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">
- Melanie<br>
<br>
[1] <a href=3D"https://www.postgresql.org/about/sponsors/" rel=3D"noreferre=
r" target=3D"_blank">https://www.postgresql.org/about/sponsors/</a></blockq=
uote><div><br></div><div>Overall, thank you very much for your reply. I=E2=
=80=99d be happy to discuss the details further with you and offer any addi=
tional help.</div><div><br></div><div>Best wishes</div><div>Cornelia=C2=A0=
=C2=A0</div></div></div>

<br>
<div><hr></div><b>E-Mail Disclaimer</b><br>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.<br><br><hr><b>CONFIDENTIALITY NOTICE &amp; DISCLAIMER<br></b>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.
--000000000000170b820640f1fd49--