[binutils.git] / gdb / MAINTAINERS

		GDB Maintainers
		===============


		   Overview
		   --------

This file describes different groups of people who are, together, the
maintainers and developers of the GDB project.  Don't worry - it sounds
more complicated than it really is.

There are four groups of GDB developers, covering the patch development and
review process:

  - The Global Maintainers.

    These are the developers in charge of most daily development.  They
    have wide authority to apply and reject patches, but defer to the
    Responsible Maintainers (see below) within their spheres of
    responsibility.

  - The Responsible Maintainers.

    These are developers who have expertise and interest in a particular
    area of GDB, who are generally available to review patches, and who
    prefer to enforce a single vision within their areas.

  - The Authorized Committers.

    These are developers who are trusted to make changes within a specific
    area of GDB without additional oversight.

  - The Write After Approval Maintainers.

    These are developers who have write access to the GDB source tree.  They
    can check in their own changes once a developer with the appropriate
    authority has approved the changes; they can also apply the Obvious
    Fix Rule (below).

All maintainers are encouraged to post major patches to the gdb-patches
mailing list for comments, even if they have the authority to commit the
patch without review from another maintainer.  This especially includes
patches which change internal interfaces (e.g. global functions, data
structures) or external interfaces (e.g. user, remote, MI, et cetera).

The term "review" is used in this file to describe several kinds of feedback
from a maintainer: approval, rejection, and requests for changes or
clarification with the intention of approving a revised version.  Review is
a privilege and/or responsibility of various positions among the GDB
Maintainers.  Of course, anyone - whether they hold a position but not the
relevant one for a particular patch, or are just following along on the
mailing lists for fun, or anything in between - may suggest changes or
ask questions about a patch!

There's also a couple of other people who play special roles in the GDB
community, separately from the patch process:

  - The GDB Steering Committee.

    These are the official (FSF-appointed) maintainers of GDB.  They have
    final and overriding authority for all GDB-related decisions, including
    anything described in this file.  The committee is not generally
    involved in day-to-day development (although its members may be, as
    individuals).

  - The Release Manager.

    This developer is in charge of making new releases of GDB.

  - The Patch Champions.

    These volunteers make sure that no contribution is overlooked or
    forgotten.

Most changes to the list of maintainers in this file are handled by
consensus among the global maintainers and any other involved parties.
In cases where consensus can not be reached, the global maintainers may
ask the Steering Committee for a final decision.


			The Obvious Fix Rule
			--------------------

All maintainers listed in this file, including the Write After Approval
developers, are allowed to check in obvious fixes.

An "obvious fix" means that there is no possibility that anyone will
disagree with the change.

A good mental test is "will the person who hates my work the most be
able to find fault with the change" - if so, then it's not obvious and
needs to be posted first. :-)

Something like changing or bypassing an interface is _not_ an obvious
fix, since such a change without discussion will result in
instantaneous and loud complaints.

For documentation changes, about the only kind of fix that is obvious
is correction of a typo or bad English usage.


	     GDB Steering Committee
	     ----------------------

The members of the GDB Steering Committee are the FSF-appointed
maintainers of the GDB project.

The Steering Committee has final authority for all GDB-related topics;
they may make whatever changes that they deem necessary, or that the FSF
requests.  However, they are generally not involved in day-to-day
development.

The current members of the steering committee are listed below, in
alphabetical order.  Their affiliations are provided for reference only -
their membership on the Steering Committee is individual and not through
their affiliation, and they act on behalf of the GNU project.

	Jim Blandy (CodeSourcery)
	Andrew Cagney (Red Hat)
	Robert Dewar (AdaCore, NYU)
	Klee Dienes (Apple)
	Paul Hilfinger (UC Berkeley)
	Dan Jacobowitz (CodeSourcery)
	Stan Shebs (Mozilla)
	Richard Stallman (FSF)
	Ian Lance Taylor (C2)
	Todd Whitesel


		  Global Maintainers
		  ------------------

The global maintainers may review and commit any change to GDB, except in
areas with a Responsible Maintainer available.  For major changes, or
changes to areas with other active developers, global maintainers are
strongly encouraged to post their own patches for feedback before
committing.

The global maintainers are responsible for reviewing patches to any area
for which no Responsible Maintainer is listed.

Global maintainers also have the authority to revert patches which should
not have been applied, e.g. patches which were not approved, controversial
patches committed under the Obvious Fix Rule, patches with important bugs
that can't be immediately fixed, or patches which go against an accepted and
documented roadmap for GDB development.  Any global maintainer may request
the reversion of a patch.  If no global maintainer, or responsible
maintainer in the affected areas, supports the patch (except for the
maintainer who originally committed it), then after 48 hours the maintainer
who called for the reversion may revert the patch.

No one may reapply a reverted patch without the agreement of the maintainer
who reverted it, or bringing the issue to the GDB Steering Committee for
discussion.

At the moment there are no documented roadmaps for GDB development; in the
future, if there are, a reference to the list will be included here.

The current global maintainers are (in alphabetical order):

Jim Blandy			[email protected]
Kevin Buettner			[email protected]
Andrew Cagney			[email protected]
Fred Fish			[email protected]
Daniel Jacobowitz		[email protected]
Mark Kettenis           	[email protected]
Stan Shebs			[email protected]
Michael Snyder			[email protected]
Ulrich Weigand			[email protected]
Elena Zannoni			[email protected]
Eli Zaretskii			[email protected]


			Release Manager
			---------------

The current release manager is: Joel Brobecker  <[email protected]>

His responsibilities are:

    * organizing, scheduling, and managing releases of GDB.

    * deciding the approval and commit policies for release branches,
      and can change them as needed.


			Patch Champions
			---------------

These volunteers track all patches submitted to the gdb-patches list.  They
endeavor to prevent any posted patch from being overlooked; work with
contributors to meet GDB's coding style and general requirements, along with
FSF copyright assignments; remind (ping) responsible maintainers to review
patches; and ensure that contributors are given credit.

Current patch champions (in alphabetical order):

	Randolph Chung     <[email protected]>
	Daniel Jacobowitz  <[email protected]>


			Responsible Maintainers
			-----------------------

These developers have agreed to review patches in specific areas of GDB, in
which they have knowledge and experience.  These areas are generally broad;
the role of a responsible maintainer is to provide coherent and cohesive
structure within their area of GDB, to assure that patches from many
different contributors all work together for the best results.

Global maintainers will defer to responsible maintainers within their areas,
as long as the responsible maintainer is active.  Active means that
responsible maintainers agree to review submitted patches in their area
promptly; patches and followups should generally be answered within a week.
If a responsible maintainer is interested in reviewing a patch but will not
have time within a week of posting, the maintainer should send an
acknowledgement of the patch to the gdb-patches mailing list, and
plan to follow up with a review within a month.  These deadlines are for
initial responses to a patch - if the maintainer has suggestions
or questions, it may take an extended discussion before the patch
is ready to commit.  There are no written requirements for discussion,
but maintainers are asked to be responsive.

If a responsible maintainer misses these deadlines occasionally (e.g.
vacation or unexpected workload), it's not a disaster - any global
maintainer may step in to review the patch.  But sometimes life intervenes
more permanently, and a maintainer may no longer have time for these duties.
When this happens, he or she should step down (either into the Authorized
Committers section if still interested in the area, or simply removed from
the list of Responsible Maintainers if not).

If a responsible maintainer is unresponsive for an extended period of time
without stepping down, please contact the Global Maintainers; they will try
to contact the maintainer directly and fix the problem - potentially by
removing that maintainer from their listed position.

If there are several maintainers for a given domain then any one of them
may review a submitted patch.

Target Instruction Set Architectures:

The *-tdep.c files.  ISA (Instruction Set Architecture) and OS-ABI
(Operating System / Application Binary Interface) issues including CPU
variants.

The Target/Architecture maintainer works with the host maintainer when
resolving build issues.  The Target/Architecture maintainer works with
the native maintainer when resolving ABI issues.

	alpha		--target=alpha-elf ,-Werror

	arm		--target=arm-elf ,-Werror
			Richard Earnshaw	[email protected]

	avr		--target=avr ,-Werror

	cris		--target=cris-elf ,-Werror ,
			(sim does not build with -Werror)

	frv		--target=frv-elf ,-Werror

	h8300		--target=h8300-elf ,-Werror

	i386		--target=i386-elf ,-Werror
			Mark Kettenis           [email protected]

	ia64		--target=ia64-linux-gnu ,-Werror
			(--target=ia64-elf broken)

	m32c		--target=m32c-elf ,-Werror
			Jim Blandy, [email protected]

	m32r		--target=m32r-elf ,-Werror

	m68hc11		--target=m68hc11-elf ,-Werror ,
			Stephane Carrez		[email protected]

	m68k		--target=m68k-elf ,-Werror

	m88k		--target=m88k-openbsd ,-Werror
			Mark Kettenis		[email protected]

	mcore		Deleted

	mep		--target=mep-elf ,-Werror
			Kevin Buettner		[email protected]

	mips		--target=mips-elf ,-Werror

	mn10300		--target=mn10300-elf broken
			(sim/ dies with make -j)
			Michael Snyder		[email protected]

	ms1		--target=ms1-elf ,-Werror
			Kevin Buettner		[email protected]

	ns32k		Deleted

	pa		--target=hppa-elf ,-Werror

	powerpc		--target=powerpc-eabi ,-Werror

	s390		--target=s390-linux-gnu ,-Werror

	score	--target=score-elf
			Qinwei		[email protected]

	sh		--target=sh-elf ,-Werror
			--target=sh64-elf ,-Werror

	sparc		--target=sparc64-solaris2.10 ,-Werror
			(--target=sparc-elf broken)

	spu		--target=spu-elf ,-Werror
			Ulrich Weigand		[email protected]

	v850		--target=v850-elf ,-Werror

	vax		--target=vax-netbsd ,-Werror

	x86-64		--target=x86_64-linux-gnu ,-Werror

	xstormy16	--target=xstormy16-elf
			Corinna Vinschen	[email protected]

	xtensa		--target=xtensa-elf
			Maxim Grigoriev		[email protected]

All developers recognized by this file can make arbitrary changes to
OBSOLETE targets.

The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
above targets.


Host/Native:

The Native maintainer is responsible for target specific native
support - typically shared libraries and quirks to procfs/ptrace/...
The Native maintainer works with the Arch and Core maintainers when
resolving more generic problems.

The host maintainer ensures that gdb can be built as a cross debugger on
their platform.

AIX			Joel Brobecker		[email protected]

djgpp native		Eli Zaretskii		[email protected]
GNU Hurd		Alfred M. Szmidt	[email protected]
MS Windows (NT, '00, 9x, Me, XP) host & native
			Chris Faylor		[email protected]
GNU/Linux/x86 native & host
			Mark Kettenis		[email protected]
GNU/Linux MIPS native & host
			Daniel Jacobowitz	[email protected]
GNU/Linux m68k		Andreas Schwab		[email protected]
FreeBSD native & host	Mark Kettenis		[email protected]


Core: Generic components used by all of GDB

tracing			Michael Snyder		[email protected]
threads			Michael Snyder		[email protected]
			Mark Kettenis		[email protected]
language support
  C++			Daniel Jacobowitz	[email protected]
  Objective C support   Adam Fedor		[email protected]
shared libs		Kevin Buettner		[email protected]

documentation		Eli Zaretskii		[email protected]
  (including NEWS)
testsuite
  gdbtk (gdb.gdbtk)     Keith Seitz             [email protected]
  threads (gdb.threads) Michael Snyder          [email protected]
  trace (gdb.trace)     Michael Snyder          [email protected]


UI: External (user) interfaces.

gdbtk (c & tcl)		Fernando Nasser         [email protected]
			Keith Seitz		[email protected]
libgui (w/foundry, sn)	Keith Seitz		[email protected]


Misc:

gdb/gdbserver		Daniel Jacobowitz	[email protected]

Makefile.in, configure*	ALL

mmalloc/		ALL Host maintainers

sim/			See sim/MAINTAINERS

readline/		Master version: ftp://ftp.cwru.edu/pub/bash/
			ALL
			Host maintainers (host dependant parts)
			(but get your changes into the master version)

tcl/ tk/ itcl/		ALL


		Authorized Committers
		---------------------

These are developers working on particular areas of GDB, who are trusted to
commit their own (or other developers') patches in those areas without
further review from a Global Maintainer or Responsible Maintainer.  They are
under no obligation to review posted patches - but, of course, are invited
to do so!

PowerPC			Andrew Cagney		[email protected]
CRIS			Hans-Peter Nilsson	[email protected]
IA64			Jeff Johnston		[email protected]
MIPS			Joel Brobecker		[email protected]
m32r			Kei Sakamoto		[email protected]
PowerPC			Kevin Buettner		[email protected]
CRIS			Orjan Friberg		[email protected]
HPPA			Randolph Chung		[email protected]
S390			Ulrich Weigand		[email protected]
djgpp			DJ Delorie		[email protected]
			[Please use this address to contact DJ about DJGPP]
tui			Stephane Carrez		[email protected]
ia64			Kevin Buettner		[email protected]
AIX			Kevin Buettner		[email protected]
GNU/Linux PPC native	Kevin Buettner		[email protected]
gdb.java tests		Anthony Green		[email protected]
FreeBSD native & host	David O'Brien		[email protected]
event loop		Elena Zannoni		[email protected]
generic symtabs		Elena Zannoni		[email protected]
dwarf readers		Elena Zannoni		[email protected]
elf reader		Elena Zannoni		[email protected]
stabs reader		Elena Zannoni		[email protected]
readline/		Elena Zannoni		[email protected]
NetBSD native & host	Jason Thorpe		[email protected]
Pascal support		Pierre Muller		[email protected]
avr			Theodore A. Roth	[email protected]
Modula-2 support	Gaius Mulley		[email protected]


			Write After Approval
			   (alphabetic)

To get recommended for the Write After Approval list you need a valid
FSF assignment and have submitted one good patch.

Pedro Alves					[email protected]
David Anderson					[email protected]
John David Anglin				[email protected]
Shrinivas Atre					[email protected]
Scott Bambrough					[email protected]
Jan Beulich					[email protected]
Jim Blandy					[email protected]
Philip Blundell					[email protected]
Per Bothner					[email protected]
Joel Brobecker					[email protected]
Dave Brolley					[email protected]
Paul Brook					[email protected]
Julian Brown					[email protected]
Kevin Buettner					[email protected]
Andrew Cagney					[email protected]
David Carlton					[email protected]
Stephane Carrez					[email protected]
Michael Chastain				[email protected]
Eric Christopher				[email protected]
Randolph Chung					[email protected]
Nick Clifton					[email protected]
J.T. Conklin					[email protected]
Brendan Conoboy					[email protected]
DJ Delorie					[email protected]
Philippe De Muyter				[email protected]
Dhananjay Deshpande				[email protected]
Klee Dienes					[email protected]
Gabriel Dos Reis                                [email protected]
Richard Earnshaw				[email protected]
Steve Ellcey					[email protected]
Frank Ch. Eigler				[email protected]
Ben Elliston					[email protected]
Adam Fedor					[email protected]
Fred Fish					[email protected]
Brian Ford					[email protected]
Orjan Friberg					[email protected]
Nathan Froyd					[email protected]
Gary Funck					[email protected]
Paul Gilliam					[email protected]
Raoul Gough					[email protected]
Anthony Green			 		[email protected]
Matthew Green					[email protected]
Maxim Grigoriev					[email protected]
Jerome Guitton					[email protected]
Ben Harris					[email protected]
Richard Henderson				[email protected]
Aldy Hernandez					[email protected]
Paul Hilfinger					[email protected]
Matt Hiller					[email protected]
Kazu Hirata					[email protected]
Jeff Holcomb					[email protected]
Don Howard					[email protected]
Martin Hunt					[email protected]
Jim Ingham					[email protected]
Baurzhan Ismagulov				[email protected]
Manoj Iyer					[email protected]
Daniel Jacobowitz				[email protected]
Andreas Jaeger					[email protected]
Jeff Johnston					[email protected]
Geoff Keating					[email protected]
Mark Kettenis					[email protected]
Jim Kingdon					[email protected]
Jan Kratochvil					[email protected]
Jonathan Larmour				[email protected]
Jeff Law					[email protected]
David Lecomber					[email protected]
Robert Lipe					[email protected]
H.J. Lu						[email protected]
Michal Ludvig                                   [email protected]
Glen McCready					[email protected]
Greg McGary					[email protected]
Roland McGrath					[email protected]
Bryce McKinlay					[email protected]
Jason Merrill					[email protected]
David S. Miller					[email protected]
Mark Mitchell					[email protected]
Marko Mlinar                                    [email protected]
Alan Modra					[email protected]
Jason Molenda					[email protected]
Pierre Muller					[email protected]
Gaius Mulley                                    [email protected]
Joseph Myers					[email protected]
Fernando Nasser					[email protected]
Adam Nemet					[email protected]
Nathanael Nerode				[email protected]
Hans-Peter Nilsson				[email protected]
David O'Brien					[email protected]
Alexandre Oliva					[email protected]
Denis Pilat					[email protected]
Vladimir Prus                                   [email protected]
Qinwei							[email protected]
Ramana Radhakrishnan 				[email protected]
Frederic Riss					[email protected]
Tom Rix						[email protected]
Nick Roberts					[email protected]
Bob Rossi 					[email protected]
Theodore A. Roth				[email protected]
Ian Roxborough					[email protected]
Grace Sainsbury					[email protected]
Kei Sakamoto					[email protected]
Mark Salter					[email protected]
Richard Sandiford				[email protected]
Peter Schauer					[email protected]
Andreas Schwab					[email protected]
Keith Seitz					[email protected]
Stan Shebs					[email protected]
Mark Shinwell					[email protected]
Aidan Skinner					[email protected]
Jiri Smid					[email protected]
David Smith					[email protected]
Stephen P. Smith				[email protected]
Jackie Smith Cashion				[email protected]
Michael Snyder					[email protected]
Petr Sorfa					[email protected]
Andrew Stubbs					[email protected]
Ian Lance Taylor				[email protected]
Gary Thomas					[email protected]
Jason Thorpe					[email protected]
Caroline Tice					[email protected]
Tom Tromey					[email protected]
David Ung					[email protected]
D Venkatasubramanian				[email protected]
Corinna Vinschen				[email protected]
Keith Walker					[email protected]
Kris Warkentin					[email protected]
Ulrich Weigand					[email protected]
Nathan Williams					[email protected]
Bob Wilson					[email protected]
Jim Wilson					[email protected]
Elena Zannoni					[email protected]
Eli Zaretskii					[email protected]
Wu Zhou						[email protected]
Yoshinori Sato					[email protected]


			Past Maintainers

Whenever removing yourself, or someone else, from this file, consider
listing their areas of development here for posterity.

Jimmy Guo (gdb.hp, tui)				guo at cup dot hp dot com
Jeff Law (hppa)					law at cygnus dot com
Daniel Berlin (C++ support)			dan at cgsoftware dot com
Nick Duffek (powerpc, SCO, Sol/x86)		nick at duffek dot com
David Taylor (d10v, sparc, utils, defs,
  expression evaluator, language support)	taylor at candd dot org
J.T. Conklin (dcache, NetBSD, remote, global)	jtc at acorntoolworks dot com
Frank Ch. Eigler (sim)				fche at redhat dot com
Per Bothner (Java)				per at bothner dot com
Anthony Green (Java)				green at redhat dot com
Fernando Nasser (testsuite/, mi, cli, KOD)      fnasser at redhat dot com
Mark Salter (testsuite/lib+config)		msalter at redhat dot com
Jim Kingdon (web pages)				kingdon at panix dot com
Jim Ingham (gdbtk, libgui)			jingham at apple dot com
Mark Kettenis (hurd native)			kettenis at gnu dot org
Ian Roxborough (in-tree tcl, tk, itcl)		irox at redhat dot com
Robert Lipe (SCO/Unixware)			rjl at sco dot com
Peter Schauer (global, AIX, xcoffsolib,
  Solaris/x86)					Peter.Schauer at mytum dot de
Scott Bambrough (ARM)				scottb at netwinder dot org
Philippe De Muyter (coff)			phdm at macqel dot be
Michael Chastain (testsuite)			mec.gnu at mindspring dot com


Folks that have been caught up in a paper trail:

David Carlton					[email protected]