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