8 This file describes different groups of people who are, together, the
9 maintainers and developers of the GDB project. Don't worry - it sounds
10 more complicated than it really is.
12 There are four groups of GDB developers, covering the patch development and
15 - The Global Maintainers.
17 These are the developers in charge of most daily development. They
18 have wide authority to apply and reject patches, but defer to the
19 Responsible Maintainers (see below) within their spheres of
22 - The Responsible Maintainers.
24 These are developers who have expertise and interest in a particular
25 area of GDB, who are generally available to review patches, and who
26 prefer to enforce a single vision within their areas.
28 - The Authorized Committers.
30 These are developers who are trusted to make changes within a specific
31 area of GDB without additional oversight.
33 - The Write After Approval Maintainers.
35 These are developers who have write access to the GDB source tree. They
36 can check in their own changes once a developer with the appropriate
37 authority has approved the changes; they can also apply the Obvious
40 All maintainers are encouraged to post major patches to the gdb-patches
41 mailing list for comments, even if they have the authority to commit the
42 patch without review from another maintainer. This especially includes
43 patches which change internal interfaces (e.g. global functions, data
44 structures) or external interfaces (e.g. user, remote, MI, et cetera).
46 The term "review" is used in this file to describe several kinds of feedback
47 from a maintainer: approval, rejection, and requests for changes or
48 clarification with the intention of approving a revised version. Review is
49 a privilege and/or responsibility of various positions among the GDB
50 Maintainers. Of course, anyone - whether they hold a position but not the
51 relevant one for a particular patch, or are just following along on the
52 mailing lists for fun, or anything in between - may suggest changes or
53 ask questions about a patch!
55 There's also a couple of other people who play special roles in the GDB
56 community, separately from the patch process:
58 - The GDB Steering Committee.
60 These are the official (FSF-appointed) maintainers of GDB. They have
61 final and overriding authority for all GDB-related decisions, including
62 anything described in this file. The committee is not generally
63 involved in day-to-day development (although its members may be, as
66 - The Release Manager.
68 This developer is in charge of making new releases of GDB.
70 - The Patch Champions.
72 These volunteers make sure that no contribution is overlooked or
75 Most changes to the list of maintainers in this file are handled by
76 consensus among the global maintainers and any other involved parties.
77 In cases where consensus can not be reached, the global maintainers may
78 ask the Steering Committee for a final decision.
84 All maintainers listed in this file, including the Write After Approval
85 developers, are allowed to check in obvious fixes.
87 An "obvious fix" means that there is no possibility that anyone will
88 disagree with the change.
90 A good mental test is "will the person who hates my work the most be
91 able to find fault with the change" - if so, then it's not obvious and
92 needs to be posted first. :-)
94 Something like changing or bypassing an interface is _not_ an obvious
95 fix, since such a change without discussion will result in
96 instantaneous and loud complaints.
98 For documentation changes, about the only kind of fix that is obvious
99 is correction of a typo or bad English usage.
102 GDB Steering Committee
103 ----------------------
105 The members of the GDB Steering Committee are the FSF-appointed
106 maintainers of the GDB project.
108 The Steering Committee has final authority for all GDB-related topics;
109 they may make whatever changes that they deem necessary, or that the FSF
110 requests. However, they are generally not involved in day-to-day
113 The current members of the steering committee are listed below, in
114 alphabetical order. Their affiliations are provided for reference only -
115 their membership on the Steering Committee is individual and not through
116 their affiliation, and they act on behalf of the GNU project.
118 Jim Blandy (CodeSourcery)
119 Andrew Cagney (Red Hat)
120 Robert Dewar (AdaCore, NYU)
122 Paul Hilfinger (UC Berkeley)
123 Dan Jacobowitz (CodeSourcery)
125 Richard Stallman (FSF)
126 Ian Lance Taylor (C2)
133 The global maintainers may review and commit any change to GDB, except in
134 areas with a Responsible Maintainer available. For major changes, or
135 changes to areas with other active developers, global maintainers are
136 strongly encouraged to post their own patches for feedback before
139 The global maintainers are responsible for reviewing patches to any area
140 for which no Responsible Maintainer is listed.
142 Global maintainers also have the authority to revert patches which should
143 not have been applied, e.g. patches which were not approved, controversial
144 patches committed under the Obvious Fix Rule, patches with important bugs
145 that can't be immediately fixed, or patches which go against an accepted and
146 documented roadmap for GDB development. Any global maintainer may request
147 the reversion of a patch. If no global maintainer, or responsible
148 maintainer in the affected areas, supports the patch (except for the
149 maintainer who originally committed it), then after 48 hours the maintainer
150 who called for the reversion may revert the patch.
152 No one may reapply a reverted patch without the agreement of the maintainer
153 who reverted it, or bringing the issue to the GDB Steering Committee for
156 At the moment there are no documented roadmaps for GDB development; in the
157 future, if there are, a reference to the list will be included here.
159 The current global maintainers are (in alphabetical order):
161 Jim Blandy jimb@codesourcery.com
162 Kevin Buettner kevinb@redhat.com
163 Andrew Cagney cagney@gnu.org
164 Fred Fish fnf@ninemoons.com
165 Daniel Jacobowitz dan@debian.org
166 Mark Kettenis kettenis@gnu.org
167 Stan Shebs shebs@apple.com
168 Michael Snyder Michael.Snyder@PalmSource.com
169 Elena Zannoni ezannoni@redhat.com
170 Eli Zaretskii eliz@gnu.org
176 The current release manager is: Joel Brobecker <brobecker@adacore.com>
178 His responsibilities are:
180 * organizing, scheduling, and managing releases of GDB.
182 * deciding the approval and commit policies for release branches,
183 and can change them as needed.
190 These volunteers track all patches submitted to the gdb-patches list. They
191 endeavor to prevent any posted patch from being overlooked; work with
192 contributors to meet GDB's coding style and general requirements, along with
193 FSF copyright assignments; remind (ping) responsible maintainers to review
194 patches; and ensure that contributors are given credit.
196 Current patch champions (in alphabetical order):
198 Randolph Chung <tausq@debian.org>
199 Daniel Jacobowitz <dan@debian.org>
203 Responsible Maintainers
204 -----------------------
206 These developers have agreed to review patches in specific areas of GDB, in
207 which they have knowledge and experience. These areas are generally broad;
208 the role of a responsible maintainer is to provide coherent and cohesive
209 structure within their area of GDB, to assure that patches from many
210 different contributors all work together for the best results.
212 Global maintainers will defer to responsible maintainers within their areas,
213 as long as the responsible maintainer is active. Active means that
214 responsible maintainers agree to review submitted patches in their area
215 promptly; patches and followups should generally be answered within a week.
216 If a responsible maintainer is interested in reviewing a patch but will not
217 have time within a week of posting, the maintainer should send an
218 acknowledgement of the patch to the gdb-patches mailing list, and
219 plan to follow up with a review within a month. These deadlines are for
220 initial responses to a patch - if the maintainer has suggestions
221 or questions, it may take an extended discussion before the patch
222 is ready to commit. There are no written requirements for discussion,
223 but maintainers are asked to be responsive.
225 If a responsible maintainer misses these deadlines occasionally (e.g.
226 vacation or unexpected workload), it's not a disaster - any global
227 maintainer may step in to review the patch. But sometimes life intervenes
228 more permanently, and a maintainer may no longer have time for these duties.
229 When this happens, he or she should step down (either into the Authorized
230 Committers section if still interested in the area, or simply removed from
231 the list of Responsible Maintainers if not).
233 If a responsible maintainer is unresponsive for an extended period of time
234 without stepping down, please contact the Global Maintainers; they will try
235 to contact the maintainer directly and fix the problem - potentially by
236 removing that maintainer from their listed position.
238 If there are several maintainers for a given domain then any one of them
239 may review a submitted patch.
241 Target Instruction Set Architectures:
243 The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
244 (Operating System / Application Binary Interface) issues including CPU
247 The Target/Architecture maintainer works with the host maintainer when
248 resolving build issues. The Target/Architecture maintainer works with
249 the native maintainer when resolving ABI issues.
251 alpha --target=alpha-elf ,-Werror
253 arm --target=arm-elf ,-Werror
254 Richard Earnshaw rearnsha@arm.com
256 avr --target=avr ,-Werror
258 cris --target=cris-elf ,-Werror
262 frv --target=frv-elf ,-Werror
264 h8300 --target=h8300-elf ,-Werror
266 i386 --target=i386-elf ,-Werror
267 Mark Kettenis kettenis@gnu.org
269 ia64 --target=ia64-linux-gnu ,-Werror
270 (--target=ia64-elf broken)
272 m32c --target=m32c-elf ,-Werror
273 Jim Blandy, jimb@codesourcery.com
275 m32r --target=m32r-elf ,-Werror
277 m68hc11 --target=m68hc11-elf ,-Werror ,
278 Stephane Carrez stcarrez@nerim.fr
280 m68k --target=m68k-elf ,-Werror
282 m88k --target=m88k-openbsd ,-Werror
283 Mark Kettenis kettenis@gnu.org
287 mips --target=mips-elf ,-Werror
289 mn10300 --target=mn10300-elf broken
290 (sim/ dies with make -j)
291 Michael Snyder Michael.Snyder@PalmSource.com
293 ms1 --target=ms1-elf ,-Werror
294 Kevin Buettner kevinb@redhat.com
298 pa --target=hppa-elf ,-Werror
300 powerpc --target=powerpc-eabi ,-Werror
302 s390 --target=s390-linux-gnu ,-Werror
304 sh --target=sh-elf ,-Werror
305 --target=sh64-elf ,-Werror
307 sparc --target=sparc-elf ,-Werror
309 spu --target=spu-elf ,-Werror
310 Ulrich Weigand uweigand@de.ibm.com
312 v850 --target=v850-elf ,-Werror
314 vax --target=vax-netbsd ,-Werror
316 x86-64 --target=x86_64-linux-gnu ,-Werror
318 xstormy16 --target=xstormy16-elf
319 Corinna Vinschen vinschen@redhat.com
321 xtensa --target=xtensa-elf
322 Maxim Grigoriev maxim2405@gmail.com
324 All developers recognized by this file can make arbitrary changes to
327 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
333 The Native maintainer is responsible for target specific native
334 support - typically shared libraries and quirks to procfs/ptrace/...
335 The Native maintainer works with the Arch and Core maintainers when
336 resolving more generic problems.
338 The host maintainer ensures that gdb can be built as a cross debugger on
341 AIX Joel Brobecker brobecker@adacore.com
343 djgpp native Eli Zaretskii eliz@gnu.org
344 GNU Hurd Alfred M. Szmidt ams@gnu.org
345 MS Windows (NT, '00, 9x, Me, XP) host & native
346 Chris Faylor cgf@alum.bu.edu
347 GNU/Linux/x86 native & host
348 Mark Kettenis kettenis@gnu.org
349 GNU/Linux MIPS native & host
350 Daniel Jacobowitz dan@debian.org
351 GNU/Linux m68k Andreas Schwab schwab@suse.de
352 FreeBSD native & host Mark Kettenis kettenis@gnu.org
356 Core: Generic components used by all of GDB
358 tracing Michael Snyder Michael.Snyder@PalmSource.com
359 threads Michael Snyder Michael.Snyder@PalmSource.com
360 Mark Kettenis kettenis@gnu.org
362 C++ Daniel Jacobowitz dan@debian.org
363 Objective C support Adam Fedor fedor@gnu.org
364 shared libs Kevin Buettner kevinb@redhat.com
366 documentation Eli Zaretskii eliz@gnu.org
369 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
370 threads (gdb.threads) Michael Snyder Michael.Snyder@PalmSource.com
371 trace (gdb.trace) Michael Snyder Michael.Snyder@PalmSource.com
374 UI: External (user) interfaces.
376 gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
377 Keith Seitz keiths@redhat.com
378 libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
383 gdb/gdbserver Daniel Jacobowitz dan@debian.org
385 Makefile.in, configure* ALL
387 mmalloc/ ALL Host maintainers
389 sim/ See sim/MAINTAINERS
391 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
393 Host maintainers (host dependant parts)
394 (but get your changes into the master version)
399 Authorized Committers
400 ---------------------
402 These are developers working on particular areas of GDB, who are trusted to
403 commit their own (or other developers') patches in those areas without
404 further review from a Global Maintainer or Responsible Maintainer. They are
405 under no obligation to review posted patches - but, of course, are invited
408 PowerPC Andrew Cagney cagney@gnu.org
409 CRIS Hans-Peter Nilsson hp@bitrange.com
410 IA64 Jeff Johnston jjohnstn@redhat.com
411 MIPS Joel Brobecker brobecker@adacore.com
412 m32r Kei Sakamoto sakamoto.kei@renesas.com
413 PowerPC Kevin Buettner kevinb@redhat.com
414 CRIS Orjan Friberg orjanf@axis.com
415 HPPA Randolph Chung tausq@debian.org
416 S390 Ulrich Weigand uweigand@de.ibm.com
417 djgpp DJ Delorie dj@delorie.com
418 [Please use this address to contact DJ about DJGPP]
419 tui Stephane Carrez stcarrez@nerim.fr
420 ia64 Kevin Buettner kevinb@redhat.com
421 AIX Kevin Buettner kevinb@redhat.com
422 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
423 gdb.java tests Anthony Green green@redhat.com
424 FreeBSD native & host David O'Brien obrien@freebsd.org
425 event loop Elena Zannoni ezannoni@redhat.com
426 generic symtabs Elena Zannoni ezannoni@redhat.com
427 dwarf readers Elena Zannoni ezannoni@redhat.com
428 elf reader Elena Zannoni ezannoni@redhat.com
429 stabs reader Elena Zannoni ezannoni@redhat.com
430 readline/ Elena Zannoni ezannoni@redhat.com
431 NetBSD native & host Jason Thorpe thorpej@netbsd.org
432 Pascal support Pierre Muller muller@sources.redhat.com
433 avr Theodore A. Roth troth@openavr.org
434 Modula-2 support Gaius Mulley gaius@glam.ac.uk
440 To get recommended for the Write After Approval list you need a valid
441 FSF assignment and have submitted one good patch.
443 David Anderson davea@sgi.com
444 John David Anglin dave.anglin@nrc-cnrc.gc.ca
445 Shrinivas Atre shrinivasa@kpitcummins.com
446 Scott Bambrough scottb@netwinder.org
447 Jan Beulich jbeulich@novell.com
448 Jim Blandy jimb@codesourcery.com
449 Philip Blundell philb@gnu.org
450 Per Bothner per@bothner.com
451 Joel Brobecker brobecker@adacore.com
452 Dave Brolley brolley@redhat.com
453 Paul Brook paul@codesourcery.com
454 Julian Brown julian@codesourcery.com
455 Kevin Buettner kevinb@redhat.com
456 Andrew Cagney cagney@gnu.org
457 David Carlton carlton@bactrian.org
458 Stephane Carrez stcarrez@nerim.fr
459 Michael Chastain mec.gnu@mindspring.com
460 Eric Christopher echristo@apple.com
461 Randolph Chung tausq@debian.org
462 Nick Clifton nickc@redhat.com
463 J.T. Conklin jtc@acorntoolworks.com
464 Brendan Conoboy blc@redhat.com
465 DJ Delorie dj@redhat.com
466 Philippe De Muyter phdm@macqel.be
467 Dhananjay Deshpande dhananjayd@kpitcummins.com
468 Klee Dienes kdienes@apple.com
469 Richard Earnshaw rearnsha@arm.com
470 Steve Ellcey sje@cup.hp.com
471 Frank Ch. Eigler fche@redhat.com
472 Ben Elliston bje@gnu.org
473 Adam Fedor fedor@gnu.org
474 Fred Fish fnf@ninemoons.com
475 Brian Ford ford@vss.fsi.com
476 Orjan Friberg orjanf@axis.com
477 Paul Gilliam pgilliam@us.ibm.com
478 Raoul Gough RaoulGough@yahoo.co.uk
479 Anthony Green green@redhat.com
480 Matthew Green mrg@eterna.com.au
481 Maxim Grigoriev maxim2405@gmail.com
482 Jerome Guitton guitton@act-europe.fr
483 Ben Harris bjh21@netbsd.org
484 Richard Henderson rth@redhat.com
485 Aldy Hernandez aldyh@redhat.com
486 Paul Hilfinger hilfinger@gnat.com
487 Matt Hiller hiller@redhat.com
488 Kazu Hirata kazu@cs.umass.edu
489 Jeff Holcomb jeffh@redhat.com
490 Don Howard dhoward@redhat.com
491 Martin Hunt hunt@redhat.com
492 Jim Ingham jingham@apple.com
493 Baurzhan Ismagulov ibr@radix50.net
494 Manoj Iyer manjo@austin.ibm.com
495 Daniel Jacobowitz dan@debian.org
496 Andreas Jaeger aj@suse.de
497 Jeff Johnston jjohnstn@redhat.com
498 Geoff Keating geoffk@redhat.com
499 Mark Kettenis kettenis@gnu.org
500 Jim Kingdon kingdon@panix.com
501 Jonathan Larmour jlarmour@redhat.co.uk
502 Jeff Law law@redhat.com
503 David Lecomber david@streamline-computing.com
504 Robert Lipe rjl@sco.com
505 H.J. Lu hjl@lucon.org
506 Michal Ludvig mludvig@suse.cz
507 Glen McCready gkm@redhat.com
508 Greg McGary greg@mcgary.org
509 Roland McGrath roland@redhat.com
510 Bryce McKinlay mckinlay@redhat.com
511 Jason Merrill jason@redhat.com
512 David S. Miller davem@redhat.com
513 Mark Mitchell mark@codesourcery.com
514 Marko Mlinar markom@opencores.org
515 Alan Modra amodra@bigpond.net.au
516 Jason Molenda jmolenda@apple.com
517 Pierre Muller muller@sources.redhat.com
518 Gaius Mulley gaius@glam.ac.uk
519 Joseph Myers joseph@codesourcery.com
520 Fernando Nasser fnasser@redhat.com
521 Adam Nemet anemet@caviumnetworks.com
522 Nathanael Nerode neroden@gcc.gnu.org
523 Hans-Peter Nilsson hp@bitrange.com
524 David O'Brien obrien@freebsd.org
525 Alexandre Oliva aoliva@redhat.com
526 Vladimir Prus vladimir@codesourcery.com
527 Ramana Radhakrishnan ramana.radhakrishnan@codito.com
528 Frederic Riss frederic.riss@st.com
529 Tom Rix trix@redhat.com
530 Nick Roberts nickrob@snap.net.nz
531 Bob Rossi bob_rossi@cox.net
532 Theodore A. Roth troth@openavr.org
533 Ian Roxborough irox@redhat.com
534 Grace Sainsbury graces@redhat.com
535 Kei Sakamoto sakamoto.kei@renesas.com
536 Mark Salter msalter@redhat.com
537 Richard Sandiford richard@codesourcery.com
538 Peter Schauer Peter.Schauer@mytum.de
539 Andreas Schwab schwab@suse.de
540 Keith Seitz keiths@redhat.com
541 Stan Shebs shebs@apple.com
542 Aidan Skinner aidan@velvet.net
543 Jiri Smid smid@suse.cz
544 David Smith dsmith@redhat.com
545 Stephen P. Smith ischis2@cox.net
546 Jackie Smith Cashion jsmith@redhat.com
547 Michael Snyder Michael.Snyder@PalmSource.com
548 Petr Sorfa petrs@caldera.com
549 Andrew Stubbs andrew.stubbs@st.com
550 Ian Lance Taylor ian@airs.com
551 Gary Thomas gthomas@redhat.com
552 Jason Thorpe thorpej@netbsd.org
553 Tom Tromey tromey@redhat.com
554 David Ung davidu@mips.com
555 D Venkatasubramanian dvenkat@noida.hcltech.com
556 Corinna Vinschen vinschen@redhat.com
557 Keith Walker keith.walker@arm.com
558 Kris Warkentin kewarken@qnx.com
559 Ulrich Weigand uweigand@de.ibm.com
560 Nathan Williams nathanw@wasabisystems.com
561 Bob Wilson bob.wilson@acm.org
562 Jim Wilson wilson@specifixinc.com
563 Elena Zannoni ezannoni@redhat.com
564 Eli Zaretskii eliz@gnu.org
565 Wu Zhou woodzltc@cn.ibm.com
566 Yoshinori Sato ysato@users.sourceforge.jp
571 Whenever removing yourself, or someone else, from this file, consider
572 listing their areas of development here for posterity.
574 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
575 Jeff Law (hppa) law at cygnus dot com
576 Daniel Berlin (C++ support) dan at cgsoftware dot com
577 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
578 David Taylor (d10v, sparc, utils, defs,
579 expression evaluator, language support) taylor at candd dot org
580 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
581 Frank Ch. Eigler (sim) fche at redhat dot com
582 Per Bothner (Java) per at bothner dot com
583 Anthony Green (Java) green at redhat dot com
584 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
585 Mark Salter (testsuite/lib+config) msalter at redhat dot com
586 Jim Kingdon (web pages) kingdon at panix dot com
587 Jim Ingham (gdbtk, libgui) jingham at apple dot com
588 Mark Kettenis (hurd native) kettenis at gnu dot org
589 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
590 Robert Lipe (SCO/Unixware) rjl at sco dot com
591 Peter Schauer (global, AIX, xcoffsolib,
592 Solaris/x86) Peter.Schauer at mytum dot de
593 Scott Bambrough (ARM) scottb at netwinder dot org
594 Philippe De Muyter (coff) phdm at macqel dot be
595 Michael Chastain (testsuite) mec.gnu at mindspring dot com
599 Folks that have been caught up in a paper trail:
601 David Carlton carlton@bactrian.org