cdf29d9464e390909d436867b28393997921b8f0
[deliverable/binutils-gdb.git] / gdb / MAINTAINERS
1 GDB Maintainers
2 ===============
3
4
5 Overview
6 --------
7
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.
11
12 There are four groups of GDB developers, covering the patch development and
13 review process:
14
15 - The Global Maintainers.
16
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.
21
22 - The Responsible Maintainers.
23
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.
27
28 - The Authorized Committers.
29
30 These are developers who are trusted to make changes within a specific
31 area of GDB without additional oversight.
32
33 - The Write After Approval Maintainers.
34
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).
39
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).
45
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!
54
55 There's also a couple of other people who play special roles in the GDB
56 community, separately from the patch process:
57
58 - The GDB Steering Committee.
59
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).
65
66 - The Release Manager.
67
68 This developer is in charge of making new releases of GDB.
69
70 - The Patch Champions.
71
72 These volunteers make sure that no contribution is overlooked or
73 forgotten.
74
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.
79
80
81 The Obvious Fix Rule
82 --------------------
83
84 All maintainers listed in this file, including the Write After Approval
85 developers, are allowed to check in obvious fixes.
86
87 An "obvious fix" means that there is no possibility that anyone will
88 disagree with the change.
89
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. :-)
93
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.
97
98
99 GDB Steering Committee
100 ----------------------
101
102 The members of the GDB Steering Committee are the FSF-appointed
103 maintainers of the GDB project.
104
105 The Steering Committee has final authority for all GDB-related topics;
106 they may make whatever changes that they deem necessary, or that the FSF
107 requests. However, they are generally not involved in day-to-day
108 development.
109
110 The current members of the steering committee are listed below, in
111 alphabetical order. Their affiliations are provided for reference only -
112 their membership on the Steering Committee is individual and not through
113 their affiliation, and they act on behalf of the GNU project.
114
115 Jim Blandy (Red Hat)
116 Andrew Cagney (Red Hat)
117 Robert Dewar (AdaCore, NYU)
118 Klee Dienes (Apple)
119 Paul Hilfinger (UC Berkeley)
120 Dan Jacobowitz (CodeSourcery)
121 Stan Shebs (Apple)
122 Richard Stallman (FSF)
123 Ian Lance Taylor (C2)
124 Todd Whitesel
125
126
127 Global Maintainers
128 ------------------
129
130 The global maintainers may review and commit any change to GDB, except in
131 areas with a Responsible Maintainer available. For major changes, or
132 changes to areas with other active developers, global maintainers are
133 strongly encouraged to post their own patches for feedback before
134 committing.
135
136 The global maintainers are responsible for reviewing patches to any area
137 for which no Responsible Maintainer is listed.
138
139 Global maintainers also have the authority to revert patches which should
140 not have been applied, e.g. patches which were not approved, controversial
141 patches committed under the Obvious Fix Rule, patches with important bugs
142 that can't be immediately fixed, or patches which go against an accepted and
143 documented roadmap for GDB development. Any global maintainer may request
144 the reversion of a patch. If no global maintainer, or responsible
145 maintainer in the affected areas, supports the patch (except for the
146 maintainer who originally committed it), then after 48 hours the maintainer
147 who called for the reversion may revert the patch.
148
149 No one may reapply a reverted patch without the agreement of the maintainer
150 who reverted it, or bringing the issue to the GDB Steering Committee for
151 discussion.
152
153 At the moment there are no documented roadmaps for GDB development; in the
154 future, if there are, a reference to the list will be included here.
155
156 The current global maintainers are (in alphabetical order):
157
158 Jim Blandy jimb@redhat.com
159 Kevin Buettner kevinb@redhat.com
160 Andrew Cagney cagney@gnu.org
161 J.T. Conklin jtc@acorntoolworks.com
162 Fred Fish fnf@ninemoons.com
163 Daniel Jacobowitz dan@debian.org
164 Mark Kettenis kettenis@gnu.org
165 Peter Schauer Peter.Schauer@regent.e-technik.tu-muenchen.de
166 Stan Shebs shebs@apple.com
167 Michael Snyder msnyder@redhat.com
168 Elena Zannoni ezannoni@redhat.com
169 Eli Zaretskii eliz@gnu.org
170
171
172 Release Manager
173 ---------------
174
175 The current release manager is: Joel Brobecker <brobecker@adacore.com>
176
177 His responsibilities are:
178
179 * organizing, scheduling, and managing releases of GDB.
180
181 * deciding the approval and commit policies for release branches,
182 and can change them as needed.
183
184
185
186 Patch Champions
187 ---------------
188
189 These volunteers track all patches submitted to the gdb-patches list. They
190 endeavor to prevent any posted patch from being overlooked; work with
191 contributors to meet GDB's coding style and general requirements, along with
192 FSF copyright assignments; remind (ping) responsible maintainers to review
193 patches; and ensure that contributors are given credit.
194
195 Current patch champions (in alphabetical order):
196
197 Joel Brobecker <brobecker@adacore.com>
198 Daniel Jacobowitz <dan@debian.org>
199
200
201
202 Responsible Maintainers
203 -----------------------
204
205 These developers have agreed to review patches in specific areas of GDB, in
206 which they have knowledge and experience. These areas are generally broad;
207 the role of a responsible maintainer is to provide coherent and cohesive
208 structure within their area of GDB, to assure that patches from many
209 different contributors all work together for the best results.
210
211 Global maintainers will defer to responsible maintainers within their areas,
212 as long as the responsible maintainer is active. Active means that
213 responsible maintainers agree to review submitted patches in their area
214 promptly; patches and followups should generally be answered within a week.
215 If a responsible maintainer is interested in reviewing a patch but will not
216 have time within a week of posting, the maintainer should send an
217 acknowledgement of the patch to the gdb-patches mailing list, and
218 plan to follow up with a review within a month. These deadlines are for
219 initial responses to a patch - if the maintainer has suggestions
220 or questions, it may take an extended discussion before the patch
221 is ready to commit. There are no written requirements for discussion,
222 but maintainers are asked to be responsive.
223
224 If a responsible maintainer misses these deadlines occasionally (e.g.
225 vacation or unexpected workload), it's not a disaster - any global
226 maintainer may step in to review the patch. But sometimes life intervenes
227 more permanently, and a maintainer may no longer have time for these duties.
228 When this happens, he or she should step down (either into the Authorized
229 Committers section if still interested in the area, or simply removed from
230 the list of Responsible Maintainers if not).
231
232 If a responsible maintainer is unresponsive for an extended period of time
233 without stepping down, please contact the Global Maintainers; they will try
234 to contact the maintainer directly and fix the problem - potentially by
235 removing that maintainer from their listed position.
236
237 If there are several maintainers for a given domain then any one of them
238 may review a submitted patch.
239
240 Target Instruction Set Architectures:
241
242 The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
243 (Operating System / Application Binary Interface) issues including CPU
244 variants.
245
246 The Target/Architecture maintainer works with the host maintainer when
247 resolving build issues. The Target/Architecture maintainer works with
248 the native maintainer when resolving ABI issues.
249
250 alpha --target=alpha-elf ,-Werror
251
252 arm --target=arm-elf ,-Werror
253 Scott Bambrough scottb@netwinder.org
254 Richard Earnshaw rearnsha@arm.com
255
256 avr --target=avr ,-Werror
257 Theodore A. Roth troth@openavr.org
258
259 cris --target=cris-elf ,-Werror
260
261 d10v OBSOLETE
262
263 frv --target=frv-elf ,-Werror
264
265 h8300 --target=h8300-elf ,-Werror
266
267 i386 --target=i386-elf ,-Werror
268 Mark Kettenis kettenis@gnu.org
269
270 ia64 --target=ia64-linux-gnu ,-Werror
271 (--target=ia64-elf broken)
272 Kevin Buettner kevinb@redhat.com
273
274 m32r --target=m32r-elf ,-Werror
275
276 m68hc11 --target=m68hc11-elf ,-Werror ,
277 Stephane Carrez stcarrez@nerim.fr
278
279 m68k --target=m68k-elf ,-Werror
280
281 m88k --target=m88k-openbsd ,-Werror
282 Mark Kettenis kettenis@gnu.org
283
284 mcore Deleted
285
286 mips --target=mips-elf ,-Werror
287
288 mn10300 --target=mn10300-elf broken
289 (sim/ dies with make -j)
290 Michael Snyder msnyder@redhat.com
291
292 ms1 --target=ms1-elf ,-Werror
293 Kevin Buettner kevinb@redhat.com
294
295 ns32k Deleted
296
297 pa --target=hppa-elf ,-Werror
298
299 powerpc --target=powerpc-eabi ,-Werror
300
301 s390 --target=s390-linux-gnu ,-Werror
302
303 sh --target=sh-elf ,-Werror
304 --target=sh64-elf ,-Werror
305
306 sparc --target=sparc-elf ,-Werror
307
308 v850 --target=v850-elf ,-Werror
309
310 vax --target=vax-netbsd ,-Werror
311
312 x86-64 --target=x86_64-linux-gnu ,-Werror
313
314 xstormy16 --target=xstormy16-elf
315 Corinna Vinschen vinschen@redhat.com
316
317 All developers recognized by this file can make arbitrary changes to
318 OBSOLETE targets.
319
320 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
321 above targets.
322
323
324 Host/Native:
325
326 The Native maintainer is responsible for target specific native
327 support - typically shared libraries and quirks to procfs/ptrace/...
328 The Native maintainer works with the Arch and Core maintainers when
329 resolving more generic problems.
330
331 The host maintainer ensures that gdb can be built as a cross debugger on
332 their platform.
333
334 AIX Peter Schauer Peter.Schauer@regent.e-technik.tu-muenchen.de
335 Kevin Buettner kevinb@redhat.com
336 Joel Brobecker brobecker@gnat.com
337
338 djgpp native Eli Zaretskii eliz@gnu.org
339 DJ Delorie dj@redhat.com
340 MS Windows (NT, '00, 9x, Me, XP) host & native
341 Chris Faylor cgf@alum.bu.edu
342 GNU/Linux/x86 native & host
343 Mark Kettenis kettenis@gnu.org
344 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
345 GNU/Linux MIPS native & host
346 Daniel Jacobowitz dan@debian.org
347 GNU/Linux m68k Andreas Schwab schwab@suse.de
348 FreeBSD native & host Mark Kettenis kettenis@gnu.org
349 David O'Brien obrien@freebsd.org
350 hurd native Mark Kettenis kettenis@gnu.org
351 NetBSD native & host Jason Thorpe thorpej@netbsd.org
352 SCO/Unixware Robert Lipe rjl@sco.com
353 GNU/Linux ARM native Scott Bambrough scottb@netwinder.org
354 Solaris/x86 native & host (devolved)
355 Peter Schauer Peter.Schauer@regent.e-technik.tu-muenchen.de
356 Solaris/SPARC native & host (devolved)
357 (Global Maintainers)
358
359
360
361 Core: Generic components used by all of GDB
362
363 generic arch support (Global Maintainers)
364 Any host/target maintainer can add to
365 gdbarch.{c,h,sh}.
366 target vector (Global Maintainers)
367
368 event loop Elena Zannoni ezannoni@redhat.com
369 For the part of top.c related to the event loop,
370 send questions to ezannoni@redhat.com
371
372 generic symtabs Elena Zannoni ezannoni@redhat.com
373 dwarf readers Elena Zannoni ezannoni@redhat.com
374 elf reader Elena Zannoni ezannoni@redhat.com
375 stabs reader Elena Zannoni ezannoni@redhat.com
376 coff reader Philippe De Muyter phdm@macqel.be
377 xcoff reader Any maintainer can modify this; please send tricky
378 ones to Kevin Buettner <kevinb@redhat.com>
379 HP/UX readers Any [past] maintainer can modify this.
380 Please send tricky ones to the symtabs maintainers.
381
382 tracing bytecode stuff (Global Maintainers)
383 tracing Michael Snyder msnyder@redhat.com
384 threads Michael Snyder msnyder@redhat.com
385 Mark Kettenis kettenis@gnu.org
386 breakpoints (Global Maintainers)
387 language support (Blanket Write Privs Maintainers)
388 C++ Daniel Jacobowitz dan@debian.org
389 Java support (Global Maintainers)
390 Pascal support Pierre Muller muller@sources.redhat.com
391 Objective C support Adam Fedor fedor@gnu.org
392 shared libs (devolved) Kevin Buettner kevinb@redhat.com
393 xcoffsolib Peter Schauer Peter.Schauer@regent.e-technik.tu-muenchen.de
394
395 sds protocol (vacant)
396 rdi/adp protocol (vacant)
397 documentation Eli Zaretskii eliz@gnu.org
398 testsuite Michael Chastain mec.gnu@mindspring.com
399 (Global Maintainers)
400 lib/, config/, gdb.base/, ...
401 Michael Chastain mec.gnu@mindspring.com
402 (Global Maintainers)
403 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
404 c++ (gdb.cp) Michael Chastain mec.gnu@mindspring.com
405 threads (gdb.threads) Michael Snyder msnyder@redhat.com
406 Michael Chastain mec.gnu@mindspring.com
407 trace (gdb.trace) Michael Snyder msnyder@redhat.com
408 hp tests (gdb.hp) (vacant)
409 Java tests (gdb.java) Anthony Green green@redhat.com
410 Kernel Object Display Fernando Nasser fnasser@redhat.com
411
412
413 UI: External (user) interfaces.
414
415 command interpreter (Global Maintainers)
416 gdbtk (c & tcl) Jim Ingham jingham@apple.com
417 Fernando Nasser fnasser@redhat.com
418 Keith Seitz keiths@redhat.com
419 libgui (w/foundry, sn) Jim Ingham jingham@apple.com
420 Keith Seitz keiths@redhat.com
421 tui Stephane Carrez stcarrez@nerim.fr
422 (Global Maintainers)
423
424
425 Misc:
426
427 gdb/gdbserver Daniel Jacobowitz dan@debian.org
428
429 Web pages. Jim Kingdon jkingdon@engr.sgi.com ++
430 (anyone can edit; kingdon is just lead maintainer)
431
432 Makefile.in, configure* ALL
433
434 mmalloc/ ALL Host maintainers
435
436 NEWS ALL
437
438 sim/ See sim/MAINTAINERS
439
440 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
441 Elena Zannoni ezannoni@redhat.com
442 Host maintainers (host dependant parts)
443 (but get your changes into the master version)
444
445 tcl/ tk/ itcl/ Ian Roxborough irox@redhat.com
446
447
448 Authorized Committers
449 ---------------------
450
451 These are developers working on particular areas of GDB, who are trusted to
452 commit their own (or other developers') patches in those areas without
453 further review from a Global Maintainer or Responsible Maintainer. They are
454 under no obligation to review posted patches - but, of course, are invited
455 to do so!
456
457 Andrew Cagney (powerpc, powerpc-linux)
458 Hans-Peter Nilsson (cris)
459 Jeff Johnston (ia64)
460 Joel Brobecker (mips)
461 Kei Sakamoto (m32r)
462 Kevin Buettner (powerpc)
463 Orjan Friberg (cris)
464 Randolph Chung (pa)
465 Ulrich Weigand (s390)
466
467
468 Write After Approval
469 (alphabetic)
470
471 To get recommended for the Write After Approval list you need a valid
472 FSF assignment and have submitted one good patch.
473
474 David Anderson davea@sgi.com
475 John David Anglin dave.anglin@nrc-cnrc.gc.ca
476 Shrinivas Atre shrinivasa@kpitcummins.com
477 Scott Bambrough scottb@netwinder.org
478 Jan Beulich jbeulich@novell.com
479 Jim Blandy jimb@redhat.com
480 Philip Blundell philb@gnu.org
481 Per Bothner per@bothner.com
482 Joel Brobecker brobecker@gnat.com
483 Dave Brolley brolley@redhat.com
484 Paul Brook paul@codesourcery.com
485 Kevin Buettner kevinb@redhat.com
486 Andrew Cagney cagney@gnu.org
487 David Carlton carlton@bactrian.org
488 Stephane Carrez stcarrez@nerim.fr
489 Michael Chastain mec.gnu@mindspring.com
490 Eric Christopher echristo@apple.com
491 Randolph Chung tausq@debian.org
492 Nick Clifton nickc@redhat.com
493 Brendan Conoboy blc@redhat.com
494 DJ Delorie dj@redhat.com
495 Philippe De Muyter phdm@macqel.be
496 Dhananjay Deshpande dhananjayd@kpitcummins.com
497 Klee Dienes kdienes@apple.com
498 Richard Earnshaw rearnsha@arm.com
499 Steve Ellcey sje@cup.hp.com
500 Frank Ch. Eigler fche@redhat.com
501 Ben Elliston bje@gnu.org
502 Adam Fedor fedor@gnu.org
503 Fred Fish fnf@ninemoons.com
504 Brian Ford ford@vss.fsi.com
505 Orjan Friberg orjanf@axis.com
506 Paul Gilliam pgilliam@us.ibm.com
507 Raoul Gough RaoulGough@yahoo.co.uk
508 Anthony Green green@redhat.com
509 Matthew Green mrg@eterna.com.au
510 Jerome Guitton guitton@act-europe.fr
511 Ben Harris bjh21@netbsd.org
512 Richard Henderson rth@redhat.com
513 Aldy Hernandez aldyh@redhat.com
514 Paul Hilfinger hilfinger@gnat.com
515 Matt Hiller hiller@redhat.com
516 Kazu Hirata kazu@cs.umass.edu
517 Jeff Holcomb jeffh@redhat.com
518 Don Howard dhoward@redhat.com
519 Martin Hunt hunt@redhat.com
520 Jim Ingham jingham@apple.com
521 Baurzhan Ismagulov ibr@radix50.net
522 Manoj Iyer manjo@austin.ibm.com
523 Daniel Jacobowitz dan@debian.org
524 Andreas Jaeger aj@suse.de
525 Jeff Johnston jjohnstn@redhat.com
526 Geoff Keating geoffk@redhat.com
527 Mark Kettenis kettenis@gnu.org
528 Jim Kingdon jkingdon@engr.sgi.com ++
529 Jonathan Larmour jlarmour@redhat.co.uk
530 Jeff Law law@redhat.com
531 David Lecomber david@streamline-computing.com
532 Robert Lipe rjl@sco.com
533 H.J. Lu hjl@lucon.org
534 Michal Ludvig mludvig@suse.cz
535 Glen McCready gkm@redhat.com
536 Greg McGary greg@mcgary.org
537 Roland McGrath roland@redhat.com
538 Bryce McKinlay mckinlay@redhat.com
539 Jason Merrill jason@redhat.com
540 David S. Miller davem@redhat.com
541 Mark Mitchell mark@codesourcery.com
542 Marko Mlinar markom@opencores.org
543 Alan Modra amodra@bigpond.net.au
544 Jason Molenda jmolenda@apple.com
545 Pierre Muller muller@sources.redhat.com
546 Joseph Myers joseph@codesourcery.com
547 Fernando Nasser fnasser@redhat.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 Ramana Radhakrishnan ramana.radhakrishnan@codito.com
553 Frederic Riss frederic.riss@st.com
554 Tom Rix trix@redhat.com
555 Nick Roberts nickrob@snap.net.nz
556 Bob Rossi bob_rossi@cox.net
557 Theodore A. Roth troth@openavr.org
558 Ian Roxborough irox@redhat.com
559 Grace Sainsbury graces@redhat.com
560 Kei Sakamoto sakamoto.kei@renesas.com
561 Mark Salter msalter@redhat.com
562 Richard Sandiford richard@codesourcery.com
563 Peter Schauer Peter.Schauer@regent
564 Andreas Schwab schwab@suse.de
565 Keith Seitz keiths@redhat.com
566 Stan Shebs shebs@apple.com
567 Aidan Skinner aidan@velvet.net
568 Jiri Smid smid@suse.cz
569 David Smith dsmith@redhat.com
570 Stephen P. Smith ischis2@cox.net
571 Jackie Smith Cashion jsmith@redhat.com
572 Michael Snyder msnyder@redhat.com
573 Petr Sorfa petrs@caldera.com
574 Andrew Stubbs andrew.stubbs@st.com
575 Ian Lance Taylor ian@airs.com
576 Gary Thomas gthomas@redhat.com
577 Jason Thorpe thorpej@netbsd.org
578 Tom Tromey tromey@redhat.com
579 David Ung davidu@mips.com
580 D Venkatasubramanian dvenkat@noida.hcltech.com
581 Corinna Vinschen vinschen@redhat.com
582 Keith Walker keith.walker@arm.com
583 Kris Warkentin kewarken@qnx.com
584 Ulrich Weigand uweigand@de.ibm.com
585 Nathan Williams nathanw@wasabisystems.com
586 Jim Wilson wilson@specifixinc.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
591
592
593 Past Maintainers
594
595 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
596 Jeff Law (hppa) law at cygnus dot com
597 Daniel Berlin (C++ support) dan at cgsoftware dot com
598 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
599 David Taylor (d10v, sparc, utils, defs,
600 expression evaluator, language support) taylor at candd dot org
601 J.T. Conklin (dcache, NetBSD, remote) jtc at redback dot com
602 Frank Ch. Eigler (sim) fche at redhat dot com
603 Per Bothner (Java) per at bothner dot com
604 Anthony Green (Java) green at redhat dot com
605 Fernando Nasser (testsuite/, mi, cli) fnasser at redhat dot com
606 Mark Salter (testsuite/lib+config) msalter at redhat dot com
607
608
609
610 Folks that have been caught up in a paper trail:
611
612 Jim Kingdon jkingdon@engr.sgi.com
613 David Carlton carlton@bactrian.org
This page took 0.101445 seconds and 4 git commands to generate.