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.98.2) (envelope-from ) id 1xHcnv-00000003CHv-3ITh for pgsql-www@arkaria.postgresql.org; Fri, 16 Oct 2026 07:56:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xHcnu-0000000DE1S-3H5X for pgsql-www@arkaria.postgresql.org; Fri, 16 Oct 2026 07:56:38 +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.98.2) (envelope-from ) id 1xHcnu-0000000DE1G-2KSO; Fri, 16 Oct 2026 07:56:38 +0000 Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xHcns-00000002IZU-1I8F; Fri, 16 Oct 2026 07:56:37 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=aCZhsRqGIkoIYHiaRaPxGrkI4N3dNcdzP0bWRfhGSzE=; b=UMauIug97DEj18xKRR3hBWlD7A k5Qoax5NsWXeJz7Hteb/lUufOcO6xVwrl05rZfh0Zcb7eNYyEyBuCkpM0TLjIDGBNopY1p1Cdcmot x0aDQuh1YIOazeNLohBMuN6SQZgpkHA3/o/9/CVzbYn+DRj5AAa/Zh6qRBWdRqM1Xg/vrr3TATC81 1tOvouOFP6tf5bzYGV349AglJuiGVTa7nwx83phAk9d61tLqgCNTRA3KfXVsVdVqxksYNK8aKp464 R4HJhVVO79IRhaZHTgWIMmwwch31ikfpJU/7QPW5R4RebdQmfy0+mcBCZ4FQs1JyRP0oyOL1gHfWQ ZC3fB4Zg==; Received: from authenticated-user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from ) id 1xHcnj-005ott-1h; Fri, 16 Oct 2026 07:56:27 +0000 Date: Fri, 16 Oct 2026 09:56:25 +0200 From: Christoph Berg To: Magnus Hagander Cc: "Jonathan S. Katz" , Daniel Gustafsson , pgsql-www@lists.postgresql.org, Andrey Borodin , Melanie Plageman , PostgreSQL Contributors Subject: Re: Introduce contributor badges Message-ID: References: <329b5d0e-44ba-4c5f-8cc9-c9eb5424955b@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Debian-User: myon List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Re: Magnus Hagander > I will point out that I *explicitly* asked that this system not be used > fully Fwiw, it is not fully in use yet. There are no links to badges or to the people page. There is not going to be a huge spike of requests because no one has these URLs yet. We are doing this precisely to allow looking at how it works in practise before the world runs over it. > until I had completed my review. I have *not* withdrawn this > requirement. AFAIK nobody has done the full review ont he impact this will > have on our caching setups and the production systems. Afaict the proper purge rules are in place, and the images have Etag headers. We can check all that once a badge is approved. (I had already submitted "PostgreSQL 18 Contributor" before your mail.) > If that is wrong, > then please point me to that. But if not, then my objection still stands, > and I am *not* happy that my *explicit* request to review production impact > was not honored. I still believe that we addressed all concerns. I was aware that you wanted more review, that's why we did that here. If that review was not enough going into that direction, I'm sorry - that's why we did it here openly on the list. Yes I know it's conference preparation time for you, but it should have been obvious that we were moving to putting this live, so just a "please do more review of X" line would have helped. Christoph