public inbox for [email protected]  

help / color / mirror / Atom feed

From: Christoph Berg <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: [email protected]
Cc: Andrey Borodin <[email protected]>
Cc: Melanie Plageman <[email protected]>
Cc: PostgreSQL Contributors <[email protected]>
Subject: Re: Introduce contributor badges
Date: Tue, 28 Apr 2026 15:06:14 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CABUevEzgNKBdKySvuzn9diZMeEyyCNM6EWC9JZpse_AZPgk1hQ@mail.gmail.com>
References: <CAAKRu_aQ4Frj2v+i7GciMmmUOx5kjBi_FyuudRdPqqCDP7Y5Hw@mail.gmail.com>
	<CABUevExk=h0gLboP8D0XQk9kv-HSDkM30tv4zoHZvuhznXfUvg@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CABUevEzgNKBdKySvuzn9diZMeEyyCNM6EWC9JZpse_AZPgk1hQ@mail.gmail.com>

Re: Magnus Hagander
> Given the fairly substantial concerns raised ofer this during in-person
> discussions at FOSDEM, please do *not* commit this until you have signoff
> from those involved. (It might be that it's fine, but given the concerns
> and discussions around it, let's make sure those are resolved).

I said in the other thread:

> The last result (from the lunch discussion in Brussels) was that we
> need handling of retired people from "permanent" badges like "Sysadmin
> Team". That's not included yet, but in the team, we concluded that
> instead of some complicated date range handling (perhaps that's what
> you remember as plenty?) we can just add a single boolean "retired"
> flag. We don't have that yet, but that's not a big blocker.

I've now implemented retiring from badges. Internally it's tracked by
filling in a date_retired field, but in order not to overcomplicate
the user interface, it's treated as a boolean. Retirees still show up
in badge listing, but are marked as retired.

Removing people from badges is now a two-stage process, retire them
and then remove them. To un-retire someone, add their email address
again (which NULLs the date_retired field).

I'm attaching that as a separate commit for better review. It would
get squashed before committing, of course.

I believe that addresses the concerns from Brussels, or was there
anything else?

Christoph


Attachments:

  [application/gzip] v6-0001-Introduce-contributor-badges.patch.gz (10.8K, ../[email protected]/2-v6-0001-Introduce-contributor-badges.patch.gz)
  download

  [application/gzip] v6-0002-Add-dates-on-badgeholders-so-people-can-be-retire.patch.gz (4.9K, ../[email protected]/3-v6-0002-Add-dates-on-badgeholders-so-people-can-be-retire.patch.gz)
  download

view thread (11+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Introduce contributor badges
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox