pg.ddx.io pgsql-translators@postgresql.org mailing list archive
help / color / mirror / Atom feedTranslators are not listed as contributors
6+ messages / 5 participants
[nested] [flat]
* Translators are not listed as contributors
@ 2026-09-10 09:26 Pavlo Golub <pavlo.golub@gmail.com>
0 siblings, 4 replies; 6+ messages in thread
From: Pavlo Golub @ 2026-09-10 09:26 UTC (permalink / raw)
To: pgsql-translators@lists.postgresql.org
Hello.
Right now, Peter pushes all new changes from the pgtranslation repo to
the main one. And I'm in no way accusing Peter of anything. He is
already doing a lot by handling all this stuff. The commit message
looks like:
------
Translation updates
Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: fcf4cea0a0730cdd7f5da35160ab1c745212768f
------
If we check other commit messages to the main repo, for example just
the latest I see:
------
postgres_fdw: Adjust warning message in statistics import.
The previous warning message when falling back to sampling in a certain
case failed to properly mention the reason for that.
Also, for clarity, rewrite a comment about the fallback and add a note
about it to postgres-fdw.sgml.
Follow-up to commit 6a85715.
Reported-by: Fujii Masao masao.fujii@gmail.com
Author: Etsuro Fujita etsuro.fujita@gmail.com
Reviewed-by: Corey Huinker corey.huinker@gmail.com
Discussion: https://postgr.es/m/CAHGQGwHq1VuXwxeDU8N4dd9U4RFEW982qQ9C26mRQDs3nu_Naw%40mail.gmail.com
Backpatch-through: 19
------
The difference here disturbs me. I noticed the situation a long time
ago but had never started a discussion.
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.
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.
Something like this would be cool:
------
Translation updates
Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git
Source-Git-Hash: fcf4cea0a0730cdd7f5da35160ab1c745212768f
Translators: John Johnson john@john.son, Will Smith, ....
------
This also forces people to list translators in pgtranslation repo commits.
1: https://crowdin.com/project/postgresql/
--
Hoc est vivere bis, vita posse priore frui.
Nullus est in vitae sensus, ipsa vera est sensus.
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Translators are not listed as contributors
@ 2026-09-10 11:53 Guillaume Lelarge <guillaume.lelarge@dalibo.com>
parent: Pavlo Golub <pavlo.golub@gmail.com>
3 siblings, 0 replies; 6+ messages in thread
From: Guillaume Lelarge @ 2026-09-10 11:53 UTC (permalink / raw)
To: pgsql-translators@lists.postgresql.org
Hi,
On 10/09/2026 11:26, Pavlo Golub wrote:
> [...]
> 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.
>
> Something like this would be cool:
> ------
> Translation updates
> Source-Git-URL: https://git.postgresql.org/git/pgtranslation/messages.git
> Source-Git-Hash: fcf4cea0a0730cdd7f5da35160ab1c745212768f
>
> Translators: John Johnson john@john.son, Will Smith, ....
> ------
>
FWIW, I totally agree. It would be nice to have that.
Regards.
--
Guillaume Lelarge
Consultant
https://dalibo.com
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Translators are not listed as contributors
@ 2026-09-10 12:04 Daniel Gustafsson <daniel@yesql.se>
parent: Pavlo Golub <pavlo.golub@gmail.com>
3 siblings, 0 replies; 6+ messages in thread
From: Daniel Gustafsson @ 2026-09-10 12:04 UTC (permalink / raw)
To: Pavlo Golub <pavlo.golub@gmail.com>; +Cc: pgsql-translators@lists.postgresql.org
> On 10 Sep 2026, at 11:26, Pavlo Golub <pavlo.golub@gmail.com> wrote:
> 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.
I could not agree more. When doing the research for Claire's contribution talk
at PGConf.EU I remember it being somewhat tricky to figure out exactly whom had
been involved for the current release (one person submitting on behalf of a
group effort etc). Is the group of people who contribute to a specific release
tracked somewhere in Redmine or elsewhere?
--
Daniel Gustafsson
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Translators are not listed as contributors
@ 2026-09-10 17:44 Euler Taveira <euler@eulerto.com>
parent: Pavlo Golub <pavlo.golub@gmail.com>
3 siblings, 1 reply; 6+ messages in thread
From: Euler Taveira @ 2026-09-10 17:44 UTC (permalink / raw)
To: Pavlo Golub <pavlo.golub@gmail.com>; pgsql-translators@lists.postgresql.org
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/
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Translators are not listed as contributors
@ 2026-09-10 18:05 Pavlo Golub <pavlo.golub@gmail.com>
parent: Euler Taveira <euler@eulerto.com>
0 siblings, 0 replies; 6+ messages in thread
From: Pavlo Golub @ 2026-09-10 18:05 UTC (permalink / raw)
To: Euler Taveira <euler@eulerto.com>; +Cc: pgsql-translators@lists.postgresql.org
>
>
>
> 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.
>
Oh, please, accept my sincere apologies! I'd blame the workflow we have. Do
we even have approved maintainers for languages? I acted in a full believe
we don't. The same like we don't have maintainers for parts of the postgres
code base itself. So any committer is doing their best to keep the code in
the best shape. Again, please accept my apologies!
> I wasn't aware that we have a approved platform for translations. Did I
> miss the discussion?
>
No, we don't have any approved platforms even though we had a lot of
discussions. I'd not call Redmine a platform, I'm not sure if it's still
alive.
> > 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
>
+1
>
> Are you suggesting for both major and minor releases? If we adopt it, I
> would say yes for both cases.
>
I'd say both since translators come and go in the middle of the year
>
>
> --
> Euler Taveira
> EDB https://www.enterprisedb.com/
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Translators are not listed as contributors
@ 2026-09-15 08:21 Peter Eisentraut <peter@eisentraut.org>
parent: Pavlo Golub <pavlo.golub@gmail.com>
3 siblings, 0 replies; 6+ messages in thread
From: Peter Eisentraut @ 2026-09-15 08:21 UTC (permalink / raw)
To: Pavlo Golub <pavlo.golub@gmail.com>; pgsql-translators@lists.postgresql.org
On 10.09.26 11:26, Pavlo Golub wrote:
> 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.
>
> Something like this would be cool:
> ------
> Translation updates
> Source-Git-URL:https://git.postgresql.org/git/pgtranslation/messages.git
> Source-Git-Hash: fcf4cea0a0730cdd7f5da35160ab1c745212768f
>
> Translators: John Johnsonjohn@john.son, Will Smith, ....
> ------
>
> This also forces people to list translators in pgtranslation repo commits.
I suggest for the imminent PostgreSQL 19, someone collect these names
manually and send them over to pgsql-hackers for inclusion into the
release notes.
For PostgreSQL 20, we can think of a more automated process. I think we
could extract the names from the pgtranslators commit log and add them
into the postgresql commit message similar to what you suggest. But one
immediate challenge is that this would require collecting the names from
the commit log since the last time the translations were synced, which
would require additional bookkeeping somewhere. Alternatively, we ask
the person who prepares the release notes credits to scan the
pgtranslation commit log directly. (Alternatively alternatively,
someone from this mailing list does that and merges it into the existing
list, which is sort of what I suggested above.)
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2026-09-15 08:21 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-09-10 09:26 Translators are not listed as contributors Pavlo Golub <pavlo.golub@gmail.com>
2026-09-10 11:53 ` Guillaume Lelarge <guillaume.lelarge@dalibo.com>
2026-09-10 12:04 ` Daniel Gustafsson <daniel@yesql.se>
2026-09-10 17:44 ` Euler Taveira <euler@eulerto.com>
2026-09-10 18:05 ` Pavlo Golub <pavlo.golub@gmail.com>
2026-09-15 08:21 ` Peter Eisentraut <peter@eisentraut.org>
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