From: Christoph Berg <myon@debian.org>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: pgsql-www@lists.postgresql.org, Andrey Borodin <x4mmm@yandex-team.ru>
Cc: Melanie Plageman <melanieplageman@gmail.com>
Cc: PostgreSQL Contributors <contributors@lists.postgresql.org>
Subject: Re: Introduce contributor badges
Date: Mon, 12 Oct 2026 15:28:39 +0200
Message-ID: <aszgh1hJGT6bG7QU@msg.df7cb.de> (raw)
In-Reply-To: <6DA1DB71-95BA-4D04-9796-A46242B114FA@yesql.se> <9E423E7C-9EF6-4C43-BC86-6CAEB902CC9C@yesql.se>
Re: Daniel Gustafsson
> 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.
I've staged a bump to 64 (to match the max slug length). To keep the
migrations churn down, we should bundle that with the next database
update (or when we actually run into the limit).
> 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"? 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.
Changed to "PostgreSQL logo" in the attached patch.
> 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"?
Same.
> Rather than wrapping the entry with a conditional <em> 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.
... same.
> Shouldn't this (and a previous instance of webmaster@) use the
> hidemail filter for consistency?
None of the other static appearances of email addresses in the
codebase does that, the @postgresql.org strings are all there in
plain.
Re: Daniel Gustafsson
> >> 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.)
>
> They can, but it's a lot easier to mess up when working with an intermediate
> representation where the end result is a product of transformation. I would
> start with a more restrictive limit and possibly increase later rather than the
> other way around.
I'm unsure here. Which size limit would you suggest?
(TBH I think we shouldn't micro-manage this. If the badge logo looks
terrible, the submitter can still swap it later.)
> That's a fair argument, but "people" sound very generic and more like a
> decription of an unknown group. Maybe "Community members" or something else?
It currently looks like this:
http://localhost:8000/community/people/
People in the PostgreSQL Community
These are the fine people who have made contributions to PostgreSQL over the years.
Recognized Significant and Major Contributors are listed on the PostgreSQL Recognized Contributors page.
Bob Badgeholder · Christoph Berg · Pat Holder
... so before we say "fine people" there the heading and the URL that
already have "people" and put that into context. The wording isn't
mine, it's taken from the existing /community/contributors/ page and
frankly, "the fine community members" isn't that snappy.
> > 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.
>
> Markdown would be nice as a future improvement, if it can be restricted to not
> include links.
Ack. I'll keep that for the next iteration.
> >> I'll revisit the remaining parts in a follow-up look.
>
> A few further comments from a second read-through. I am not particularly
> Django-literate so I might well have missed something there.
>
> + re_path(r'^community/people/([^/]+)/$', pgweb.contributors.views.profile),
>
> Shouldn't this match the regexp for allowed characters in the username?
Most URL patterns in that file don't do that either, and if someone
tries a username that doesn't exist, they just get a 404 error.
> - <p>You can edit the information that's shown on the <a href="/community/contributors/" target="_blank" rel="noopener">contributors</a> page.
> + <p>You can edit the information that's shown on your <a href="/community/people/{{user.username}}/" target="_blank" rel="noopener">profile</a> page.
>
> Maybe nitpicking, but this will still be published on the
> community/contributors page for a subset of users. Should the text reflect
> that, possibly conditional on the the logged in users controbutor status?
The form and this text is only shown if the user already has a
contributor object in the database. Was that the question?
> To be consistent with modern HTML (where we are going with pgweb) I think the
> <input> should have an id attributed and a <label> for that attribute.
Done.
> +<h2>Getting added</h2>
> +{% if badge.org %}
> +<p>This badge is issued by <em>{{badge.org}}</em>.</p>
> +{%endif%}
> +
> +<p>If you think you should be listed
> + here, check your <a href="/account/profile/">account profile</a> page if the
> + badge is present there and activate your contribution profile page. If not,
> + contact the badge issuing organisation and ask to be added.</p>
> +
> +{% if badge.contact %}
> +<p>Contact information: <em>{{badge.contact}}</em>.</p>
> +{%endif%}
>
> A badge can be without both a contact and an org IIUC which, although highly
> unlikely, should probably be reflected in the template. Maybe the entire
> "Getting added" section should be omitted if .org and .contact are both blank?
The contact information might still be obvious from the context (like
asking the conference organizers), so I'd tend to leave it like it is.
(This is probably a question that is better answered once we have the
first concrete badges in to see how it feels in practise.)
> + <img src="{%if b.has_image %}/community/badge/{{b.slug}}/image/{%else%}/media/img/about/press/elephant.png{%endif%}">
>
> All <img> tags must have alt attributes to keep our accessibility score.
Done.
Thanks for the review!
What do you think about the open ends?
Attachments:
v12-0001-Contributor-copy-editing.patch - the stuff from this mail
v12-0001-Make-contributor-badges-discoverable.patch - what will
actually put the badges live
v12-0001-Extend-badge-title-to-64-chars.patch - future database fix
Assuming v12-0001-Contributor-copy-editing.patch is ok, would you
think that we can proceed with adding some badges now? My hope would
be to have at least "PostgreSQL 18 Contributor" live for Valencia.
Timeline:
after ack: apply v12-0001-Contributor-copy-editing.patch
this week: create initial badges, add holders
have badges approved in moderation (they are still not visible)
shortly before the conference: apply v12-0001-Make-contributor-badges-discoverable.patch
later: apply v12-0001-Extend-badge-title-to-64-chars.patch
Christoph
Attachments:download all (3 files, .tar.gz)v12-0001-Contributor-copy-editing.patch (text/x-diff, 10.1K) download
From fc08c159e2c0d570da307029cbc43660c86da1f5 Mon Sep 17 00:00:00 2001
From: Christoph Berg <myon@debian.org>
Date: Mon, 12 Oct 2026 15:14:39 +0200
Subject: [PATCH v12] Contributor copy-editing
Apply finding from Daniel's review:
* retired badge holders have a CSS class
* contribution field description is "Describe your involvement in the
PostgreSQL community"
* The logo is the PostgreSQL logo
* Badge images have an alt title
* "Create contributor profile" checkbox has a proper id and label
---
media/css/main.css | 3 +++
pgweb/contributors/migrations/0001_initial.py | 2 +-
...er_contributor_ctype_alter_contributor_email_and_more.py | 2 +-
pgweb/contributors/models.py | 4 ++--
templates/account/userprofileform.html | 4 ++--
templates/contributors/badge.html | 6 +++---
templates/contributors/people.html | 2 +-
templates/contributors/profile.html | 4 ++--
8 files changed, 15 insertions(+), 12 deletions(-)
diff --git a/media/css/main.css b/media/css/main.cssindex 9c4e24d8..a41632d2 100644--- a/media/css/main.css+++ b/media/css/main.css@@ -1758,6 +1758,9 @@ table.contributor-table thead tr th {
text-align: center;
padding: 4px;
}
+.badgeholder-retired {+ font-style: italic;+}
/* News archive */
#pgContentWrap span.newstag {
diff --git a/pgweb/contributors/migrations/0001_initial.py b/pgweb/contributors/migrations/0001_initial.pyindex 244e2e49..e2121892 100644--- a/pgweb/contributors/migrations/0001_initial.py+++ b/pgweb/contributors/migrations/0001_initial.py@@ -22,7 +22,7 @@ class Migration(migrations.Migration):
('company', models.CharField(max_length=100, null=True, blank=True)),
('companyurl', models.URLField(max_length=100, null=True, verbose_name='Company URL', blank=True)),
('location', models.CharField(max_length=100, null=True, blank=True)),
- ('contribution', models.TextField(null=True, blank=True, help_text='Describe what you did in the PostgreSQL community')),+ ('contribution', models.TextField(null=True, blank=True, help_text='Describe your involvement in the PostgreSQL community')),
],
options={
'ordering': ('lastname', 'firstname'),
diff --git a/pgweb/contributors/migrations/0005_alter_contributor_ctype_alter_contributor_email_and_more.py b/pgweb/contributors/migrations/0005_alter_contributor_ctype_alter_contributor_email_and_more.pyindex 75b002aa..87627ccb 100644--- a/pgweb/contributors/migrations/0005_alter_contributor_ctype_alter_contributor_email_and_more.py+++ b/pgweb/contributors/migrations/0005_alter_contributor_ctype_alter_contributor_email_and_more.py@@ -82,7 +82,7 @@ class Migration(migrations.Migration):
"imagedata",
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.",+ help_text="Square image, will be auto-scaled to 150×150. JPEG or PNG, up to 1 MB. When left blank, the PostgreSQL logo will be used.",
max_length=1000000,
null=True,
verbose_name="Image",
diff --git a/pgweb/contributors/models.py b/pgweb/contributors/models.pyindex 7ffc0881..7d55a0dc 100644--- a/pgweb/contributors/models.py+++ b/pgweb/contributors/models.py@@ -53,7 +53,7 @@ class Contributor(models.Model):
companyurl = models.URLField(max_length=100, null=True, blank=True, verbose_name='Company URL')
location = models.CharField(max_length=100, null=True, blank=True)
contribution = models.TextField(null=True, blank=True,
- help_text='Describe what you did in the PostgreSQL community')+ help_text='Describe your involvement in the PostgreSQL community')
user = models.OneToOneField(User, null=True, blank=True, on_delete=models.CASCADE)
send_notification = True
@@ -102,7 +102,7 @@ class Badge(TwostateModerateModel):
slug = models.SlugField(max_length=64, null=False, blank=False, unique=True, help_text='URL-friendly identifier for the badge page. Generated from the title when the badge is created, and kept fixed after that.')
description = models.TextField(null=True, blank=True, help_text='What did the people do who contributed here?')
url = models.URLField(max_length=100, null=True, blank=True, verbose_name='Contribution URL', help_text='URL for this contribution, e.g. the conference homepage. (Leave blank when there is no URL.)')
- imagedata = ImageBinaryField(max_length=1000000, resolution=(150, 150), auto_scale=True, blank=True, null=True, verbose_name="Image", 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.")+ imagedata = ImageBinaryField(max_length=1000000, resolution=(150, 150), auto_scale=True, blank=True, null=True, verbose_name="Image", help_text="Square image, will be auto-scaled to 150×150. JPEG or PNG, up to 1 MB. When left blank, the PostgreSQL logo will be used.")
contact = models.CharField(max_length=100, null=True, blank=True, verbose_name='Contact address', help_text='Contact address (email, URL, other) for people who want to be added as badge holder')
holders = models.ManyToManyField(User, through="Badgeholder", through_fields=("badge", "user"), blank=True)
diff --git a/templates/account/userprofileform.html b/templates/account/userprofileform.htmlindex bac04651..01fba575 100644--- a/templates/account/userprofileform.html+++ b/templates/account/userprofileform.html@@ -100,7 +100,7 @@
{%for b in badges %}
<figure>
<a href="/community/badge/{{b.slug}}/">
- <img src="{%if b.has_image %}/community/badge/{{b.slug}}/image/{%else%}/media/img/about/press/elephant.png{%endif%}">+ <img src="{%if b.has_image %}/community/badge/{{b.slug}}/image/{%else%}/media/img/about/press/elephant.png{%endif%}" alt="{{b}}">
<figcaption>{{b}}</figcaption>
</a>
</figure>
@@ -134,7 +134,7 @@
<h2>Create contributor profile</h2>
<p>You have been awarded contributor badges. To have your name included in the public people and badge holder lists, you can create a publicly visible profile page.</p>
<div>
- <input type="checkbox" name="create_contributor_profile"> Create publicly visible profile page+ <input type="checkbox" name="create_contributor_profile" id="create_contributor_profile"> <label for="create_contributor_profile">Create publicly visible profile page</label>
</div>
{% endif %}
diff --git a/templates/contributors/badge.html b/templates/contributors/badge.htmlindex 1da8f84b..7ea0f1fd 100644--- a/templates/contributors/badge.html+++ b/templates/contributors/badge.html@@ -3,7 +3,7 @@
{%block title%}{{badge}} - Contribution{%endblock%}
{%block contents%}
<h1>Badge: {{badge}} <i class="fa fa-star"></i></h1>
-<p><img src="{%if badge.has_image %}/community/badge/{{badge.slug}}/image/{%else%}/media/img/about/press/elephant.png{%endif%}" width="150"></p>+<p><img src="{%if badge.has_image %}/community/badge/{{badge.slug}}/image/{%else%}/media/img/about/press/elephant.png{%endif%}" width="150" alt="{{badge}}"></p>
{% if badge.description or badge.url %}
<h2>Contribution</h2>
@@ -19,12 +19,12 @@
<h2>Badge Holders</h2>
{%if holders|length > 50%}
{%for u in holders.all %}
- <nobr>{%if u.date_retired%}<em>{%endif%}<a href="/community/people/{{u.user}}/">{{u.user.contributor.firstname}} {{u.user.contributor.lastname}}</a>{%if u.date_retired%}</em>{%endif%} {%if not forloop.last%}·{%endif%}</nobr>+ <nobr{%if u.date_retired%} class="badgeholder-retired"{%endif%}><a href="/community/people/{{u.user}}/">{{u.user.contributor.firstname}} {{u.user.contributor.lastname}}</a> {%if not forloop.last%}·{%endif%}</nobr>
{%endfor%}
{%else%}
<ul>
{%for u in holders.all%}
- <li>{%if u.date_retired%}<em>{%endif%}<a href="/community/people/{{u.user}}/">{{u.user.contributor.firstname}} {{u.user.contributor.lastname}}</a>{%if u.date_retired%} (retired from this activity)</em>{%endif%}</li>+ <li{%if u.date_retired%} class="badgeholder-retired"{%endif%}><a href="/community/people/{{u.user}}/">{{u.user.contributor.firstname}} {{u.user.contributor.lastname}}</a>{%if u.date_retired%} (retired from this activity){%endif%}</li>
{%endfor%}
</ul>
{%endif%}
diff --git a/templates/contributors/people.html b/templates/contributors/people.htmlindex 67de9b9d..37211902 100644--- a/templates/contributors/people.html+++ b/templates/contributors/people.html@@ -26,7 +26,7 @@
{%for b in badges %}
<figure>
<a href="/community/badge/{{b.slug}}/">
- <img src="{%if b.has_image %}/community/badge/{{b.slug}}/image/{%else%}/media/img/about/press/elephant.png{%endif%}">+ <img src="{%if b.has_image %}/community/badge/{{b.slug}}/image/{%else%}/media/img/about/press/elephant.png{%endif%}" alt="{{b}}">
<figcaption>{{b}}</figcaption>
</a>
</figure>
diff --git a/templates/contributors/profile.html b/templates/contributors/profile.htmlindex f4d1afdc..e47bf455 100644--- a/templates/contributors/profile.html+++ b/templates/contributors/profile.html@@ -12,8 +12,8 @@
{%for b in badges %}
<figure>
<a href="/community/badge/{{b.badge.slug}}/">
- <img src="{%if b.badge.has_image %}/community/badge/{{b.badge.slug}}/image/{%else%}/media/img/about/press/elephant.png{%endif%}">- <figcaption>{{b.badge}}{%if b.date_retired%}<br><em>(retired)</em>{%endif%}</figcaption>+ <img src="{%if b.badge.has_image %}/community/badge/{{b.badge.slug}}/image/{%else%}/media/img/about/press/elephant.png{%endif%}" alt="{{b.badge}}">+ <figcaption{%if b.date_retired%} class="badgeholder-retired"{%endif%}>{{b.badge}}{%if b.date_retired%}<br>(retired){%endif%}</figcaption>
</a>
</figure>
{%endfor%}
--
2.53.0
v12-0001-Extend-badge-title-to-64-chars.patch (text/x-diff, 2.8K) download
From abd2ffaed0ecd2a3ec40b255c822d5c9da9dd286 Mon Sep 17 00:00:00 2001
From: Christoph Berg <myon@debian.org>
Date: Mon, 12 Oct 2026 14:17:58 +0200
Subject: [PATCH v12] Extend badge title to 64 chars
Daniel pointed out that a reasonable badge title like "Nordic PGDay 2026
Program Committee" is already longer than the 32 chars (it's 35) we
catered for. Extend it to 64 to match the max slug length.
---
.../migrations/0006_alter_badge_badge.py | 25 +++++++++++++++++++
pgweb/contributors/models.py | 2 +-
2 files changed, 26 insertions(+), 1 deletion(-)
create mode 100644 pgweb/contributors/migrations/0006_alter_badge_badge.py
diff --git a/pgweb/contributors/migrations/0006_alter_badge_badge.py b/pgweb/contributors/migrations/0006_alter_badge_badge.pynew file mode 100644index 00000000..3f709417--- /dev/null+++ b/pgweb/contributors/migrations/0006_alter_badge_badge.py@@ -0,0 +1,25 @@+# Generated by Django 5.2.17 on 2026-10-12 12:17++from django.db import migrations, models+++class Migration(migrations.Migration):++ dependencies = [+ (+ "contributors",+ "0005_alter_contributor_ctype_alter_contributor_email_and_more",+ ),+ ]++ operations = [+ migrations.AlterField(+ model_name="badge",+ name="badge",+ field=models.CharField(+ help_text='Title of this badge, e.g. "PGConf.EU 2025 Speaker".',+ max_length=64,+ unique=True,+ ),+ ),+ ]diff --git a/pgweb/contributors/models.py b/pgweb/contributors/models.pyindex 7ffc0881..58616da4 100644--- a/pgweb/contributors/models.py+++ b/pgweb/contributors/models.py@@ -98,7 +98,7 @@ class BadgeManager(models.Manager):
class Badge(TwostateModerateModel):
org = models.ForeignKey(Organisation, null=False, blank=False, verbose_name="Organisation", help_text=ORGANISATION_HINT_TEXT, on_delete=models.CASCADE)
- badge = models.CharField(max_length=32, null=False, blank=False, unique=True, help_text='Title of this badge, e.g. "PGConf.EU 2025 Speaker".')+ badge = models.CharField(max_length=64, null=False, blank=False, unique=True, help_text='Title of this badge, e.g. "PGConf.EU 2025 Speaker".')
slug = models.SlugField(max_length=64, null=False, blank=False, unique=True, help_text='URL-friendly identifier for the badge page. Generated from the title when the badge is created, and kept fixed after that.')
description = models.TextField(null=True, blank=True, help_text='What did the people do who contributed here?')
url = models.URLField(max_length=100, null=True, blank=True, verbose_name='Contribution URL', help_text='URL for this contribution, e.g. the conference homepage. (Leave blank when there is no URL.)')
--
2.53.0
v12-0001-Make-contributor-badges-discoverable.patch (text/x-diff, 5.2K) download
From db10a0cc66aa518f4e53139552819659e33b1d1f Mon Sep 17 00:00:00 2001
From: Christoph Berg <myon@debian.org>
Date: Fri, 25 Sep 2026 17:29:36 +0200
Subject: [PATCH v12 1/2] Make contributor badges discoverable
Add the People entry to the community menu and the Contributor Badges
entry to the account's submitted-data menu, and link the recognized
contributors list to the new people and profile pages. These are the
incoming links from existing pages; the badges system is fully
functional without them, so this can be pushed separately after testing.
Author: Melanie Plageman <melanieplageman@gmail.com>
Author: Christoph Berg <myon@debian.org>
---
pgweb/util/contexts.py | 2 ++
templates/contributors/list.html | 29 ++++++++++++++++-------------
2 files changed, 18 insertions(+), 13 deletions(-)
diff --git a/pgweb/util/contexts.py b/pgweb/util/contexts.pyindex ca493714..dc60740d 100644--- a/pgweb/util/contexts.py+++ b/pgweb/util/contexts.py@@ -47,6 +47,7 @@ sitenav = {
'community': [
{'title': 'Community', 'link': '/community/'},
{'title': 'Contributors', 'link': '/community/contributors/'},
+ {'title': 'People', 'link': '/community/people/'},
{'title': 'Mailing Lists', 'link': '/list/'},
{'title': 'IRC', 'link': '/community/irc/'},
# {'title': 'Slack', 'link': 'https://join.slack.com/t/postgresteam/shared_invite/zt-1qj14i9sj-E9WqIFlvcOiHsEk2yFEMjA'},
@@ -86,6 +87,7 @@ sitenav = {
{'title': 'Events', 'link': '/account/edit/events/'},
{'title': 'Products', 'link': '/account/edit/products/'},
{'title': 'Professional Services', 'link': '/account/edit/services/'},
+ {'title': 'Contributor Badges', 'link': '/account/edit/badges/'},
{'title': 'Organisations', 'link': '/account/edit/organisations/'},
]},
{'title': 'Change password', 'link': '/account/changepwd/'},
diff --git a/templates/contributors/list.html b/templates/contributors/list.htmlindex 068fc949..8377a8e7 100644--- a/templates/contributors/list.html+++ b/templates/contributors/list.html@@ -1,18 +1,18 @@
{%extends "base/page.html"%}
{%load pgfilters%}
-{%block title%}Contributor Profiles{%endblock%}+{%block title%}Recognized Contributors{%endblock%}
{%block contents%}
-<h1>PostgreSQL Contributor Profiles <i class="fa fa-users"></i></h1>--<p>These are the fine people that make PostgreSQL what it is today!</p>+<h1>PostgreSQL Recognized Contributors <i class="fa fa-users"></i></h1>
<p>
- For a list of all code contributions to a specific release, see the- <a href="/docs/release/">Release Notes</a> for released versions of PostgreSQL.+ These are the fine people who make PostgreSQL what it is today!+ Contributors listed here have provided a sustained stream of notable contributions in recent years.
</p>
+
<p>
- Existing contributors can update their information in their- <a href="/account/profile/">user profile</a>.+ A separate page lists all+ <a href="/community/people/">people who have made contributions to PostgreSQL</a>+ over the years.
</p>
{%for t in contributortypes%}
@@ -32,7 +32,7 @@
{%for c in t.contributor_set.all %}
{%if t.detailed%}
<tr>
- <td>{{c.firstname}} {{c.lastname}} {%if t.showemail and c.email%}({{c.email|hidemail}}){%endif%}+ <td>{% if c.user %}<a href="/community/people/{{c.user.username}}/">{{c.firstname}} {{c.lastname}}</a>{% else %}{{c.firstname}} {{c.lastname}}{% endif %} {%if t.showemail and c.email%}({{c.email|hidemail}}){%endif%}
{%if c.company %}
<br/>
{% if c.companyurl %}
@@ -41,21 +41,23 @@
{{c.company}}
{% endif %}
{% endif %}
- <br/>- {{c.location}}+ {%if c.location %}+ <br/>+ {{c.location}}+ {% endif %}
</td>
<td>{{c.contribution}}</td>
</tr>
{%else%}
{%if forloop.counter0|divisibleby:"2" %}
<tr>
- <td>{{c.firstname}} {{c.lastname}}{%if t.showemail and c.email%} ({{c.email|hidemail}}){%endif%}</td>+ <td>{% if c.user %}<a href="/community/people/{{c.user.username}}/">{{c.firstname}} {{c.lastname}}</a>{% else %}{{c.firstname}} {{c.lastname}}{% endif %}{%if t.showemail and c.email%} ({{c.email|hidemail}}){%endif%}</td>
{%if forloop.last%}
<td></td>
</tr>
{%endif%}
{%else%}
- <td>{{c.firstname}} {{c.lastname}}{%if t.showemail and c.email%} ({{c.email|hidemail}}){%endif%}</td>+ <td>{% if c.user %}<a href="/community/people/{{c.user.username}}/">{{c.firstname}} {{c.lastname}}</a>{% else %}{{c.firstname}} {{c.lastname}}{% endif %}{%if t.showemail and c.email%} ({{c.email|hidemail}}){%endif%}</td>
</tr>
{%endif%}
{%endif%}
@@ -65,6 +67,7 @@
{%endfor%}
<p>All contributors are listed in alphabetical order.
+ Existing contributors can update their information in their <a href="/account/profile/">user profile</a>.
To suggest additions or corrections to this list, please email the
<a href="/about/governance/contributors/">Contributors Committee</a> at
<a href="mailto:contributors@postgresql.org">contributors@postgresql.org</a>.
--
2.53.0
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-www@postgresql.org
Cc: myon@debian.org, daniel@yesql.se, magnus@hagander.net, x4mmm@yandex-team.ru, melanieplageman@gmail.com, contributors@lists.postgresql.org
Subject: Re: Introduce contributor badges
In-Reply-To: <aszgh1hJGT6bG7QU@msg.df7cb.de>
References: <aszgh1hJGT6bG7QU@msg.df7cb.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox