Details on new maintainership

AUTHORS.md

@@ -4,16 +4,18 @@ PCRE2 Authorship and Contributors
 COPYRIGHT
 ---------
 
-Please see the file [LICENCE](./LICENCE.md) in the PCRE2 distribution for copyright details.
+Please see the file [LICENCE](./LICENCE.md) in the PCRE2 distribution for
+copyright details.
 
 
 MAINTAINERS
 -----------
 
 The PCRE and PCRE2 libraries were authored and maintained by Philip Hazel.
 
-Since 2024, the contributors with administrator access to the project are now Nicholas Wilson and Zoltán
-Herczeg. See the file [SECURITY](./SECURITY.md) for GPG keys.
+Since 2024, the contributors with administrator access to the project are now
+Nicholas Wilson and Zoltán Herczeg. See the file [SECURITY](./SECURITY.md) for
+GPG keys.
 
 Both administrators are volunteers acting in a personal capacity.
 
@@ -65,12 +67,134 @@ CONTRIBUTORS
 
 Many others have participated and contributed to PCRE2 over its history.
 
-An incomplete list of recent contributors (alphabetical):
+The maintainers are grateful for all contributions and participation over the
+years. We apologise for any names we have forgotten.
 
-    Addison Crump
-    Alex Dowad
-    Carlo Marcelo Arenas Belón
+We are especially grateful to Philip Hazel, creator of PCRE and PCRE2, and
+maintainer from 1997 to 2024.
+
+All names listed alphabetically.
 
-You may browse Git's history for further details of many past contributors.
+### Contributors to PCRE2
 
-The maintainers are grateful for all contributions and participation over the years, whether or not listed here in this recent summary.
+This list is includes names up until the PCRE2 10.44 release. New names will be
+added from the Git history on each release.
+
+    Scott Bell
+    Carlo Marcelo Arenas Belón
+    Edward Betts
+    Jan-Willem Blokland
+    Ross Burton
+    Dmitry Cherniachenko
+    Alexey Chupahin
+    Jessica Clarke
+    Alejandro Colomar
+    Jeremie Courreges-Anglas
+    Addison Crump
+    Alex Dowad
+    Daniel Engberg
+    Daniel Richard G
+    David Gaussmann
+    Andrey Gorbachev
+    Jordan Griege
+    Jason Hood
+    Bumsu Hyeon
+    Roy Ivy
+    Martin Joerg
+    Guillem Jover
+    Ralf Junker
+    Ayesh Karunaratne
+    Michael Kaufmann
+    Yunho Kim
+    Joshua Kinard
+    David Korczynski
+    Uwe Korn
+    Jonas Kvinge
+    Kristian Larsson
+    Kai Lu
+    Behzod Mansurov
+    B. Scott Michel
+    Nathan Moinvaziri
+    Mike Munday
+    Marc Mutz
+    Fabio Pagani
+    Christian Persch
+    Tristan Ross
+    William A Rowe Jr
+    David Seifert
+    Yaakov Selkowitz
+    Rich Siegel
+    Karl Skomski
+    Maciej Sroczyński
+    Wolfgang Stöggl
+    Thomas Tempelmann
+    Greg Thain
+    Lucas Trzesniewski
+    Theodore Tsirpanis
+    Matthew Vernon
+    Rémi Verschelde
+    Thomas Voss
+    Ezekiel Warren
+    Carl Weaver
+    Chris Wilson
+    Amin Yahyaabadi
+    Joe Zhang
+
+### Contributors to PCRE1
+
+These people contributed either by sending patches or reporting serious issues.
+
+    Irfan Adilovic
+    Alexander Barkov
+    Daniel Bergström
+    David Burgess
+    Ross Burton
+    David Byron
+    Fred Cox
+    Christian Ehrlicher
+    Tom Fortmann
+    Lionel Fourquaux
+    Mike Frysinger
+    Daniel Richard G
+    Dair Gran
+    "Graycode" (Red Hat Product Security)
+    Viktor Griph
+    Wen Guanxing
+    Robin Houston
+    Martin Jerabek
+    Peter Kankowski
+    Stephen Kelly
+    Yunho Kim
+    Joshua Kinard
+    Carsten Klein
+    Evgeny Kotkov
+    Ronald Landheer-Cieslak
+    Alan Lehotsky
+    Dmitry V. Levin
+    Nuno Lopes
+    Kai Lu
+    Giuseppe Maxia
+    Dan Mooney
+    Marc Mutz
+    Markus Oberhumer
+    Sheri Pierce
+    Petr Pisar
+    Ari Pollak
+    Bob Rossi
+    Ruiger Rill
+    Michael Shigorin
+    Rich Siegel
+    Craig Silverstein (C++ wrapper)
+    Karl Skomski
+    Paul Sokolovsky
+    Stan Switzer
+    Ian Taylor
+    Mark Tetrode
+    Jeff Trawick
+    Steven Van Ingelgem
+    Lawrence Velazquez
+    Jiong Wang
+    Stefan Weber
+    Chris Wilson
+
+Thanks go to Jeffrey Friedl for testing and debugging assistance.

SECURITY.md

@@ -4,25 +4,41 @@
 
 The PCRE2 project provides source-only releases, with no binaries.
 
-These source releases can be downloaded from the [GitHub Releases](https://github.com/PCRE2Project/pcre2/releases) page. Each release file is GPG-signed.
+These source releases can be downloaded from the
+[GitHub Releases](https://github.com/PCRE2Project/pcre2/releases) page. Each
+release file is GPG-signed.
 
-* Releases up to and including 10.44 are signed by Philip Hazel (GPG key: <kbd>45F68D54BBE23FB3039B46E59766E084FB0F43D8</kbd>)
-* Releases from 10.45 onwards will be signed by Nicholas Wilson (GPG key: <kbd>A95536204A3BB489715231282A98E77EB6F24CA8</kbd>, cross-signed by Philip Hazel's key for release continuity)
+* Releases up to and including 10.44 are signed by Philip Hazel (GPG key:
+  <kbd>45F68D54BBE23FB3039B46E59766E084FB0F43D8</kbd>)
+* Releases from 10.45 onwards will be signed by Nicholas Wilson (GPG key:
+  <kbd>A95536204A3BB489715231282A98E77EB6F24CA8</kbd>, cross-signed by Philip
+  Hazel's key for release continuity)
 
-From releases 10.45 onwards, the source code will additionally be provided via Git checkout of the (GPG-signed) release tag.
+From releases 10.45 onwards, the source code will additionally be provided via
+Git checkout of the (GPG-signed) release tag.
 
-Please contact the maintainers for any queries about release integrity or the project's supply-chain.
+Please contact the maintainers for any queries about release integrity or the
+project's supply-chain.
 
 ## Reporting vulnerabilities
 
-The PCRE2 project prioritises security. We appreciate third-party testing and security research, and would be grateful if you could responsibly disclose your findings to us. We will make every effort to acknowledge your contributions.
+The PCRE2 project prioritises security. We appreciate third-party testing and
+security research, and would be grateful if you could responsibly disclose your
+findings to us. We will make every effort to acknowledge your contributions.
 
-To report a security issue, please use the GitHub Security Advisory ["Report a Vulnerability"](https://github.com/PCRE2Project/pcre2/security/advisories/new) tab. (Alternatively, if you prefer you may send a GPG-encrypted email to one of the maintainers.)
+To report a security issue, please use the GitHub Security Advisory
+["Report a Vulnerability"](https://github.com/PCRE2Project/pcre2/security/advisories/new)
+tab. (Alternatively, if you prefer you may send a GPG-encrypted email to one of
+the maintainers.)
 
 ### Timeline
 
-As a very small volunteer team, we cannot guarantee rapid response, but would aim to respond within 1 week, or perhaps 2 during holidays.
+As a very small volunteer team, we cannot guarantee rapid response, but would
+aim to respond within 1 week, or perhaps 2 during holidays.
 
 ### Response procedure
 
-PCRE2 has never previously made a rapid or embargoed release in response to a security incident. We would work with security managers from trusted downstream distributors, such as major Linux distributions, before disclosing the vulnerability publicly.
+PCRE2 has never previously made a rapid or embargoed release in response to a
+security incident. We would work with security managers from trusted downstream
+distributors, such as major Linux distributions, before disclosing the
+vulnerability publicly.