*** empty log message ***
[deliverable/binutils-gdb.git] / gdb / MAINTAINERS
CommitLineData
e990a46e 1 GDB Maintainers
b2a74f99
DJ
2 ===============
3
4
5 Overview
6 --------
7
8This file describes different groups of people who are, together, the
9maintainers and developers of the GDB project. Don't worry - it sounds
10more complicated than it really is.
11
12There are four groups of GDB developers, covering the patch development and
13review 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
40All maintainers are encouraged to post major patches to the gdb-patches
41mailing list for comments, even if they have the authority to commit the
42patch without review from another maintainer. This especially includes
43patches which change internal interfaces (e.g. global functions, data
44structures) or external interfaces (e.g. user, remote, MI, et cetera).
45
46The term "review" is used in this file to describe several kinds of feedback
47from a maintainer: approval, rejection, and requests for changes or
48clarification with the intention of approving a revised version. Review is
49a privilege and/or responsibility of various positions among the GDB
50Maintainers. Of course, anyone - whether they hold a position but not the
51relevant one for a particular patch, or are just following along on the
52mailing lists for fun, or anything in between - may suggest changes or
53ask questions about a patch!
54
55There's also a couple of other people who play special roles in the GDB
56community, 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
75Most changes to the list of maintainers in this file are handled by
76consensus among the global maintainers and any other involved parties.
77In cases where consensus can not be reached, the global maintainers may
78ask the Steering Committee for a final decision.
79
80
81 The Obvious Fix Rule
82 --------------------
83
84All maintainers listed in this file, including the Write After Approval
85developers, are allowed to check in obvious fixes.
86
87An "obvious fix" means that there is no possibility that anyone will
88disagree with the change.
89
90A good mental test is "will the person who hates my work the most be
91able to find fault with the change" - if so, then it's not obvious and
92needs to be posted first. :-)
93
94Something like changing or bypassing an interface is _not_ an obvious
95fix, since such a change without discussion will result in
96instantaneous and loud complaints.
97
81e0e940
EZ
98For documentation changes, about the only kind of fix that is obvious
99is correction of a typo or bad English usage.
100
e990a46e
AC
101
102 GDB Steering Committee
b2a74f99 103 ----------------------
e990a46e
AC
104
105The members of the GDB Steering Committee are the FSF-appointed
106maintainers of the GDB project.
107
b2a74f99
DJ
108The Steering Committee has final authority for all GDB-related topics;
109they may make whatever changes that they deem necessary, or that the FSF
110requests. However, they are generally not involved in day-to-day
111development.
112
113The current members of the steering committee are listed below, in
114alphabetical order. Their affiliations are provided for reference only -
115their membership on the Steering Committee is individual and not through
116their affiliation, and they act on behalf of the GNU project.
117
5eeba8d4 118 Jim Blandy (Mozilla)
e990a46e
AC
119 Andrew Cagney (Red Hat)
120 Robert Dewar (AdaCore, NYU)
121 Klee Dienes (Apple)
122 Paul Hilfinger (UC Berkeley)
123 Dan Jacobowitz (CodeSourcery)
336de56d 124 Stan Shebs (CodeSourcery)
e990a46e
AC
125 Richard Stallman (FSF)
126 Ian Lance Taylor (C2)
127 Todd Whitesel
ef7b4488 128
5185fdd7 129
b2a74f99
DJ
130 Global Maintainers
131 ------------------
132
133The global maintainers may review and commit any change to GDB, except in
134areas with a Responsible Maintainer available. For major changes, or
135changes to areas with other active developers, global maintainers are
136strongly encouraged to post their own patches for feedback before
137committing.
138
139The global maintainers are responsible for reviewing patches to any area
140for which no Responsible Maintainer is listed.
141
142Global maintainers also have the authority to revert patches which should
143not have been applied, e.g. patches which were not approved, controversial
144patches committed under the Obvious Fix Rule, patches with important bugs
145that can't be immediately fixed, or patches which go against an accepted and
146documented roadmap for GDB development. Any global maintainer may request
147the reversion of a patch. If no global maintainer, or responsible
148maintainer in the affected areas, supports the patch (except for the
149maintainer who originally committed it), then after 48 hours the maintainer
150who called for the reversion may revert the patch.
151
152No one may reapply a reverted patch without the agreement of the maintainer
153who reverted it, or bringing the issue to the GDB Steering Committee for
154discussion.
155
156At the moment there are no documented roadmaps for GDB development; in the
157future, if there are, a reference to the list will be included here.
158
159The current global maintainers are (in alphabetical order):
5185fdd7 160
3cd9d164 161Pedro Alves pedro@codesourcery.com
a367a1f2 162Jim Blandy jimb@red-bean.com
e933291e 163Joel Brobecker brobecker@adacore.com
904507ce 164Kevin Buettner kevinb@redhat.com
1db2a798 165Andrew Cagney cagney@gnu.org
bf0d7e9c 166Doug Evans dje@google.com
322be962 167Daniel Jacobowitz dan@codesourcery.com
1b57acd2 168Mark Kettenis kettenis@gnu.org
336de56d 169Stan Shebs stan@codesourcery.com
11fa8e43 170Michael Snyder msnyder@vmware.com
d7dc3873 171Tom Tromey tromey@redhat.com
03f597d5 172Ulrich Weigand Ulrich.Weigand@de.ibm.com
692263b8 173Elena Zannoni elena.zannoni@oracle.com
904507ce 174Eli Zaretskii eliz@gnu.org
5185fdd7 175
f5bca8e7 176
b2a74f99
DJ
177 Release Manager
178 ---------------
5185fdd7 179
b2a74f99 180The current release manager is: Joel Brobecker <brobecker@adacore.com>
5185fdd7 181
b2a74f99 182His responsibilities are:
36c2118f 183
b2a74f99 184 * organizing, scheduling, and managing releases of GDB.
538aae9d 185
b2a74f99
DJ
186 * deciding the approval and commit policies for release branches,
187 and can change them as needed.
5185fdd7 188
58cfabe6 189
58cfabe6 190
b2a74f99
DJ
191 Patch Champions
192 ---------------
58cfabe6 193
b2a74f99
DJ
194These volunteers track all patches submitted to the gdb-patches list. They
195endeavor to prevent any posted patch from being overlooked; work with
196contributors to meet GDB's coding style and general requirements, along with
197FSF copyright assignments; remind (ping) responsible maintainers to review
198patches; and ensure that contributors are given credit.
58cfabe6 199
b2a74f99 200Current patch champions (in alphabetical order):
54c92070 201
c9f7217e 202 Randolph Chung <tausq@debian.org>
58cfabe6 203
a60a53c5 204
a60a53c5 205
b2a74f99
DJ
206 Responsible Maintainers
207 -----------------------
208
209These developers have agreed to review patches in specific areas of GDB, in
210which they have knowledge and experience. These areas are generally broad;
211the role of a responsible maintainer is to provide coherent and cohesive
212structure within their area of GDB, to assure that patches from many
213different contributors all work together for the best results.
a60a53c5 214
b2a74f99
DJ
215Global maintainers will defer to responsible maintainers within their areas,
216as long as the responsible maintainer is active. Active means that
217responsible maintainers agree to review submitted patches in their area
218promptly; patches and followups should generally be answered within a week.
219If a responsible maintainer is interested in reviewing a patch but will not
220have time within a week of posting, the maintainer should send an
221acknowledgement of the patch to the gdb-patches mailing list, and
222plan to follow up with a review within a month. These deadlines are for
223initial responses to a patch - if the maintainer has suggestions
224or questions, it may take an extended discussion before the patch
225is ready to commit. There are no written requirements for discussion,
226but maintainers are asked to be responsive.
227
228If a responsible maintainer misses these deadlines occasionally (e.g.
229vacation or unexpected workload), it's not a disaster - any global
230maintainer may step in to review the patch. But sometimes life intervenes
231more permanently, and a maintainer may no longer have time for these duties.
232When this happens, he or she should step down (either into the Authorized
233Committers section if still interested in the area, or simply removed from
234the list of Responsible Maintainers if not).
235
236If a responsible maintainer is unresponsive for an extended period of time
237without stepping down, please contact the Global Maintainers; they will try
238to contact the maintainer directly and fix the problem - potentially by
239removing that maintainer from their listed position.
240
241If there are several maintainers for a given domain then any one of them
242may review a submitted patch.
a60a53c5 243
c1bab85b 244Target Instruction Set Architectures:
8860ff2e 245
91a533d4
AC
246The *-tdep.c files. ISA (Instruction Set Architecture) and OS-ABI
247(Operating System / Application Binary Interface) issues including CPU
248variants.
249
250The Target/Architecture maintainer works with the host maintainer when
251resolving build issues. The Target/Architecture maintainer works with
252the native maintainer when resolving ABI issues.
5185fdd7 253
8f9cbe01 254 alpha --target=alpha-elf ,-Werror
21a6f6bb 255
66140c26 256 arm --target=arm-elf ,-Werror
26806ce2 257 Richard Earnshaw rearnsha@arm.com
9b82661c 258
e33ce519 259 avr --target=avr ,-Werror
b06adb81 260 Tristan Gingold gingold@adacore.com
e33ce519 261
cb5c8c39
DJ
262 cris --target=cris-elf ,-Werror ,
263 (sim does not build with -Werror)
93755ae6 264
53e8aaea 265 frv --target=frv-elf ,-Werror
53e8aaea 266
87d088f5 267 h8300 --target=h8300-elf ,-Werror
9b82661c 268
c1bab85b 269 i386 --target=i386-elf ,-Werror
21a6f6bb
AC
270 Mark Kettenis kettenis@gnu.org
271
32089c7c
AC
272 ia64 --target=ia64-linux-gnu ,-Werror
273 (--target=ia64-elf broken)
606139a1 274 Jan Kratochvil jan.kratochvil@redhat.com
9b82661c 275
c28c63d8
JB
276 lm32 --target=lm32-elf ,-Werror
277
96309189 278 m32c --target=m32c-elf ,-Werror
96309189 279
9644bbdd 280 m32r --target=m32r-elf ,-Werror
9b82661c 281
53fe9346 282 m68hc11 --target=m68hc11-elf ,-Werror ,
2be99286 283 Stephane Carrez stcarrez@nerim.fr
9b82661c 284
043c9cdc 285 m68k --target=m68k-elf ,-Werror
9b82661c 286
1698f4e7
MK
287 m88k --target=m88k-openbsd ,-Werror
288 Mark Kettenis kettenis@gnu.org
9b82661c 289
9445aa30 290 mcore Deleted
9b82661c 291
01c996c1
KB
292 mep --target=mep-elf ,-Werror
293 Kevin Buettner kevinb@redhat.com
294
599ec134
JB
295 microblaze --target=microblaze-xilinx-elf ,-Werror
296 --target=microblaze-linux-gnu ,-Werror
297 Michael Eager eager@eagercon.com
298
c1bab85b 299 mips --target=mips-elf ,-Werror
9b82661c 300
87d088f5
AC
301 mn10300 --target=mn10300-elf broken
302 (sim/ dies with make -j)
11fa8e43 303 Michael Snyder msnyder@vmware.com
9b82661c 304
d7066cce
AG
305 moxie --target=moxie-elf ,-Werror
306 Anthony Green green@moxielogic.com
307
37ebea84
KB
308 ms1 --target=ms1-elf ,-Werror
309 Kevin Buettner kevinb@redhat.com
310
9445aa30 311 ns32k Deleted
9b82661c 312
93449403 313 pa --target=hppa-elf ,-Werror
21a6f6bb 314
8dacb7ef 315 powerpc --target=powerpc-eabi ,-Werror
9b82661c 316
9f9d12b3 317 s390 --target=s390-linux-gnu ,-Werror
5769d3cd 318
27fd2f50
Q
319 score --target=score-elf
320 Qinwei qinwei@sunnorth.com.cn
321
5dbc6baa 322 sh --target=sh-elf ,-Werror
079c8cd0 323 --target=sh64-elf ,-Werror
9b82661c 324
cb5c8c39
DJ
325 sparc --target=sparc64-solaris2.10 ,-Werror
326 (--target=sparc-elf broken)
9b82661c 327
d1320b0b
UW
328 spu --target=spu-elf ,-Werror
329 Ulrich Weigand uweigand@de.ibm.com
330
181124bc 331 v850 --target=v850-elf ,-Werror
21a6f6bb 332
043c9cdc 333 vax --target=vax-netbsd ,-Werror
21a6f6bb 334
53fe9346 335 x86-64 --target=x86_64-linux-gnu ,-Werror
e4621584 336
b6fcb393 337 xstormy16 --target=xstormy16-elf
7c0a2a0a
CV
338 Corinna Vinschen vinschen@redhat.com
339
9cd84602
MG
340 xtensa --target=xtensa-elf
341 Maxim Grigoriev maxim2405@gmail.com
342
fcc87af1
AC
343All developers recognized by this file can make arbitrary changes to
344OBSOLETE targets.
9b82661c 345
684e56bf
AC
346The Bourne shell script gdb_mbuild.sh can be used to rebuild all the
347above targets.
5185fdd7
AC
348
349
8860ff2e
AC
350Host/Native:
351
9b82661c
AC
352The Native maintainer is responsible for target specific native
353support - typically shared libraries and quirks to procfs/ptrace/...
354The Native maintainer works with the Arch and Core maintainers when
355resolving more generic problems.
8860ff2e 356
9175c9a3
MC
357The host maintainer ensures that gdb can be built as a cross debugger on
358their platform.
5185fdd7 359
f4d408c6 360AIX Joel Brobecker brobecker@adacore.com
3e6b0399 361Darwin Tristan Gingold gingold@adacore.com
56a5d675 362djgpp native Eli Zaretskii eliz@gnu.org
e0f2823e 363GNU Hurd Alfred M. Szmidt ams@gnu.org
842330b4 364MS Windows (NT, '00, 9x, Me, XP) host & native
859a326d 365 Chris Faylor cgf@alum.bu.edu
ef7b4488 366GNU/Linux/x86 native & host
ef7b4488 367 Mark Kettenis kettenis@gnu.org
6c8e04b5 368GNU/Linux MIPS native & host
322be962 369 Daniel Jacobowitz dan@codesourcery.com
a2f63f5e 370GNU/Linux m68k Andreas Schwab schwab@linux-m68k.org
e255d535 371FreeBSD native & host Mark Kettenis kettenis@gnu.org
5185fdd7 372
9b82661c
AC
373
374
5185fdd7
AC
375Core: Generic components used by all of GDB
376
11fa8e43
MS
377tracing Michael Snyder msnyder@vmware.com
378threads Michael Snyder msnyder@vmware.com
a8596edf 379 Mark Kettenis kettenis@gnu.org
f4d408c6 380language support
b33682a7
DJ
381 Ada Joel Brobecker brobecker@adacore.com
382 Paul Hilfinger hilfinger@gnat.com
322be962 383 C++ Daniel Jacobowitz dan@codesourcery.com
3771659b 384 Objective C support Adam Fedor fedor@gnu.org
f4d408c6 385shared libs Kevin Buettner kevinb@redhat.com
d9bf65d5 386MI interface Vladimir Prus vladimir@codesourcery.com
e306c308 387
e8be95ae 388documentation Eli Zaretskii eliz@gnu.org
49101e1c 389 (including NEWS)
f4d408c6 390testsuite
5a703563 391 gdbtk (gdb.gdbtk) Keith Seitz keiths@redhat.com
11fa8e43
MS
392 threads (gdb.threads) Michael Snyder msnyder@vmware.com
393 trace (gdb.trace) Michael Snyder msnyder@vmware.com
5185fdd7
AC
394
395
396UI: External (user) interfaces.
397
f4d408c6 398gdbtk (c & tcl) Fernando Nasser fnasser@redhat.com
54403c59 399 Keith Seitz keiths@redhat.com
f4d408c6 400libgui (w/foundry, sn) Keith Seitz keiths@redhat.com
f5bca8e7
AC
401
402
403Misc:
404
322be962 405gdb/gdbserver Daniel Jacobowitz dan@codesourcery.com
3f289e6f 406
f5bca8e7 407Makefile.in, configure* ALL
7158fd7f
AC
408
409mmalloc/ ALL Host maintainers
410
f779ca99 411sim/ See sim/MAINTAINERS
5185fdd7 412
9ec7faef 413readline/ Master version: ftp://ftp.cwru.edu/pub/bash/
f4d408c6 414 ALL
9ec7faef
AC
415 Host maintainers (host dependant parts)
416 (but get your changes into the master version)
417
f4d408c6 418tcl/ tk/ itcl/ ALL
ef7b4488 419
b2a74f99
DJ
420
421 Authorized Committers
422 ---------------------
423
424These are developers working on particular areas of GDB, who are trusted to
425commit their own (or other developers') patches in those areas without
426further review from a Global Maintainer or Responsible Maintainer. They are
427under no obligation to review posted patches - but, of course, are invited
428to do so!
429
f4d408c6 430PowerPC Andrew Cagney cagney@gnu.org
cfefc99a 431CRIS Hans-Peter Nilsson hp@axis.com
f4d408c6
DJ
432IA64 Jeff Johnston jjohnstn@redhat.com
433MIPS Joel Brobecker brobecker@adacore.com
434m32r Kei Sakamoto sakamoto.kei@renesas.com
435PowerPC Kevin Buettner kevinb@redhat.com
436CRIS Orjan Friberg orjanf@axis.com
437HPPA Randolph Chung tausq@debian.org
438S390 Ulrich Weigand uweigand@de.ibm.com
439djgpp DJ Delorie dj@delorie.com
440 [Please use this address to contact DJ about DJGPP]
441tui Stephane Carrez stcarrez@nerim.fr
442ia64 Kevin Buettner kevinb@redhat.com
443AIX Kevin Buettner kevinb@redhat.com
444GNU/Linux PPC native Kevin Buettner kevinb@redhat.com
445gdb.java tests Anthony Green green@redhat.com
446FreeBSD native & host David O'Brien obrien@freebsd.org
692263b8
JB
447event loop Elena Zannoni elena.zannoni@oracle.com
448generic symtabs Elena Zannoni elena.zannoni@oracle.com
449dwarf readers Elena Zannoni elena.zannoni@oracle.com
450elf reader Elena Zannoni elena.zannoni@oracle.com
451stabs reader Elena Zannoni elena.zannoni@oracle.com
452readline/ Elena Zannoni elena.zannoni@oracle.com
f4d408c6 453NetBSD native & host Jason Thorpe thorpej@netbsd.org
0643c12e 454Pascal support Pierre Muller muller@sourceware.org
f4d408c6 455avr Theodore A. Roth troth@openavr.org
13942a42 456Modula-2 support Gaius Mulley gaius@glam.ac.uk
b2a74f99
DJ
457
458
e7745bde
AC
459 Write After Approval
460 (alphabetic)
5185fdd7 461
b76a2a57
AC
462To get recommended for the Write After Approval list you need a valid
463FSF assignment and have submitted one good patch.
464
20dad8ea 465Pedro Alves pedro_alves@portugalmail.pt
b302179c 466David Anderson davea@sgi.com
871cce51 467John David Anglin dave.anglin@nrc-cnrc.gc.ca
062103ba 468Shrinivas Atre shrinivasa@kpitcummins.com
627054c8 469Scott Bambrough scottb@netwinder.org
07bed550 470Thiago Jung Bauermann bauerman@br.ibm.com
7a893eb8 471Jon Beniston jon@beniston.com
ae2a31bf 472Jan Beulich jbeulich@novell.com
2f83030f 473Jim Blandy jimb@codesourcery.com
e7745bde 474Philip Blundell philb@gnu.org
627054c8 475Per Bothner per@bothner.com
1581f359 476Joel Brobecker brobecker@adacore.com
cdd463f9 477Dave Brolley brolley@redhat.com
dbf5be1c 478Paul Brook paul@codesourcery.com
5b031165 479Julian Brown julian@codesourcery.com
627054c8 480Kevin Buettner kevinb@redhat.com
1db2a798 481Andrew Cagney cagney@gnu.org
58e23df4 482David Carlton carlton@bactrian.org
627054c8 483Stephane Carrez stcarrez@nerim.fr
68e39e73 484Michael Chastain mec.gnu@mindspring.com
e04e8f8a 485Eric Christopher echristo@apple.com
700c15aa 486Randolph Chung tausq@debian.org
f9e2d830 487Nick Clifton nickc@redhat.com
f4d408c6 488J.T. Conklin jtc@acorntoolworks.com
56296155 489Brendan Conoboy blc@redhat.com