public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dennis Björklund <[email protected]>
To: Pavlo Golub <[email protected]>
To: Peter Eisentraut <[email protected]>
To: [email protected]
Subject: Re: No credit for translators?
Date: Sat, 11 Mar 2023 08:14:02 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

Sounds like a workable way to keep track of the persons involved in a 
release.

Just parsing the commit logs of the translation repo would give some 
names but maybe not all. On the other hand the current list in the 
release notes is probably produced by parsing the PG commits and those 
can also be from a group of persons represented by a single individual.

I don't know how testers are included in the current list and where that 
data come from.

/Dennis

Den 2023-03-10 kl. 10:40, skrev Pavlo Golub:
>> On 09.03.23 23:17, Dennis Björklund wrote:
>>> In the end of each Release notes there is this section:
>>>
>>> "The following individuals (in alphabetical order) have contributed 
>>> to this release as patch authors, committers, reviewers, testers, or 
>>> reporters of issues."
>>>
>>> It would be nice for translators to be included in the list of names 
>>> as well. It's quite a lot of work to do a translation after all.
>>
>> This is of course true.
>>
>> The release notes credits are basically composed from the commit logs.
>>
>> If we want to add translators as well, we need to come up with a 
>> reliable way to collect everybody's names, including from mailing 
>> lists, direct commits, bug tracker, as well as names of people who 
>> have helped behind the scenes but are "represented" here by a single 
>> individual.
>>
>> Now is a good time to start thinking about this.
>>
> I think we already de-facto have people responsible for a language(s). I 
> believe they should know all other persons involved. For example, I can 
> easily give you a list of translators to Ukrainian.
> 
> After we collect those lists, maybe, it's a good idea to put those under 
> version control for a current DEV branch. After official release, wipe 
> it out and start from the scratch.
> 
> 

view thread (4+ 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]
  Subject: Re: No credit for translators?
  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