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 Joel Brobecker brobecker@adacore.com
163 Kevin Buettner kevinb@redhat.com
164 Andrew Cagney cagney@gnu.org
165 Daniel Jacobowitz dan@debian.org
166 Mark Kettenis kettenis@gnu.org
167 Stan Shebs shebs@mozilla.com
168 Michael Snyder Michael.Snyder@access-company.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>
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 ,
259 (sim does not build with -Werror)
261 frv --target=frv-elf ,-Werror
263 h8300 --target=h8300-elf ,-Werror
265 i386 --target=i386-elf ,-Werror
266 Mark Kettenis kettenis@gnu.org
268 ia64 --target=ia64-linux-gnu ,-Werror
269 (--target=ia64-elf broken)
271 m32c --target=m32c-elf ,-Werror
272 Jim Blandy, jimb@codesourcery.com
274 m32r --target=m32r-elf ,-Werror
276 m68hc11 --target=m68hc11-elf ,-Werror ,
277 Stephane Carrez stcarrez@nerim.fr
279 m68k --target=m68k-elf ,-Werror
281 m88k --target=m88k-openbsd ,-Werror
282 Mark Kettenis kettenis@gnu.org
286 mep --target=mep-elf ,-Werror
287 Kevin Buettner kevinb@redhat.com
289 mips --target=mips-elf ,-Werror
291 mn10300 --target=mn10300-elf broken
292 (sim/ dies with make -j)
293 Michael Snyder Michael.Snyder@access-company.com
295 ms1 --target=ms1-elf ,-Werror
296 Kevin Buettner kevinb@redhat.com
300 pa --target=hppa-elf ,-Werror
302 powerpc --target=powerpc-eabi ,-Werror
304 s390 --target=s390-linux-gnu ,-Werror
306 score --target=score-elf
307 Qinwei qinwei@sunnorth.com.cn
309 sh --target=sh-elf ,-Werror
310 --target=sh64-elf ,-Werror
312 sparc --target=sparc64-solaris2.10 ,-Werror
313 (--target=sparc-elf broken)
315 spu --target=spu-elf ,-Werror
316 Ulrich Weigand uweigand@de.ibm.com
318 v850 --target=v850-elf ,-Werror
320 vax --target=vax-netbsd ,-Werror
322 x86-64 --target=x86_64-linux-gnu ,-Werror
324 xstormy16 --target=xstormy16-elf
325 Corinna Vinschen vinschen@redhat.com
327 xtensa --target=xtensa-elf
328 Maxim Grigoriev maxim2405@gmail.com
330 All developers recognized by this file can make arbitrary changes to
333 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
339 The Native maintainer is responsible for target specific native
340 support - typically shared libraries and quirks to procfs/ptrace/...
341 The Native maintainer works with the Arch and Core maintainers when
342 resolving more generic problems.
344 The host maintainer ensures that gdb can be built as a cross debugger on
347 AIX Joel Brobecker brobecker@adacore.com
349 djgpp native Eli Zaretskii eliz@gnu.org
350 GNU Hurd Alfred M. Szmidt ams@gnu.org
351 MS Windows (NT, '00, 9x, Me, XP) host & native
352 Chris Faylor cgf@alum.bu.edu
353 GNU/Linux/x86 native & host
354 Mark Kettenis kettenis@gnu.org
355 GNU/Linux MIPS native & host
356 Daniel Jacobowitz dan@debian.org
357 GNU/Linux m68k Andreas Schwab schwab@suse.de
358 FreeBSD native & host Mark Kettenis kettenis@gnu.org
362 Core: Generic components used by all of GDB
364 tracing Michael Snyder Michael.Snyder@access-company.com
365 threads Michael Snyder Michael.Snyder@access-company.com
366 Mark Kettenis kettenis@gnu.org
368 C++ Daniel Jacobowitz dan@debian.org
369 Objective C support Adam Fedor fedor@gnu.org
370 shared libs Kevin Buettner kevinb@redhat.com
372 documentation Eli Zaretskii eliz@gnu.org
375 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
376 threads (gdb.threads) Michael Snyder Michael.Snyder@access-company.com
377 trace (gdb.trace) Michael Snyder Michael.Snyder@access-company.com
380 UI: External (user) interfaces.
382 gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
383 Keith Seitz keiths@redhat.com
384 libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
389 gdb/gdbserver Daniel Jacobowitz dan@debian.org
391 Makefile.in, configure* ALL
393 mmalloc/ ALL Host maintainers
395 sim/ See sim/MAINTAINERS
397 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
399 Host maintainers (host dependant parts)
400 (but get your changes into the master version)
405 Authorized Committers
406 ---------------------
408 These are developers working on particular areas of GDB, who are trusted to
409 commit their own (or other developers') patches in those areas without
410 further review from a Global Maintainer or Responsible Maintainer. They are
411 under no obligation to review posted patches - but, of course, are invited
414 PowerPC Andrew Cagney cagney@gnu.org
415 CRIS Hans-Peter Nilsson hp@bitrange.com
416 IA64 Jeff Johnston jjohnstn@redhat.com
417 MIPS Joel Brobecker brobecker@adacore.com
418 m32r Kei Sakamoto sakamoto.kei@renesas.com
419 PowerPC Kevin Buettner kevinb@redhat.com
420 CRIS Orjan Friberg orjanf@axis.com
421 HPPA Randolph Chung tausq@debian.org
422 S390 Ulrich Weigand uweigand@de.ibm.com
423 djgpp DJ Delorie dj@delorie.com
424 [Please use this address to contact DJ about DJGPP]
425 tui Stephane Carrez stcarrez@nerim.fr
426 ia64 Kevin Buettner kevinb@redhat.com
427 AIX Kevin Buettner kevinb@redhat.com
428 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
429 gdb.java tests Anthony Green green@redhat.com
430 FreeBSD native & host David O'Brien obrien@freebsd.org
431 event loop Elena Zannoni ezannoni@redhat.com
432 generic symtabs Elena Zannoni ezannoni@redhat.com
433 dwarf readers Elena Zannoni ezannoni@redhat.com
434 elf reader Elena Zannoni ezannoni@redhat.com
435 stabs reader Elena Zannoni ezannoni@redhat.com
436 readline/ Elena Zannoni ezannoni@redhat.com
437 NetBSD native & host Jason Thorpe thorpej@netbsd.org
438 Pascal support Pierre Muller muller@sources.redhat.com
439 avr Theodore A. Roth troth@openavr.org
440 Modula-2 support Gaius Mulley gaius@glam.ac.uk
446 To get recommended for the Write After Approval list you need a valid
447 FSF assignment and have submitted one good patch.
449 Pedro Alves pedro_alves@portugalmail.pt
450 David Anderson davea@sgi.com
451 John David Anglin dave.anglin@nrc-cnrc.gc.ca
452 Shrinivas Atre shrinivasa@kpitcummins.com
453 Scott Bambrough scottb@netwinder.org
454 Jan Beulich jbeulich@novell.com
455 Jim Blandy jimb@codesourcery.com
456 Philip Blundell philb@gnu.org
457 Per Bothner per@bothner.com
458 Joel Brobecker brobecker@adacore.com
459 Dave Brolley brolley@redhat.com
460 Paul Brook paul@codesourcery.com
461 Julian Brown julian@codesourcery.com
462 Kevin Buettner kevinb@redhat.com
463 Andrew Cagney cagney@gnu.org
464 David Carlton carlton@bactrian.org
465 Stephane Carrez stcarrez@nerim.fr
466 Michael Chastain mec.gnu@mindspring.com
467 Eric Christopher echristo@apple.com
468 Randolph Chung tausq@debian.org
469 Nick Clifton nickc@redhat.com
470 J.T. Conklin jtc@acorntoolworks.com
471 Brendan Conoboy blc@redhat.com
472 Ludovic Courtès ludo@gnu.org
473 DJ Delorie dj@redhat.com
474 Philippe De Muyter phdm@macqel.be
475 Dhananjay Deshpande dhananjayd@kpitcummins.com
476 Klee Dienes kdienes@apple.com
477 Gabriel Dos Reis gdr@integrable-solutions.net
478 Richard Earnshaw rearnsha@arm.com
479 Steve Ellcey sje@cup.hp.com
480 Frank Ch. Eigler fche@redhat.com
481 Ben Elliston bje@gnu.org
482 Adam Fedor fedor@gnu.org
483 Brian Ford ford@vss.fsi.com
484 Orjan Friberg orjanf@axis.com
485 Nathan Froyd froydnj@codesourcery.com
486 Gary Funck gary@intrepid.com
487 Paul Gilliam pgilliam@us.ibm.com
488 Raoul Gough RaoulGough@yahoo.co.uk
489 Anthony Green green@redhat.com
490 Matthew Green mrg@eterna.com.au
491 Maxim Grigoriev maxim2405@gmail.com
492 Jerome Guitton guitton@act-europe.fr
493 Ben Harris bjh21@netbsd.org
494 Richard Henderson rth@redhat.com
495 Aldy Hernandez aldyh@redhat.com
496 Paul Hilfinger hilfinger@gnat.com
497 Matt Hiller hiller@redhat.com
498 Kazu Hirata kazu@cs.umass.edu
499 Jeff Holcomb jeffh@redhat.com
500 Don Howard dhoward@redhat.com
501 Martin Hunt hunt@redhat.com
502 Jim Ingham jingham@apple.com
503 Baurzhan Ismagulov ibr@radix50.net
504 Manoj Iyer manjo@austin.ibm.com
505 Daniel Jacobowitz dan@debian.org
506 Andreas Jaeger aj@suse.de
507 Jeff Johnston jjohnstn@redhat.com
508 Geoff Keating geoffk@redhat.com
509 Mark Kettenis kettenis@gnu.org
510 Jim Kingdon kingdon@panix.com
511 Jan Kratochvil jan.kratochvil@redhat.com
512 Jonathan Larmour jlarmour@redhat.co.uk
513 Jeff Law law@redhat.com
514 David Lecomber david@streamline-computing.com
515 Robert Lipe rjl@sco.com
516 H.J. Lu hjl@lucon.org
517 Michal Ludvig mludvig@suse.cz
518 Glen McCready gkm@redhat.com
519 Greg McGary greg@mcgary.org
520 Roland McGrath roland@redhat.com
521 Bryce McKinlay mckinlay@redhat.com
522 Jason Merrill jason@redhat.com
523 David S. Miller davem@redhat.com
524 Mark Mitchell mark@codesourcery.com
525 Marko Mlinar markom@opencores.org
526 Alan Modra amodra@bigpond.net.au
527 Jason Molenda jmolenda@apple.com
528 Pierre Muller muller@sources.redhat.com
529 Gaius Mulley gaius@glam.ac.uk
530 Joseph Myers joseph@codesourcery.com
531 Fernando Nasser fnasser@redhat.com
532 Adam Nemet anemet@caviumnetworks.com
533 Nathanael Nerode neroden@gcc.gnu.org
534 Hans-Peter Nilsson hp@bitrange.com
535 David O'Brien obrien@freebsd.org
536 Alexandre Oliva aoliva@redhat.com
537 Denis Pilat denis.pilat@st.com
538 Vladimir Prus vladimir@codesourcery.com
539 Qinwei qinwei@sunnorth.com.cn
540 Ramana Radhakrishnan ramana.radhakrishnan@codito.com
541 Frederic Riss frederic.riss@st.com
542 Tom Rix trix@redhat.com
543 Nick Roberts nickrob@snap.net.nz
544 Bob Rossi bob_rossi@cox.net
545 Theodore A. Roth troth@openavr.org
546 Ian Roxborough irox@redhat.com
547 Maciej W. Rozycki macro@linux-mips.org
548 Grace Sainsbury graces@redhat.com
549 Kei Sakamoto sakamoto.kei@renesas.com
550 Mark Salter msalter@redhat.com
551 Richard Sandiford richard@codesourcery.com
552 Peter Schauer Peter.Schauer@mytum.de
553 Andreas Schwab schwab@suse.de
554 Keith Seitz keiths@redhat.com
555 Stan Shebs shebs@mozilla.com
556 Mark Shinwell shinwell@codesourcery.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@access-company.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 Caroline Tice ctice@apple.com
569 Tom Tromey tromey@redhat.com
570 David Ung davidu@mips.com
571 D Venkatasubramanian dvenkat@noida.hcltech.com
572 Corinna Vinschen vinschen@redhat.com
573 Keith Walker keith.walker@arm.com
574 Kris Warkentin kewarken@qnx.com
575 Ulrich Weigand uweigand@de.ibm.com
576 Nathan Williams nathanw@wasabisystems.com
577 Bob Wilson bob.wilson@acm.org
578 Jim Wilson wilson@specifixinc.com
579 Elena Zannoni ezannoni@redhat.com
580 Eli Zaretskii eliz@gnu.org
581 Wu Zhou woodzltc@cn.ibm.com
582 Yoshinori Sato ysato@users.sourceforge.jp
587 Whenever removing yourself, or someone else, from this file, consider
588 listing their areas of development here for posterity.
590 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
591 Jeff Law (hppa) law at cygnus dot com
592 Daniel Berlin (C++ support) dan at cgsoftware dot com
593 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
594 David Taylor (d10v, sparc, utils, defs,
595 expression evaluator, language support) taylor at candd dot org
596 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
597 Frank Ch. Eigler (sim) fche at redhat dot com
598 Per Bothner (Java) per at bothner dot com
599 Anthony Green (Java) green at redhat dot com
600 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
601 Mark Salter (testsuite/lib+config) msalter at redhat dot com
602 Jim Kingdon (web pages) kingdon at panix dot com
603 Jim Ingham (gdbtk, libgui) jingham at apple dot com
604 Mark Kettenis (hurd native) kettenis at gnu dot org
605 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
606 Robert Lipe (SCO/Unixware) rjl at sco dot com
607 Peter Schauer (global, AIX, xcoffsolib,
608 Solaris/x86) Peter.Schauer at mytum dot de
609 Scott Bambrough (ARM) scottb at netwinder dot org
610 Philippe De Muyter (coff) phdm at macqel dot be
611 Michael Chastain (testsuite) mec.gnu at mindspring dot com
616 Folks that have been caught up in a paper trail:
618 David Carlton carlton@bactrian.org