From PostgreSQL wiki
Jump to navigationJump to search

This is the current list of people with access to push to the git repository with their user names. For technical details on how committing works, see Committing with Git. Note: This is just a list of people who currently have access to push to git; for information on current and previous contributors, see the contributor profiles section of the web site. Note: The names are listed here in order of first commit or when added as a committer, oldest first; this isn't intended to imply anything about depth of contribution.

  • Bruce Momjian (momjian)
  • Tom Lane (tgl)
  • Michael Meskes (meskes)
  • Tatsuo Ishii (ishii)
  • Peter Eisentraut (petere)
  • Joe Conway (joe)
  • Alvaro Herrera (alvherre)
  • Andrew Dunstan (adunstan)
  • Magnus Hagander (mha)
  • Heikki Linnakangas (heikki)
  • Robert Haas (rhaas)
  • Jeff Davis (jdavis)
  • Stephen Frost (sfrost)
  • Fujii Masao (fujii)
  • Noah Misch (noah)
  • Andres Freund (andres)
  • Dean Rasheed (deanr)
  • Andrew Gierth (rhodiumtoad)
  • Alexander Korotkov (smagen)
  • Amit Kapila (amitkapila)
  • Tomas Vondra (fuzzycz)
  • Michael Paquier (michael-kun)
  • Thomas Munro (macdice)
  • Peter Geoghegan (pgeoghegan)
  • Etsuro Fujita (efujita)
  • David Rowley (drowley)
  • Daniel Gustafsson (d_gustafsson)
  • John Naylor (john.naylor)
  • Nathan Bossart (nbossart)
  • Amit Langote (amitlan)
  • Masahiko Sawada (msawada)

Notes on the Commit Log

Hundreds of developers have successfully contributed work to PostgreSQL over more than 20 years, many acting as individuals, though also many representing academic institutions and both user and vendor companies. Both the "Author" and "Committer" fields of such patches will reflect the committer. The actual author of a patch, if different, is generally listed in the commit message; reviewers or others who contributed ideas or otherwise helped with the patch may also be listed. Many patches, in the form in which they are committed, are the work of multiple people: original author or authors, reviewer(s), and/or committer. As a result, no simple analysis of duration or depth of contribution over time is possible from the commit log. The project operates a system of careful peer review and even committers have their work checked by other committers and the community as a whole.

New Committers and Removing Committers

New committers are added approximately annually by the Core Team. Contributors to PostgreSQL are selected to be committers based on the following loose criteria:

  • several years of substantial contributions to the project
  • multiple and continuing code contributions
  • responsibility for maintenance of one or more areas of the codebase
  • track record of reviewing and helping other contributors with their patches
  • high quality code contributions which require very little revision or correction for commit
  • demonstrated understanding of the process and criteria for patch acceptance

Generally, new committers are selected March or April and announced at pgCon.

Committers who have become inactive and have not contributed significantly to the PostgreSQL project in several years are removed as committers. Again, the review process for this is approximately annual.