someone else to do the list of acknowledgments

I would like for someone else to prepare the list of acknowledgments in
the release notes this year.

I have been preparing the list of acknowledgments in the release notes
(example: [0]) since PostgreSQL 10 (launched from discussions at PGCon
2017 [1]).  I'm looking to hand this off now, so that I'm not hogging
this job forever.

[0]: 
https://www.postgresql.org/docs/17/release-17.html#RELEASE-17-ACKNOWLEDGEMENTS
[1]: 
https://wiki.postgresql.org/wiki/PgCon_2017_Developer_Meeting#Release_notes_scope.2C_and_giving_credit

I'm happy to train the next person and hand them my tips and scripts,
or they can of course define their own processes.

So that prospective candidates know what they are getting into, the
(my) process is approximately:

1. collect names from git logs in semi-automated way
2. sort, organize, fix, and normalize names
3. check manually against git log
4. commit
5. fix up based on public feedback
6. keep updated until release

The whole thing might take about 20 to 30 hours wall-clock time.

I have found it not useful to start this too early, since you'll get a
lot of new names during the beta period.  I have lately usually
started after the August beta release.  (Or you can start early and
keep it updated.  Again, it's your process.)

Anyone can do this, you don't need to be a committer or developer (but
you'll need to be able to produce a well-formed documentation patch).
However, I suggest that because there is a fair amount of work to
normalize, fix, and transliterate names, it would help if you've been
around for a while and have some passing familiarity with the names of
the people around here.  Also, since this list is often cited for
public credit, some care and attention to detail is needed.

So, there is some time to think about this.  Please discuss here if
you're interested or have questions.

(This is presupposing that we still want to do this.  If you have
other ideas for a better list or no list, this is also the time to
discuss this.)