Date: Tue, 20 Jan 2026 13:11:13 +0100
From: Christoph Berg <myon@debian.org>
To: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: Magnus Hagander <magnus@hagander.net>,
	Melanie Plageman <melanieplageman@gmail.com>,
	pgsql-www@lists.postgresql.org,
	PostgreSQL Contributors <contributors@lists.postgresql.org>
Subject: Re: Introduce contributor badges
Message-ID: <aW9w4VAkIlIcmUeb@msg.df7cb.de>
References: 
 <CAAKRu_Z42AAq7N=usSS3UPMtXqbVvsQzktNmH1X20oypyqA_Xg@mail.gmail.com>
 <CABUevEzJqKgnRjHscDP1r8kr+04Nozh=HQ=c8SY6Eq7+V_+tqA@mail.gmail.com>
 <CAAKRu_aQ4Frj2v+i7GciMmmUOx5kjBi_FyuudRdPqqCDP7Y5Hw@mail.gmail.com>
 <CABUevExk=h0gLboP8D0XQk9kv-HSDkM30tv4zoHZvuhznXfUvg@mail.gmail.com>
 <aW5bm-4Dk6f-CvCT@msg.df7cb.de>
 <7DF542FC-E797-4050-B204-7755AEFDFF4A@yandex-team.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7DF542FC-E797-4050-B204-7755AEFDFF4A@yandex-team.ru>
Archived-At: 
 <https://www.postgresql.org/message-id/aW9w4VAkIlIcmUeb%40msg.df7cb.de>
Precedence: bulk

Re: Andrey Borodin
> Thanks for working on this! Looks great!
> I've setup preview version to test how things will look like. There's some generated sample data.
> 
> http://89.169.141.31:8000/community/people/alice/

Thanks, that makes review a bit easier for everyone else I guess.

The "people" page there has a problem:
http://89.169.141.31:8000/community/people/
It's not happening here, so I can't say if that's a bug in the patch.

> I'm slightly worried that user does not approve their badges.

The idea is that the badge itself needs approval and then is trusted.
So I think the worst thing that could happen is that someone
legitimately creates a "PostgreSQL Conf Antarctica Speaker", awards it
to you, but you don't want to publicly admit that you've been there.
Anything I'm missing?

> Also do we plan to add a page where user can claim a badge so org admin can approve their claim?

I think the basic workflow is that people contribute, an organisation
creates a badge for it and awards it to these people. For example,
after the PG19 release, we would create a "PostgreSQL 19 Contributor"
badge and award it to everyone listed in the release notes. Similarly
for conference speakers.

Maybe the other way round shouldn't be too easy so badge issuers don't
get flooded with requests. That's why we put the email link there.

Perhaps we need to make sure all approved badges have clear criteria
for badge holders. For example, "Has said something useful on the
mailing list" would be very fuzzy and invite request spam too much.

> And I find it a bit oxymoron: "Basic contributor, not recognized"

That's there to make the distinction to recognized contributors clear.
Better suggestions welcome.

Christoph