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 1xFFWS-00000001VPw-412I for pgsql-www@arkaria.postgresql.org; Fri, 09 Oct 2026 18:40:49 +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 1xFFWR-00000000vnd-2P72 for pgsql-www@arkaria.postgresql.org; Fri, 09 Oct 2026 18:40:47 +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 1xFFWR-00000000vnR-1D0m; Fri, 09 Oct 2026 18:40:47 +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 1xFFWO-00000001CjW-3JnT; Fri, 09 Oct 2026 18:40:46 +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-Transfer-Encoding: Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Reply-To:Content-ID:Content-Description; bh=U7GfvrN6RNUslZNE4UBo51b5lGDu9/AT/SHZxiTElK8=; b=iHSrUwzA/UxVzqpgEKuRL8ltuU vyLv/Vo63oDGgIsM1KtNVlvfHjfHFQwlAFF0MzHESxiT012BZe/0i+skdgdxsxh1atNT5isicsSJ/ hllDPZE4kfAXhITwZ9hiB3+nL9HVs18aGjSaI9XQ4ipgbjzs7CzHjiSwSOY/0ZIbVWSttvUTrAKgJ YJ4shduHLS9CG8AmD8T6NWBrZGE8i96yUwPE3uvI1JLp6y+3Gqe+fJLhNKzihlM8STgThATuCqT/t zl6la0M0ek41GIenY4UszeRNT7D4dcs87FsdDTYbFIQY3FB3onu801NzRm4u50uxBJZFsb7fuLdDn DDLhMx/A==; 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 1xFFWF-000jQ8-0Z; Fri, 09 Oct 2026 18:40:36 +0000 Date: Fri, 9 Oct 2026 20:40:33 +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> <9E423E7C-9EF6-4C43-BC86-6CAEB902CC9C@yesql.se> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9E423E7C-9EF6-4C43-BC86-6CAEB902CC9C@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 > + "badge", > + models.CharField( > + help_text='Title of this badge, e.g. "PGConf.EU 2025 Speaker".', > + max_length=32, > > Will 32 characters be enough for all purposes? A "Nordic PGDay 2026 Program > Committee" badge as an example would require more than 32, and I can imagine > others like that. It's good that submissions need to be creative to fit within > a constraint, but we also don't want to end up with needlessly abbreviated > badges. Thanks for the example. One goal here is to have the titles not make the grid of badges on the people page not explode, but it should of course not be too restrictive. I guess we need to bump this. (I would rather limit the length per moderation than technically.) > + pgweb.util.fields.ImageBinaryField( > + blank=True, > + help_text="Square image, will be auto-scaled to 150×150. JPEG or PNG, up to 1 MB. When left blank, the Slony logo will be used.", > > While Slony was a great tool back i the day, I think you mean "Slonik logo" > here =) I wonder though, will everyone be familiar with "Slonik" or should we > just say "PostgreSQL logo"? PostgreSQL logo is better, yes. > I also fear that allowing 1MB large image files > opens the risk for getting detailed and feature rich submissions which will > look terrible in 150x150. Is that the problem of the limit? People could submit terrible things even at smaller scales. (Again, perhaps a question for moderation.) > + models.CharField( > + blank=True, > + help_text="Contact address (email, URL, other) for people who want to be added as badge holder", > > Should we keep it simple and limit this to email for now? If we encourage > people to visit third party sites we don't control in order to control behavior > on our site then we need to verify said sites. This would usually be something like https://2026.pgconf.eu/contact/, so be in community control. It's also shown at moderation time and part of the notification emails sent when edited post-moderation (I think, I don't get moderation email yet). So I think we don't need to be overly restrictive here. Allowing URLs also enables events without a persistent email address. > - help_text='This description is currently used for major contributors only') > + help_text='Describe what you did in the PostgreSQL community') > > This reads like focusing on the past like adding an Alumni entry, shouldn't > this be more like "Describe your involvement in the PostgreSQL community"? Sounds good. > + {%for u in holders.all%} > +
  • {%if u.date_retired%}{%endif%}{{u.user.contributor.firstname}} {{u.user.contributor.lastname}}{%if u.date_retired%} (retired from this activity){%endif%}
  • > + {%endfor%} > > Rather than wrapping the entry with a conditional it seems like a cleaner > solution to use the condition to set a CSS class which controls the rendering. > This is more a nice-to-have of course. Ack. > +

    People are listed in alphabetical order.

    > > s/People/Contributors/ ? We deliberately don't say "Contributor" there to keep the perceived distance to the original now-"recognized" contributors list greater. Of course everyone in that list did contribute, so this is maybe splitting hairs... > + If you are listed and want to claim your profile page, write a mail including your community account name to > + contributors@postgresql.org. > > Shouldn't this (and a previous instance of webmaster@) use the hidemail filter > for consistency? Ack. > contribution = models.TextField(null=True, blank=True, > - help_text='This description is currently used for major contributors only') > + help_text='Describe what you did in the PostgreSQL community') > > When opening this up to a lot more people than the major contributors, this > field should probably be sanitized when saved (and possibly when read as well) > to keep malicious content out. Maybe that's already done today and I'm plain > missing that, but if not we need to do that IMO. It's already html-escaped. I was thinking of allowing markdown in the future (and render only the first paragraph in the recognized contributors page), but then we'll have the question of links etc again. The answer we settled on when we discussed that with Magnus was that post-moderation by reading the change emails is good enough. Anyone on that list did something positive for the community, and they will not want to get kicked out for doing something evil with their profile page. > I'll revisit the remaining parts in a follow-up look. Thanks! Christoph