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.96) (envelope-from ) id 1viAN9-00H3e4-0j for pgsql-www@arkaria.postgresql.org; Tue, 20 Jan 2026 11:58:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1viAN8-000zxl-12 for pgsql-www@arkaria.postgresql.org; Tue, 20 Jan 2026 11:58:10 +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.96) (envelope-from ) id 1viALO-000qhX-2N; Tue, 20 Jan 2026 11:56:23 +0000 Received: from forwardcorp1d.mail.yandex.net ([178.154.239.200]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1viALK-001PjM-1W; Tue, 20 Jan 2026 11:56:21 +0000 Received: from mail-nwsmtp-smtp-corp-main-68.klg.yp-c.yandex.net (mail-nwsmtp-smtp-corp-main-68.klg.yp-c.yandex.net [IPv6:2a02:6b8:c42:94a9:0:640:a3fa:0]) by forwardcorp1d.mail.yandex.net (Yandex) with ESMTPS id 2CCE180833; Tue, 20 Jan 2026 14:56:15 +0300 (MSK) Received: from smtpclient.apple (unknown [2a02:6bf:8080:c5e::1:15]) by mail-nwsmtp-smtp-corp-main-68.klg.yp-c.yandex.net (smtpcorp/Yandex) with ESMTPSA id DuYHct1ArqM0-NGDnQSnj; Tue, 20 Jan 2026 14:56:14 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1768910174; bh=0JXYbsxcONjp9S3qipOnnIxQQ/iovng8q/5wH/4p7aQ=; h=Message-Id:To:Date:References:Cc:In-Reply-To:From:Subject; b=NGG98RvtSxMToIynhhd0LwNAduekb+he2RIP5F5n1kSzmkU1mWcLKri3rDbNAXcod K2d5h2qBiNBpIuzsD2uwvLemy5z2V4ljQ//Zneub+9C9jsorLP/bHW0IPq07u33+AL lSKAQa4fRTq8sdhjnBvMQ/APcH6/KgIB1oDAgsKc= Authentication-Results: mail-nwsmtp-smtp-corp-main-68.klg.yp-c.yandex.net; dkim=pass header.i=@yandex-team.ru Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81.1.4\)) Subject: Re: Introduce contributor badges From: Andrey Borodin In-Reply-To: Date: Tue, 20 Jan 2026 16:56:03 +0500 Cc: Magnus Hagander , Melanie Plageman , pgsql-www@lists.postgresql.org, PostgreSQL Contributors Content-Transfer-Encoding: quoted-printable Message-Id: <7DF542FC-E797-4050-B204-7755AEFDFF4A@yandex-team.ru> References: To: Christoph Berg X-Mailer: Apple Mail (2.3826.700.81.1.4) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 19 Jan 2026, at 21:28, Christoph Berg wrote: >=20 > Over the holidays, I used the time to implement the badges idea. We've > discussed in the team and we are happy with how it looks like now, and > I'm attaching the version with the changes from the last contributors > team meeting. 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/ ogin:moderator pwd:moderator123=20 orgmanager1 manager123=20 orgmanager2 manager123=20 alice alice123 -- Has 3 badges + profile page bob bob123 -- Has 2 bandges charlie charlie123 -- 2 badges, without profile I'm slightly worried that user does not approve their badges. Also do we plan to add a page where user can claim a badge so org admin = can approve their claim? And I find it a bit oxymoron: "Basic contributor, not recognized" Best regards, Andrey Borodin.=