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