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@mozilla.com
168 Michael Snyder Michael.Snyder@PalmSource.com
169 Ulrich Weigand Ulrich.Weigand@de.ibm.com
170 Elena Zannoni ezannoni@redhat.com
171 Eli Zaretskii eliz@gnu.org
177 The current release manager is: Joel Brobecker <brobecker@adacore.com>
179 His responsibilities are:
181 * organizing, scheduling, and managing releases of GDB.
183 * deciding the approval and commit policies for release branches,
184 and can change them as needed.
191 These volunteers track all patches submitted to the gdb-patches list. They
192 endeavor to prevent any posted patch from being overlooked; work with
193 contributors to meet GDB's coding style and general requirements, along with
194 FSF copyright assignments; remind (ping) responsible maintainers to review
195 patches; and ensure that contributors are given credit.
197 Current patch champions (in alphabetical order):
199 Randolph Chung <tausq@debian.org>
200 Daniel Jacobowitz <dan@debian.org>
204 Responsible Maintainers
205 -----------------------
207 These developers have agreed to review patches in specific areas of GDB, in
208 which they have knowledge and experience. These areas are generally broad;
209 the role of a responsible maintainer is to provide coherent and cohesive
210 structure within their area of GDB, to assure that patches from many
211 different contributors all work together for the best results.
213 Global maintainers will defer to responsible maintainers within their areas,
214 as long as the responsible maintainer is active. Active means that
215 responsible maintainers agree to review submitted patches in their area
216 promptly; patches and followups should generally be answered within a week.
217 If a responsible maintainer is interested in reviewing a patch but will not
218 have time within a week of posting, the maintainer should send an
219 acknowledgement of the patch to the gdb-patches mailing list, and
220 plan to follow up with a review within a month. These deadlines are for
221 initial responses to a patch - if the maintainer has suggestions
222 or questions, it may take an extended discussion before the patch
223 is ready to commit. There are no written requirements for discussion,
224 but maintainers are asked to be responsive.
226 If a responsible maintainer misses these deadlines occasionally (e.g.
227 vacation or unexpected workload), it's not a disaster - any global
228 maintainer may step in to review the patch. But sometimes life intervenes
229 more permanently, and a maintainer may no longer have time for these duties.
230 When this happens, he or she should step down (either into the Authorized
231 Committers section if still interested in the area, or simply removed from
232 the list of Responsible Maintainers if not).
234 If a responsible maintainer is unresponsive for an extended period of time
235 without stepping down, please contact the Global Maintainers; they will try
236 to contact the maintainer directly and fix the problem - potentially by
237 removing that maintainer from their listed position.
239 If there are several maintainers for a given domain then any one of them
240 may review a submitted patch.
242 Target Instruction Set Architectures:
244 The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
245 (Operating System / Application Binary Interface) issues including CPU
248 The Target/Architecture maintainer works with the host maintainer when
249 resolving build issues. The Target/Architecture maintainer works with
250 the native maintainer when resolving ABI issues.
252 alpha --target=alpha-elf ,-Werror
254 arm --target=arm-elf ,-Werror
255 Richard Earnshaw rearnsha@arm.com
257 avr --target=avr ,-Werror
259 cris --target=cris-elf ,-Werror ,
260 (sim does not build with -Werror)
264 frv --target=frv-elf ,-Werror
266 h8300 --target=h8300-elf ,-Werror
268 i386 --target=i386-elf ,-Werror
269 Mark Kettenis kettenis@gnu.org
271 ia64 --target=ia64-linux-gnu ,-Werror
272 (--target=ia64-elf broken)
274 m32c --target=m32c-elf ,-Werror
275 Jim Blandy, jimb@codesourcery.com
277 m32r --target=m32r-elf ,-Werror
279 m68hc11 --target=m68hc11-elf ,-Werror ,
280 Stephane Carrez stcarrez@nerim.fr
282 m68k --target=m68k-elf ,-Werror
284 m88k --target=m88k-openbsd ,-Werror
285 Mark Kettenis kettenis@gnu.org
289 mep --target=mep-elf ,-Werror
290 Kevin Buettner kevinb@redhat.com
292 mips --target=mips-elf ,-Werror
294 mn10300 --target=mn10300-elf broken
295 (sim/ dies with make -j)
296 Michael Snyder Michael.Snyder@PalmSource.com
298 ms1 --target=ms1-elf ,-Werror
299 Kevin Buettner kevinb@redhat.com
303 pa --target=hppa-elf ,-Werror
305 powerpc --target=powerpc-eabi ,-Werror
307 s390 --target=s390-linux-gnu ,-Werror
309 score --target=score-elf
310 Qinwei qinwei@sunnorth.com.cn
312 sh --target=sh-elf ,-Werror
313 --target=sh64-elf ,-Werror
315 sparc --target=sparc64-solaris2.10 ,-Werror
316 (--target=sparc-elf broken)
318 spu --target=spu-elf ,-Werror
319 Ulrich Weigand uweigand@de.ibm.com
321 v850 --target=v850-elf ,-Werror
323 vax --target=vax-netbsd ,-Werror
325 x86-64 --target=x86_64-linux-gnu ,-Werror
327 xstormy16 --target=xstormy16-elf
328 Corinna Vinschen vinschen@redhat.com
330 xtensa --target=xtensa-elf
331 Maxim Grigoriev maxim2405@gmail.com
333 All developers recognized by this file can make arbitrary changes to
336 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
342 The Native maintainer is responsible for target specific native
343 support - typically shared libraries and quirks to procfs/ptrace/...
344 The Native maintainer works with the Arch and Core maintainers when
345 resolving more generic problems.
347 The host maintainer ensures that gdb can be built as a cross debugger on
350 AIX Joel Brobecker brobecker@adacore.com
352 djgpp native Eli Zaretskii eliz@gnu.org
353 GNU Hurd Alfred M. Szmidt ams@gnu.org
354 MS Windows (NT, '00, 9x, Me, XP) host & native
355 Chris Faylor cgf@alum.bu.edu
356 GNU/Linux/x86 native & host
357 Mark Kettenis kettenis@gnu.org
358 GNU/Linux MIPS native & host
359 Daniel Jacobowitz dan@debian.org
360 GNU/Linux m68k Andreas Schwab schwab@suse.de
361 FreeBSD native & host Mark Kettenis kettenis@gnu.org
365 Core: Generic components used by all of GDB
367 tracing Michael Snyder Michael.Snyder@PalmSource.com
368 threads Michael Snyder Michael.Snyder@PalmSource.com
369 Mark Kettenis kettenis@gnu.org
371 C++ Daniel Jacobowitz dan@debian.org
372 Objective C support Adam Fedor fedor@gnu.org
373 shared libs Kevin Buettner kevinb@redhat.com
375 documentation Eli Zaretskii eliz@gnu.org
378 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
379 threads (gdb.threads) Michael Snyder Michael.Snyder@PalmSource.com
380 trace (gdb.trace) Michael Snyder Michael.Snyder@PalmSource.com
383 UI: External (user) interfaces.
385 gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
386 Keith Seitz keiths@redhat.com
387 libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
392 gdb/gdbserver Daniel Jacobowitz dan@debian.org
394 Makefile.in, configure* ALL
396 mmalloc/ ALL Host maintainers
398 sim/ See sim/MAINTAINERS
400 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
402 Host maintainers (host dependant parts)
403 (but get your changes into the master version)
408 Authorized Committers
409 ---------------------
411 These are developers working on particular areas of GDB, who are trusted to
412 commit their own (or other developers') patches in those areas without
413 further review from a Global Maintainer or Responsible Maintainer. They are
414 under no obligation to review posted patches - but, of course, are invited
417 PowerPC Andrew Cagney cagney@gnu.org
418 CRIS Hans-Peter Nilsson hp@bitrange.com
419 IA64 Jeff Johnston jjohnstn@redhat.com
420 MIPS Joel Brobecker brobecker@adacore.com
421 m32r Kei Sakamoto sakamoto.kei@renesas.com
422 PowerPC Kevin Buettner kevinb@redhat.com
423 CRIS Orjan Friberg orjanf@axis.com
424 HPPA Randolph Chung tausq@debian.org
425 S390 Ulrich Weigand uweigand@de.ibm.com
426 djgpp DJ Delorie dj@delorie.com
427 [Please use this address to contact DJ about DJGPP]
428 tui Stephane Carrez stcarrez@nerim.fr
429 ia64 Kevin Buettner kevinb@redhat.com
430 AIX Kevin Buettner kevinb@redhat.com
431 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
432 gdb.java tests Anthony Green green@redhat.com
433 FreeBSD native & host David O'Brien obrien@freebsd.org
434 event loop Elena Zannoni ezannoni@redhat.com
435 generic symtabs Elena Zannoni ezannoni@redhat.com
436 dwarf readers Elena Zannoni ezannoni@redhat.com
437 elf reader Elena Zannoni ezannoni@redhat.com
438 stabs reader Elena Zannoni ezannoni@redhat.com
439 readline/ Elena Zannoni ezannoni@redhat.com
440 NetBSD native & host Jason Thorpe thorpej@netbsd.org
441 Pascal support Pierre Muller muller@sources.redhat.com
442 avr Theodore A. Roth troth@openavr.org
443 Modula-2 support Gaius Mulley gaius@glam.ac.uk
449 To get recommended for the Write After Approval list you need a valid
450 FSF assignment and have submitted one good patch.
452 Pedro Alves pedro_alves@portugalmail.pt
453 David Anderson davea@sgi.com
454 John David Anglin dave.anglin@nrc-cnrc.gc.ca
455 Shrinivas Atre shrinivasa@kpitcummins.com
456 Scott Bambrough scottb@netwinder.org
457 Jan Beulich jbeulich@novell.com
458 Jim Blandy jimb@codesourcery.com
459 Philip Blundell philb@gnu.org
460 Per Bothner per@bothner.com
461 Joel Brobecker brobecker@adacore.com
462 Dave Brolley brolley@redhat.com
463 Paul Brook paul@codesourcery.com
464 Julian Brown julian@codesourcery.com
465 Kevin Buettner kevinb@redhat.com
466 Andrew Cagney cagney@gnu.org
467 David Carlton carlton@bactrian.org
468 Stephane Carrez stcarrez@nerim.fr
469 Michael Chastain mec.gnu@mindspring.com
470 Eric Christopher echristo@apple.com
471 Randolph Chung tausq@debian.org
472 Nick Clifton nickc@redhat.com
473 J.T. Conklin jtc@acorntoolworks.com
474 Brendan Conoboy blc@redhat.com
475 DJ Delorie dj@redhat.com
476 Philippe De Muyter phdm@macqel.be
477 Dhananjay Deshpande dhananjayd@kpitcummins.com
478 Klee Dienes kdienes@apple.com
479 Gabriel Dos Reis gdr@integrable-solutions.net
480 Richard Earnshaw rearnsha@arm.com
481 Steve Ellcey sje@cup.hp.com
482 Frank Ch. Eigler fche@redhat.com
483 Ben Elliston bje@gnu.org
484 Adam Fedor fedor@gnu.org
485 Fred Fish fnf@ninemoons.com
486 Brian Ford ford@vss.fsi.com
487 Orjan Friberg orjanf@axis.com
488 Gary Funck gary@intrepid.com
489 Paul Gilliam pgilliam@us.ibm.com
490 Raoul Gough RaoulGough@yahoo.co.uk
491 Anthony Green green@redhat.com
492 Matthew Green mrg@eterna.com.au
493 Maxim Grigoriev maxim2405@gmail.com
494 Jerome Guitton guitton@act-europe.fr
495 Ben Harris bjh21@netbsd.org
496 Richard Henderson rth@redhat.com
497 Aldy Hernandez aldyh@redhat.com
498 Paul Hilfinger hilfinger@gnat.com
499 Matt Hiller hiller@redhat.com
500 Kazu Hirata kazu@cs.umass.edu
501 Jeff Holcomb jeffh@redhat.com
502 Don Howard dhoward@redhat.com
503 Martin Hunt hunt@redhat.com
504 Jim Ingham jingham@apple.com
505 Baurzhan Ismagulov ibr@radix50.net
506 Manoj Iyer manjo@austin.ibm.com
507 Daniel Jacobowitz dan@debian.org
508 Andreas Jaeger aj@suse.de
509 Jeff Johnston jjohnstn@redhat.com
510 Geoff Keating geoffk@redhat.com
511 Mark Kettenis kettenis@gnu.org
512 Jim Kingdon kingdon@panix.com
513 Jan Kratochvil jan.kratochvil@redhat.com
514 Jonathan Larmour jlarmour@redhat.co.uk
515 Jeff Law law@redhat.com
516 David Lecomber david@streamline-computing.com
517 Robert Lipe rjl@sco.com
518 H.J. Lu hjl@lucon.org
519 Michal Ludvig mludvig@suse.cz
520 Glen McCready gkm@redhat.com
521 Greg McGary greg@mcgary.org
522 Roland McGrath roland@redhat.com
523 Bryce McKinlay mckinlay@redhat.com
524 Jason Merrill jason@redhat.com
525 David S. Miller davem@redhat.com
526 Mark Mitchell mark@codesourcery.com
527 Marko Mlinar markom@opencores.org
528 Alan Modra amodra@bigpond.net.au
529 Jason Molenda jmolenda@apple.com
530 Pierre Muller muller@sources.redhat.com
531 Gaius Mulley gaius@glam.ac.uk
532 Joseph Myers joseph@codesourcery.com
533 Fernando Nasser fnasser@redhat.com
534 Adam Nemet anemet@caviumnetworks.com
535 Nathanael Nerode neroden@gcc.gnu.org
536 Hans-Peter Nilsson hp@bitrange.com
537 David O'Brien obrien@freebsd.org
538 Alexandre Oliva aoliva@redhat.com
539 Denis Pilat denis.pilat@st.com
540 Vladimir Prus vladimir@codesourcery.com
541 Qinwei qinwei@sunnorth.com.cn
542 Ramana Radhakrishnan ramana.radhakrishnan@codito.com
543 Frederic Riss frederic.riss@st.com
544 Tom Rix trix@redhat.com
545 Nick Roberts nickrob@snap.net.nz
546 Bob Rossi bob_rossi@cox.net
547 Theodore A. Roth troth@openavr.org
548 Ian Roxborough irox@redhat.com
549 Grace Sainsbury graces@redhat.com
550 Kei Sakamoto sakamoto.kei@renesas.com
551 Mark Salter msalter@redhat.com
552 Richard Sandiford richard@codesourcery.com
553 Peter Schauer Peter.Schauer@mytum.de
554 Andreas Schwab schwab@suse.de
555 Keith Seitz keiths@redhat.com
556 Stan Shebs shebs@mozilla.com
557 Aidan Skinner aidan@velvet.net
558 Jiri Smid smid@suse.cz
559 David Smith dsmith@redhat.com
560 Stephen P. Smith ischis2@cox.net
561 Jackie Smith Cashion jsmith@redhat.com
562 Michael Snyder Michael.Snyder@PalmSource.com
563 Petr Sorfa petrs@caldera.com
564 Andrew Stubbs andrew.stubbs@st.com
565 Ian Lance Taylor ian@airs.com
566 Gary Thomas gthomas@redhat.com
567 Jason Thorpe thorpej@netbsd.org
568 Tom Tromey tromey@redhat.com
569 David Ung davidu@mips.com
570 D Venkatasubramanian dvenkat@noida.hcltech.com
571 Corinna Vinschen vinschen@redhat.com
572 Keith Walker keith.walker@arm.com
573 Kris Warkentin kewarken@qnx.com
574 Ulrich Weigand uweigand@de.ibm.com
575 Nathan Williams nathanw@wasabisystems.com
576 Bob Wilson bob.wilson@acm.org
577 Jim Wilson wilson@specifixinc.com
578 Elena Zannoni ezannoni@redhat.com
579 Eli Zaretskii eliz@gnu.org
580 Wu Zhou woodzltc@cn.ibm.com
581 Yoshinori Sato ysato@users.sourceforge.jp
586 Whenever removing yourself, or someone else, from this file, consider
587 listing their areas of development here for posterity.
589 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
590 Jeff Law (hppa) law at cygnus dot com
591 Daniel Berlin (C++ support) dan at cgsoftware dot com
592 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
593 David Taylor (d10v, sparc, utils, defs,
594 expression evaluator, language support) taylor at candd dot org
595 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
596 Frank Ch. Eigler (sim) fche at redhat dot com
597 Per Bothner (Java) per at bothner dot com
598 Anthony Green (Java) green at redhat dot com
599 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
600 Mark Salter (testsuite/lib+config) msalter at redhat dot com
601 Jim Kingdon (web pages) kingdon at panix dot com
602 Jim Ingham (gdbtk, libgui) jingham at apple dot com
603 Mark Kettenis (hurd native) kettenis at gnu dot org
604 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
605 Robert Lipe (SCO/Unixware) rjl at sco dot com
606 Peter Schauer (global, AIX, xcoffsolib,
607 Solaris/x86) Peter.Schauer at mytum dot de
608 Scott Bambrough (ARM) scottb at netwinder dot org
609 Philippe De Muyter (coff) phdm at macqel dot be
610 Michael Chastain (testsuite) mec.gnu at mindspring dot com
614 Folks that have been caught up in a paper trail:
616 David Carlton carlton@bactrian.org