Re: Translators are not listed as contributors

On Thu, Sep 10, 2026, at 6:26 AM, Pavlo Golub wrote:
>
> What triggered me this time is the situation with the pt_BR language
> in particular. For those of you who are not aware, pt_BR could've not
> make it into the Postgres 19 release due to a low level of translated
> strings (<80%). On the Crowdin platform [1], we have an active
> community working hard on exactly this language. So I pushed all
> strings done by them, and now pt_BR qualifies with 85%. In practice,
> those nine translators saved the language from exclusion. But no one
> ever hears about them or about all other translators because we treat
> this as a non-important non-committer job.
>

That's a nobel idea but you should have coordinated this action with the
current pt_BR maintainer. :( I'm about to finish the translation for v19
(6 remaining files). And now I need to spend several hours to merge each
file.

I wasn't aware that we have a approved platform for translations. Did I
miss the discussion?

> I'm sure that all translators who participated in release translations
> must be listed as contributors to the release. It's not fair to ignore
> all the people and efforts they committed. This is especially true for
> people outside of our community, who contributed just because they
> love open-source and are committed to it.
>

+1. It seems we need an automated way to collect all translators from
the commit log. The translators for each language is generally a single
person or a small group (2 or 3 people). If we want to adopt your
proposal, all committers from pgtranslation repository needs to add the
Author into each commit message. And then, a command like the above
can provide the list of translators.

git log 0f717a85af6..bb57de57057 | grep 'Author:' | sort | uniq

Are you suggesting for both major and minor releases? If we adopt it, I
would say yes for both cases.

--
Euler Taveira
EDB https://www.enterprisedb.com/