| blob | ef97479c82fe37621855e4cf751c811f72620baa |
1 GDB Maintainers
2 ===============
5 Overview
6 --------
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
13 review process:
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
20 responsibility.
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
38 Fix Rule (below).
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
64 individuals).
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
73 forgotten.
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.
81 The Obvious Fix Rule
82 --------------------
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
111 development.
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 (Mozilla)
119 Andrew Cagney (Red Hat)
120 Robert Dewar (AdaCore, NYU)
121 Klee Dienes (Apple)
122 Paul Hilfinger (UC Berkeley)
123 Dan Jacobowitz (CodeSourcery)
124 Stan Shebs (Mozilla)
125 Richard Stallman (FSF)
126 Ian Lance Taylor (C2)
127 Todd Whitesel
130 Global Maintainers
131 ------------------
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
137 committing.
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
154 discussion.
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@mozilla.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 msnyder@specifix.com
169 Ulrich Weigand Ulrich.Weigand@de.ibm.com
170 Elena Zannoni ezannoni@redhat.com
171 Eli Zaretskii eliz@gnu.org
174 Release Manager
175 ---------------
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.
188 Patch Champions
189 ---------------
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
245 variants.
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
284 mcore Deleted
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 msnyder@specifix.com
295 ms1 --target=ms1-elf ,-Werror
296 Kevin Buettner kevinb@redhat.com
298 ns32k Deleted
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
331 OBSOLETE targets.
333 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
334 above targets.
337 Host/Native:
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
345 their platform.
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 msnyder@specifix.com
365 threads Michael Snyder msnyder@specifix.com
366 Mark Kettenis kettenis@gnu.org
367 language support
368 Ada Joel Brobecker brobecker@adacore.com
369 Paul Hilfinger hilfinger@gnat.com
370 C++ Daniel Jacobowitz dan@debian.org
371 Objective C support Adam Fedor fedor@gnu.org
372 shared libs Kevin Buettner kevinb@redhat.com
374 documentation Eli Zaretskii eliz@gnu.org
375 (including NEWS)
376 testsuite
377 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
378 threads (gdb.threads) Michael Snyder msnyder@specifix.com
379 trace (gdb.trace) Michael Snyder msnyder@specifix.com
382 UI: External (user) interfaces.
384 gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
385 Keith Seitz keiths@redhat.com
386 libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
389 Misc:
391 gdb/gdbserver Daniel Jacobowitz dan@debian.org
393 Makefile.in, configure* ALL
395 mmalloc/ ALL Host maintainers
397 sim/ See sim/MAINTAINERS
399 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
400 ALL
401 Host maintainers (host dependant parts)
402 (but get your changes into the master version)
404 tcl/ tk/ itcl/ ALL
407 Authorized Committers
408 ---------------------
410 These are developers working on particular areas of GDB, who are trusted to
411 commit their own (or other developers') patches in those areas without
412 further review from a Global Maintainer or Responsible Maintainer. They are
413 under no obligation to review posted patches - but, of course, are invited
414 to do so!
416 PowerPC Andrew Cagney cagney@gnu.org
417 CRIS Hans-Peter Nilsson hp@bitrange.com
418 IA64 Jeff Johnston jjohnstn@redhat.com
419 MIPS Joel Brobecker brobecker@adacore.com
420 m32r Kei Sakamoto sakamoto.kei@renesas.com
421 PowerPC Kevin Buettner kevinb@redhat.com
422 CRIS Orjan Friberg orjanf@axis.com
423 HPPA Randolph Chung tausq@debian.org
424 S390 Ulrich Weigand uweigand@de.ibm.com
425 djgpp DJ Delorie dj@delorie.com
426 [Please use this address to contact DJ about DJGPP]
427 tui Stephane Carrez stcarrez@nerim.fr
428 ia64 Kevin Buettner kevinb@redhat.com
429 AIX Kevin Buettner kevinb@redhat.com
430 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
431 gdb.java tests Anthony Green green@redhat.com
432 FreeBSD native & host David O'Brien obrien@freebsd.org
433 event loop Elena Zannoni ezannoni@redhat.com
434 generic symtabs Elena Zannoni ezannoni@redhat.com
435 dwarf readers Elena Zannoni ezannoni@redhat.com
436 elf reader Elena Zannoni ezannoni@redhat.com
437 stabs reader Elena Zannoni ezannoni@redhat.com
438 readline/ Elena Zannoni ezannoni@redhat.com
439 NetBSD native & host Jason Thorpe thorpej@netbsd.org
440 Pascal support Pierre Muller muller@sources.redhat.com
441 avr Theodore A. Roth troth@openavr.org
442 Modula-2 support Gaius Mulley gaius@glam.ac.uk
445 Write After Approval
446 (alphabetic)
448 To get recommended for the Write After Approval list you need a valid
449 FSF assignment and have submitted one good patch.
451 Pedro Alves pedro_alves@portugalmail.pt
452 David Anderson davea@sgi.com
453 John David Anglin dave.anglin@nrc-cnrc.gc.ca
454 Shrinivas Atre shrinivasa@kpitcummins.com
455 Scott Bambrough scottb@netwinder.org
456 Thiago Jung Bauermann bauerman@br.ibm.com
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 Ludovic Courtès ludo@gnu.org
476 DJ Delorie dj@redhat.com
477 Philippe De Muyter phdm@macqel.be
478 Dhananjay Deshpande dhananjayd@kpitcummins.com
479 Markus Deuling deuling@de.ibm.com
480 Klee Dienes kdienes@apple.com
481 Gabriel Dos Reis gdr@integrable-solutions.net
482 Richard Earnshaw rearnsha@arm.com
483 Steve Ellcey sje@cup.hp.com
484 Frank Ch. Eigler fche@redhat.com
485 Ben Elliston bje@gnu.org
486 Doug Evans dje@google.com
487 Adam Fedor fedor@gnu.org
488 Brian Ford ford@vss.fsi.com
489 Orjan Friberg orjanf@axis.com
490 Nathan Froyd froydnj@codesourcery.com
491 Gary Funck gary@intrepid.com
492 Paul Gilliam pgilliam@us.ibm.com
493 Raoul Gough RaoulGough@yahoo.co.uk
494 Anthony Green green@redhat.com
495 Matthew Green mrg@eterna.com.au
496 Maxim Grigoriev maxim2405@gmail.com
497 Jerome Guitton guitton@act-europe.fr
498 Ben Harris bjh21@netbsd.org
499 Richard Henderson rth@redhat.com
500 Aldy Hernandez aldyh@redhat.com
501 Paul Hilfinger hilfinger@gnat.com
502 Matt Hiller hiller@redhat.com
503 Kazu Hirata kazu@cs.umass.edu
504 Jeff Holcomb jeffh@redhat.com
505 Don Howard dhoward@redhat.com
506 Nick Hudson nick.hudson@dsl.pipex.com
507 Martin Hunt hunt@redhat.com
508 Jim Ingham jingham@apple.com
509 Baurzhan Ismagulov ibr@radix50.net
510 Manoj Iyer manjo@austin.ibm.com
511 Daniel Jacobowitz dan@debian.org
512 Andreas Jaeger aj@suse.de
513 Jeff Johnston jjohnstn@redhat.com
514 Geoff Keating geoffk@redhat.com
515 Mark Kettenis kettenis@gnu.org
516 Jim Kingdon kingdon@panix.com
517 Jan Kratochvil jan.kratochvil@redhat.com
518 Jonathan Larmour jlarmour@redhat.co.uk
519 Jeff Law law@redhat.com
520 David Lecomber david@streamline-computing.com
521 Robert Lipe rjl@sco.com
522 H.J. Lu hjl.tools@gmail.com
523 Michal Ludvig mludvig@suse.cz
524 Luis Machado luisgpm@br.ibm.com
525 Glen McCready gkm@redhat.com
526 Greg McGary greg@mcgary.org
527 Roland McGrath roland@redhat.com
528 Bryce McKinlay mckinlay@redhat.com
529 Jason Merrill jason@redhat.com
530 David S. Miller davem@redhat.com
531 Mark Mitchell mark@codesourcery.com
532 Marko Mlinar markom@opencores.org
533 Alan Modra amodra@bigpond.net.au
534 Jason Molenda jmolenda@apple.com
535 Pierre Muller muller@sources.redhat.com
536 Gaius Mulley gaius@glam.ac.uk
537 Joseph Myers joseph@codesourcery.com
538 Fernando Nasser fnasser@redhat.com
539 Adam Nemet anemet@caviumnetworks.com
540 Nathanael Nerode neroden@gcc.gnu.org
541 Hans-Peter Nilsson hp@bitrange.com
542 David O'Brien obrien@freebsd.org
543 Alexandre Oliva aoliva@redhat.com
544 Denis Pilat denis.pilat@st.com
545 Vladimir Prus vladimir@codesourcery.com
546 Qinwei qinwei@sunnorth.com.cn
547 Ramana Radhakrishnan ramana.radhakrishnan@codito.com
548 Frederic Riss frederic.riss@st.com
549 Tom Rix trix@redhat.com
550 Nick Roberts nickrob@snap.net.nz
551 Bob Rossi bob_rossi@cox.net
552 Theodore A. Roth troth@openavr.org
553 Ian Roxborough irox@redhat.com
554 Maciej W. Rozycki macro@linux-mips.org
555 Grace Sainsbury graces@redhat.com
556 Kei Sakamoto sakamoto.kei@renesas.com
557 Mark Salter msalter@redhat.com
558 Richard Sandiford richard@codesourcery.com
559 Peter Schauer Peter.Schauer@mytum.de
560 Andreas Schwab schwab@suse.de
561 Keith Seitz keiths@redhat.com
562 Carlos Eduardo Seo cseo@linux.vnet.ibm.com
563 Stan Shebs shebs@mozilla.com
564 Mark Shinwell shinwell@codesourcery.com
565 Aidan Skinner aidan@velvet.net
566 Jiri Smid smid@suse.cz
567 David Smith dsmith@redhat.com
568 Stephen P. Smith ischis2@cox.net
569 Jackie Smith Cashion jsmith@redhat.com
570 Michael Snyder msnyder@specifix.com
571 Petr Sorfa petrs@caldera.com
572 Andrew Stubbs andrew.stubbs@st.com
573 Ian Lance Taylor ian@airs.com
574 Gary Thomas gthomas@redhat.com
575 Jason Thorpe thorpej@netbsd.org
576 Caroline Tice ctice@apple.com
577 Tom Tromey tromey@redhat.com
578 David Ung davidu@mips.com
579 D Venkatasubramanian dvenkat@noida.hcltech.com
580 Corinna Vinschen vinschen@redhat.com
581 Keith Walker keith.walker@arm.com
582 Kris Warkentin kewarken@qnx.com
583 Ulrich Weigand uweigand@de.ibm.com
584 Nathan Williams nathanw@wasabisystems.com
585 Bob Wilson bob.wilson@acm.org
586 Jim Wilson wilson@specifix.com
587 Elena Zannoni ezannoni@redhat.com
588 Eli Zaretskii eliz@gnu.org
589 Wu Zhou woodzltc@cn.ibm.com
590 Yoshinori Sato ysato@users.sourceforge.jp
593 Past Maintainers
595 Whenever removing yourself, or someone else, from this file, consider
596 listing their areas of development here for posterity.
598 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
599 Jeff Law (hppa) law at cygnus dot com
600 Daniel Berlin (C++ support) dan at cgsoftware dot com
601 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
602 David Taylor (d10v, sparc, utils, defs,
603 expression evaluator, language support) taylor at candd dot org
604 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
605 Frank Ch. Eigler (sim) fche at redhat dot com
606 Per Bothner (Java) per at bothner dot com
607 Anthony Green (Java) green at redhat dot com
608 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
609 Mark Salter (testsuite/lib+config) msalter at redhat dot com
610 Jim Kingdon (web pages) kingdon at panix dot com
611 Jim Ingham (gdbtk, libgui) jingham at apple dot com
612 Mark Kettenis (hurd native) kettenis at gnu dot org
613 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
614 Robert Lipe (SCO/Unixware) rjl at sco dot com
615 Peter Schauer (global, AIX, xcoffsolib,
616 Solaris/x86) Peter.Schauer at mytum dot de
617 Scott Bambrough (ARM) scottb at netwinder dot org
618 Philippe De Muyter (coff) phdm at macqel dot be
619 Michael Chastain (testsuite) mec.gnu at mindspring dot com
620 Fred Fish (global)
624 Folks that have been caught up in a paper trail:
626 David Carlton carlton@bactrian.org
628 ;; Local Variables:
629 ;; coding: utf-8
630 ;; End: