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