projects / binutils-gdb.git / blob
? search:
summary | shortlog | log | commit | commitdiff | tree
history | raw | HEAD
* MAINTAINERS: Update Stan Shebs' email address.
[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 For documentation changes, about the only kind of fix that is obvious
99 is correction of a typo or bad English usage.
100
101
102 GDB Steering Committee
103 ----------------------
104
105 The members of the GDB Steering Committee are the FSF-appointed
106 maintainers of the GDB project.
107
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.
112
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.
117
118 Jim Blandy (CodeSourcery)
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
128
129
130 Global Maintainers
131 ------------------
132
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.
138
139 The global maintainers are responsible for reviewing patches to any area
140 for which no Responsible Maintainer is listed.
141
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.
151
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.
155
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.
158
159 The current global maintainers are (in alphabetical order):
160
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 Elena Zannoni ezannoni@redhat.com
170 Eli Zaretskii eliz@gnu.org
171
172
173 Release Manager
174 ---------------
175
176 The current release manager is: Joel Brobecker <brobecker@adacore.com>
177
178 His responsibilities are:
179
180 * organizing, scheduling, and managing releases of GDB.
181
182 * deciding the approval and commit policies for release branches,
183 and can change them as needed.
184
185
186
187 Patch Champions
188 ---------------
189
190 These volunteers track all patches submitted to the gdb-patches list. They
191 endeavor to prevent any posted patch from being overlooked; work with
192 contributors to meet GDB's coding style and general requirements, along with
193 FSF copyright assignments; remind (ping) responsible maintainers to review
194 patches; and ensure that contributors are given credit.
195
196 Current patch champions (in alphabetical order):
197
198 Randolph Chung <tausq@debian.org>
199 Daniel Jacobowitz <dan@debian.org>
200
201
202
203 Responsible Maintainers
204 -----------------------
205
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.
211
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.
224
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).
232
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.
237
238 If there are several maintainers for a given domain then any one of them
239 may review a submitted patch.
240
241 Target Instruction Set Architectures:
242
243 The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
244 (Operating System / Application Binary Interface) issues including CPU
245 variants.
246
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.
250
251 alpha --target=alpha-elf ,-Werror
252
253 arm --target=arm-elf ,-Werror
254 Richard Earnshaw rearnsha@arm.com
255
256 avr --target=avr ,-Werror
257
258 cris --target=cris-elf ,-Werror
259
260 d10v OBSOLETE
261
262 frv --target=frv-elf ,-Werror
263
264 h8300 --target=h8300-elf ,-Werror
265
266 i386 --target=i386-elf ,-Werror
267 Mark Kettenis kettenis@gnu.org
268
269 ia64 --target=ia64-linux-gnu ,-Werror
270 (--target=ia64-elf broken)
271
272 m32c --target=m32c-elf ,-Werror
273 Jim Blandy, jimb@codesourcery.com
274
275 m32r --target=m32r-elf ,-Werror
276
277 m68hc11 --target=m68hc11-elf ,-Werror ,
278 Stephane Carrez stcarrez@nerim.fr
279
280 m68k --target=m68k-elf ,-Werror
281
282 m88k --target=m88k-openbsd ,-Werror
283 Mark Kettenis kettenis@gnu.org
284
285 mcore Deleted
286
287 mips --target=mips-elf ,-Werror
288
289 mn10300 --target=mn10300-elf broken
290 (sim/ dies with make -j)
291 Michael Snyder Michael.Snyder@PalmSource.com
292
293 ms1 --target=ms1-elf ,-Werror
294 Kevin Buettner kevinb@redhat.com
295
296 ns32k Deleted
297
298 pa --target=hppa-elf ,-Werror
299
300 powerpc --target=powerpc-eabi ,-Werror
301
302 s390 --target=s390-linux-gnu ,-Werror
303
304 score --target=score-elf
305 Qinwei qinwei@sunnorth.com.cn
306
307 sh --target=sh-elf ,-Werror
308 --target=sh64-elf ,-Werror
309
310 sparc --target=sparc-elf ,-Werror
311
312 spu --target=spu-elf ,-Werror
313 Ulrich Weigand uweigand@de.ibm.com
314
315 v850 --target=v850-elf ,-Werror
316
317 vax --target=vax-netbsd ,-Werror
318
319 x86-64 --target=x86_64-linux-gnu ,-Werror
320
321 xstormy16 --target=xstormy16-elf
322 Corinna Vinschen vinschen@redhat.com
323
324 xtensa --target=xtensa-elf
325 Maxim Grigoriev maxim2405@gmail.com
326
327 All developers recognized by this file can make arbitrary changes to
328 OBSOLETE targets.
329
330 The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
331 above targets.
332
333
334 Host/Native:
335
336 The Native maintainer is responsible for target specific native
337 support - typically shared libraries and quirks to procfs/ptrace/...
338 The Native maintainer works with the Arch and Core maintainers when
339 resolving more generic problems.
340
341 The host maintainer ensures that gdb can be built as a cross debugger on
342 their platform.
343
344 AIX Joel Brobecker brobecker@adacore.com
345
346 djgpp native Eli Zaretskii eliz@gnu.org
347 GNU Hurd Alfred M. Szmidt ams@gnu.org
348 MS Windows (NT, '00, 9x, Me, XP) host & native
349 Chris Faylor cgf@alum.bu.edu
350 GNU/Linux/x86 native & host
351 Mark Kettenis kettenis@gnu.org
352 GNU/Linux MIPS native & host
353 Daniel Jacobowitz dan@debian.org
354 GNU/Linux m68k Andreas Schwab schwab@suse.de
355 FreeBSD native & host Mark Kettenis kettenis@gnu.org
356
357
358
359 Core: Generic components used by all of GDB
360
361 tracing Michael Snyder Michael.Snyder@PalmSource.com
362 threads Michael Snyder Michael.Snyder@PalmSource.com
363 Mark Kettenis kettenis@gnu.org
364 language support
365 C++ Daniel Jacobowitz dan@debian.org
366 Objective C support Adam Fedor fedor@gnu.org
367 shared libs Kevin Buettner kevinb@redhat.com
368
369 documentation Eli Zaretskii eliz@gnu.org
370 (including NEWS)
371 testsuite
372 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
373 threads (gdb.threads) Michael Snyder Michael.Snyder@PalmSource.com
374 trace (gdb.trace) Michael Snyder Michael.Snyder@PalmSource.com
375
376
377 UI: External (user) interfaces.
378
379 gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
380 Keith Seitz keiths@redhat.com
381 libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
382
383
384 Misc:
385
386 gdb/gdbserver Daniel Jacobowitz dan@debian.org
387
388 Makefile.in, configure* ALL
389
390 mmalloc/ ALL Host maintainers
391
392 sim/ See sim/MAINTAINERS
393
394 readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
395 ALL
396 Host maintainers (host dependant parts)
397 (but get your changes into the master version)
398
399 tcl/ tk/ itcl/ ALL
400
401
402 Authorized Committers
403 ---------------------
404
405 These are developers working on particular areas of GDB, who are trusted to
406 commit their own (or other developers') patches in those areas without
407 further review from a Global Maintainer or Responsible Maintainer. They are
408 under no obligation to review posted patches - but, of course, are invited
409 to do so!
410
411 PowerPC Andrew Cagney cagney@gnu.org
412 CRIS Hans-Peter Nilsson hp@bitrange.com
413 IA64 Jeff Johnston jjohnstn@redhat.com
414 MIPS Joel Brobecker brobecker@adacore.com
415 m32r Kei Sakamoto sakamoto.kei@renesas.com
416 PowerPC Kevin Buettner kevinb@redhat.com
417 CRIS Orjan Friberg orjanf@axis.com
418 HPPA Randolph Chung tausq@debian.org
419 S390 Ulrich Weigand uweigand@de.ibm.com
420 djgpp DJ Delorie dj@delorie.com
421 [Please use this address to contact DJ about DJGPP]
422 tui Stephane Carrez stcarrez@nerim.fr
423 ia64 Kevin Buettner kevinb@redhat.com
424 AIX Kevin Buettner kevinb@redhat.com
425 GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
426 gdb.java tests Anthony Green green@redhat.com
427 FreeBSD native & host David O'Brien obrien@freebsd.org
428 event loop Elena Zannoni ezannoni@redhat.com
429 generic symtabs Elena Zannoni ezannoni@redhat.com
430 dwarf readers Elena Zannoni ezannoni@redhat.com
431 elf reader Elena Zannoni ezannoni@redhat.com
432 stabs reader Elena Zannoni ezannoni@redhat.com
433 readline/ Elena Zannoni ezannoni@redhat.com
434 NetBSD native & host Jason Thorpe thorpej@netbsd.org
435 Pascal support Pierre Muller muller@sources.redhat.com
436 avr Theodore A. Roth troth@openavr.org
437 Modula-2 support Gaius Mulley gaius@glam.ac.uk
438
439
440 Write After Approval
441 (alphabetic)
442
443 To get recommended for the Write After Approval list you need a valid
444 FSF assignment and have submitted one good patch.
445
446 David Anderson davea@sgi.com
447 John David Anglin dave.anglin@nrc-cnrc.gc.ca
448 Shrinivas Atre shrinivasa@kpitcummins.com
449 Scott Bambrough scottb@netwinder.org
450 Jan Beulich jbeulich@novell.com
451 Jim Blandy jimb@codesourcery.com
452 Philip Blundell philb@gnu.org
453 Per Bothner per@bothner.com
454 Joel Brobecker brobecker@adacore.com
455 Dave Brolley brolley@redhat.com
456 Paul Brook paul@codesourcery.com
457 Julian Brown julian@codesourcery.com
458 Kevin Buettner kevinb@redhat.com
459 Andrew Cagney cagney@gnu.org
460 David Carlton carlton@bactrian.org
461 Stephane Carrez stcarrez@nerim.fr
462 Michael Chastain mec.gnu@mindspring.com
463 Eric Christopher echristo@apple.com
464 Randolph Chung tausq@debian.org
465 Nick Clifton nickc@redhat.com
466 J.T. Conklin jtc@acorntoolworks.com
467 Brendan Conoboy blc@redhat.com
468 DJ Delorie dj@redhat.com
469 Philippe De Muyter phdm@macqel.be
470 Dhananjay Deshpande dhananjayd@kpitcummins.com
471 Klee Dienes kdienes@apple.com
472 Richard Earnshaw rearnsha@arm.com
473 Steve Ellcey sje@cup.hp.com
474 Frank Ch. Eigler fche@redhat.com
475 Ben Elliston bje@gnu.org
476 Adam Fedor fedor@gnu.org
477 Fred Fish fnf@ninemoons.com
478 Brian Ford ford@vss.fsi.com
479 Orjan Friberg orjanf@axis.com
480 Gary Funck gary@intrepid.com
481 Paul Gilliam pgilliam@us.ibm.com
482 Raoul Gough RaoulGough@yahoo.co.uk
483 Anthony Green green@redhat.com
484 Matthew Green mrg@eterna.com.au
485 Maxim Grigoriev maxim2405@gmail.com
486 Jerome Guitton guitton@act-europe.fr
487 Ben Harris bjh21@netbsd.org
488 Richard Henderson rth@redhat.com
489 Aldy Hernandez aldyh@redhat.com
490 Paul Hilfinger hilfinger@gnat.com
491 Matt Hiller hiller@redhat.com
492 Kazu Hirata kazu@cs.umass.edu
493 Jeff Holcomb jeffh@redhat.com
494 Don Howard dhoward@redhat.com
495 Martin Hunt hunt@redhat.com
496 Jim Ingham jingham@apple.com
497 Baurzhan Ismagulov ibr@radix50.net
498 Manoj Iyer manjo@austin.ibm.com
499 Daniel Jacobowitz dan@debian.org
500 Andreas Jaeger aj@suse.de
501 Jeff Johnston jjohnstn@redhat.com
502 Geoff Keating geoffk@redhat.com
503 Mark Kettenis kettenis@gnu.org
504 Jim Kingdon kingdon@panix.com
505 Jonathan Larmour jlarmour@redhat.co.uk
506 Jeff Law law@redhat.com
507 David Lecomber david@streamline-computing.com
508 Robert Lipe rjl@sco.com
509 H.J. Lu hjl@lucon.org
510 Michal Ludvig mludvig@suse.cz
511 Glen McCready gkm@redhat.com
512 Greg McGary greg@mcgary.org
513 Roland McGrath roland@redhat.com
514 Bryce McKinlay mckinlay@redhat.com
515 Jason Merrill jason@redhat.com
516 David S. Miller davem@redhat.com
517 Mark Mitchell mark@codesourcery.com
518 Marko Mlinar markom@opencores.org
519 Alan Modra amodra@bigpond.net.au
520 Jason Molenda jmolenda@apple.com
521 Pierre Muller muller@sources.redhat.com
522 Gaius Mulley gaius@glam.ac.uk
523 Joseph Myers joseph@codesourcery.com
524 Fernando Nasser fnasser@redhat.com
525 Adam Nemet anemet@caviumnetworks.com
526 Nathanael Nerode neroden@gcc.gnu.org
527 Hans-Peter Nilsson hp@bitrange.com
528 David O'Brien obrien@freebsd.org
529 Alexandre Oliva aoliva@redhat.com
530 Vladimir Prus vladimir@codesourcery.com
531 Qinwei qinwei@sunnorth.com.cn
532 Ramana Radhakrishnan ramana.radhakrishnan@codito.com
533 Frederic Riss frederic.riss@st.com
534 Tom Rix trix@redhat.com
535 Nick Roberts nickrob@snap.net.nz
536 Bob Rossi bob_rossi@cox.net
537 Theodore A. Roth troth@openavr.org
538 Ian Roxborough irox@redhat.com
539 Grace Sainsbury graces@redhat.com
540 Kei Sakamoto sakamoto.kei@renesas.com
541 Mark Salter msalter@redhat.com
542 Richard Sandiford richard@codesourcery.com
543 Peter Schauer Peter.Schauer@mytum.de
544 Andreas Schwab schwab@suse.de
545 Keith Seitz keiths@redhat.com
546 Stan Shebs shebs@mozilla.com
547 Aidan Skinner aidan@velvet.net
548 Jiri Smid smid@suse.cz
549 David Smith dsmith@redhat.com
550 Stephen P. Smith ischis2@cox.net
551 Jackie Smith Cashion jsmith@redhat.com
552 Michael Snyder Michael.Snyder@PalmSource.com
553 Petr Sorfa petrs@caldera.com
554 Andrew Stubbs andrew.stubbs@st.com
555 Ian Lance Taylor ian@airs.com
556 Gary Thomas gthomas@redhat.com
557 Jason Thorpe thorpej@netbsd.org
558 Tom Tromey tromey@redhat.com
559 David Ung davidu@mips.com
560 D Venkatasubramanian dvenkat@noida.hcltech.com
561 Corinna Vinschen vinschen@redhat.com
562 Keith Walker keith.walker@arm.com
563 Kris Warkentin kewarken@qnx.com
564 Ulrich Weigand uweigand@de.ibm.com
565 Nathan Williams nathanw@wasabisystems.com
566 Bob Wilson bob.wilson@acm.org
567 Jim Wilson wilson@specifixinc.com
568 Elena Zannoni ezannoni@redhat.com
569 Eli Zaretskii eliz@gnu.org
570 Wu Zhou woodzltc@cn.ibm.com
571 Yoshinori Sato ysato@users.sourceforge.jp
572
573
574 Past Maintainers
575
576 Whenever removing yourself, or someone else, from this file, consider
577 listing their areas of development here for posterity.
578
579 Jimmy Guo (gdb.hp, tui) guo at cup dot hp dot com
580 Jeff Law (hppa) law at cygnus dot com
581 Daniel Berlin (C++ support) dan at cgsoftware dot com
582 Nick Duffek (powerpc, SCO, Sol/x86) nick at duffek dot com
583 David Taylor (d10v, sparc, utils, defs,
584 expression evaluator, language support) taylor at candd dot org
585 J.T. Conklin (dcache, NetBSD, remote, global) jtc at acorntoolworks dot com
586 Frank Ch. Eigler (sim) fche at redhat dot com
587 Per Bothner (Java) per at bothner dot com
588 Anthony Green (Java) green at redhat dot com
589 Fernando Nasser (testsuite/, mi, cli, KOD) fnasser at redhat dot com
590 Mark Salter (testsuite/lib+config) msalter at redhat dot com
591 Jim Kingdon (web pages) kingdon at panix dot com
592 Jim Ingham (gdbtk, libgui) jingham at apple dot com
593 Mark Kettenis (hurd native) kettenis at gnu dot org
594 Ian Roxborough (in-tree tcl, tk, itcl) irox at redhat dot com
595 Robert Lipe (SCO/Unixware) rjl at sco dot com
596 Peter Schauer (global, AIX, xcoffsolib,
597 Solaris/x86) Peter.Schauer at mytum dot de
598 Scott Bambrough (ARM) scottb at netwinder dot org
599 Philippe De Muyter (coff) phdm at macqel dot be
600 Michael Chastain (testsuite) mec.gnu at mindspring dot com
601
602
603
604 Folks that have been caught up in a paper trail:
605
606 David Carlton carlton@bactrian.org