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