Re: [HACKERS] list of credits for release notes - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: [HACKERS] list of credits for release notes
Date
Msg-id 20171002181250.GH4628@tamriel.snowman.net
Whole thread Raw
In response to Re: [HACKERS] list of credits for release notes  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [HACKERS] list of credits for release notes
List pgsql-hackers
Bruce,

* Bruce Momjian (bruce@momjian.us) wrote:
> On Fri, Sep 29, 2017 at 12:00:05PM -0400, Peter Eisentraut wrote:
> > On 9/29/17 11:35, Robert Haas wrote:
> > > On Wed, Sep 27, 2017 at 8:29 PM, Michael Paquier
> > > <michael.paquier@gmail.com> wrote:
> > >> Looking at this list, the first name is followed by the family name,
> > >> so there are inconsistencies with some Japanese names:
> > >> - Fujii Masao should be Masao Fujii.
> > >> - KaiGai Kohei should be Kohei Kaigai.
> > >
> > > But his emails say Fujii Masao, not Masao Fujii.
> > >
> > > KaiGai's case is a bit trickier, as his email name has changed over time.
> >
> > Yes, I used the form that the person used in their emails.
>
> How should this be handled for the Postgres 11 release notes?

Ideally, we would let the individuals choose how to be recognized in
release notes, and anywhere else we recognize them.  We have the start
of that in https://postgresql.org/account/profile but that isn't very
easily tied to things in the commit history or elsewhere, yet.  I'd
suggest that we try to improve on that by:

- Allowing anyone to include contributor information in their .Org account, even if they aren't listed on the
Contributorspage. 

- Add in a field along the lines of "Name to be used publicly" and let them decide what they'd like, possibly even with
theoption to not be publicly listed at all. 

- Add tracking of multiple email addresses into the .Org profile (somehow sync'd with the pglister system)

- Start including contributor email addresses in commit messages along with names.

I don't think we're that far off from this being possible to do in a
more formal way that minimizes the risk of getting things incorrect,
missing someone, or mis-attributing something.  This all involves mostly
work on the .Org system, which we do have some folks working on now but
is also open source and it certainly wouldn't hurt to have more people
involved, if there are others who are interested.  The place to actually
start the discussion of such changes would be -www though.

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Andrew Borodin
Date:
Subject: Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Horrible CREATE DATABASE Performance in High Sierra