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 1xDk5l-00000000gGv-3VHd for pgsql-www@arkaria.postgresql.org; Mon, 05 Oct 2026 14:55:01 +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 1xDk5k-0000000BLqX-3Lky for pgsql-www@arkaria.postgresql.org; Mon, 05 Oct 2026 14:55:00 +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 1xDk5k-0000000BLqB-2H3f; Mon, 05 Oct 2026 14:55:00 +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 1xDk5h-00000000Ugr-3cAR; Mon, 05 Oct 2026 14:54:59 +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=Xy6MEoJb+2tu0dJ4AXZHKyZU7EQtgjx3VtGtWRB/lbg=; b=lWfrpstlWLHHWD+5S6UK91BinN 4WNYpvppWA7lxVswvB5po8rEgekv3MBzSNXBhMJfaFZZKzZMw48tsy6tNuTIhtbbxG9yDZjowAlpa zjPR4tIfeN+0364vUwDrb9+QEl7Y7YuKCkAIWaaXe8VPAcm1Rhb2soUvQ/G7tvTmTqaWFB5Vbw2cC e/S/lW7jXruFPwJmVLSVu42/njVywge272FeI6A4omtamiJSLIoMs34zA1pon5/VShHAQCkgF/bPA tyEHszIHmGN1g10nM2zmZxMbFpXwbj0Y44Tog+y9YQaQ/mGURBGCBxT4AwI4pBmn3EVP0jIKcsHTA 8cv042qA==; 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 1xDk5d-003GzZ-1g; Mon, 05 Oct 2026 14:54:53 +0000 Date: Mon, 5 Oct 2026 16:54:52 +0200 From: Christoph Berg To: Daniel Gustafsson Cc: Magnus Hagander , pgsql-www@lists.postgresql.org, Andrey Borodin , Melanie Plageman , PostgreSQL Contributors Subject: Re: Introduce contributor badges Message-ID: References: <55FAB574-1E9A-4B8F-8453-26BED1088BCB@yesql.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55FAB574-1E9A-4B8F-8453-26BED1088BCB@yesql.se> X-Debian-User: myon List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Re: Daniel Gustafsson > > I would like start merging this next week so we still have some time before > > pgconf.eu to evaluate. > > Having this in well before .eu sounds like a very good plan. Thanks. :) I pushed the first three patches now. Over the weekend I had done more polishing and fixing of some minor details, as well as several AI sessions walking through all workflows and confirming things worked. (They did.) This made me confident to proceed (and Magnus review at Lowlands sounded like he was ok with the general shape and I believe I addressed all the points he raised). The one non-trivial change still done was that badge URLs are now readable slugs instead of boring IDs. That change was small and targeted so it didn't feel like requiring another round of reviews. The slug is fixed on badge creation, so even renaming the badge title doesn't change it. (It is still admin-editable in the django interface.) So the badges infrastructure is in place now on postgresql.org. As said in the original plan, there are no links to it yet, so we can still check if everything really works as intended. Magnus remarked that he wants more review of the patch before we start adding actual badges, so please everyone check that everything is ok. The contributors committee still wants to announce the feature at pgconf.eu (which is 2 weeks from now), so it would be awesome if we had an answer by the end of this week, and we could add the first badges (PostgreSQL 19 Contributor?) next week. The point he raised from a 30s look was that changing the slug doesn't invalidate the URL from varnish. My stance on that is we don't really need to cover that because slug changes are rare (admin-interface only), and we can simply agree to not rename a badge slug after any users have been added. Also, the new URL works immediately, and the old one will eventually time out, and there should be nothing in there that needs immediate deletion (or else we should just edit it and that is properly purged). We could cover that, but that's more of an infrastructure change in the pgweb system handling news/events/.../and now badges. Christoph