+For documentation changes, about the only kind of fix that is obvious
+is correction of a typo or bad English usage.
+
+
+ GDB Steering Committee
+ ----------------------
+
+The members of the GDB Steering Committee are the FSF-appointed
+maintainers of the GDB project.
+
+The Steering Committee has final authority for all GDB-related topics;
+they may make whatever changes that they deem necessary, or that the FSF
+requests. However, they are generally not involved in day-to-day
+development.
+
+The current members of the steering committee are listed below, in
+alphabetical order. Their affiliations are provided for reference only -
+their membership on the Steering Committee is individual and not through
+their affiliation, and they act on behalf of the GNU project.
+
+ Jim Blandy (Mozilla)
+ Andrew Cagney (Red Hat)
+ Robert Dewar (AdaCore, NYU)
+ Klee Dienes (Apple)
+ Paul Hilfinger (UC Berkeley)
+ Dan Jacobowitz (CodeSourcery)
+ Stan Shebs (CodeSourcery)
+ Richard Stallman (FSF)
+ Ian Lance Taylor (C2)
+ Todd Whitesel
+
+
+ Global Maintainers
+ ------------------
+
+The global maintainers may review and commit any change to GDB, except in
+areas with a Responsible Maintainer available. For major changes, or
+changes to areas with other active developers, global maintainers are
+strongly encouraged to post their own patches for feedback before
+committing.
+
+The global maintainers are responsible for reviewing patches to any area
+for which no Responsible Maintainer is listed.
+
+Global maintainers also have the authority to revert patches which should
+not have been applied, e.g. patches which were not approved, controversial
+patches committed under the Obvious Fix Rule, patches with important bugs
+that can't be immediately fixed, or patches which go against an accepted and
+documented roadmap for GDB development. Any global maintainer may request
+the reversion of a patch. If no global maintainer, or responsible
+maintainer in the affected areas, supports the patch (except for the
+maintainer who originally committed it), then after 48 hours the maintainer
+who called for the reversion may revert the patch.
+
+No one may reapply a reverted patch without the agreement of the maintainer
+who reverted it, or bringing the issue to the GDB Steering Committee for
+discussion.
+
+At the moment there are no documented roadmaps for GDB development; in the
+future, if there are, a reference to the list will be included here.
+
+The current global maintainers are (in alphabetical order):
+
+Pedro Alves pedro@codesourcery.com
+Jim Blandy jimb@red-bean.com
+Joel Brobecker brobecker@adacore.com
+Kevin Buettner kevinb@redhat.com
+Andrew Cagney cagney@gnu.org
+Daniel Jacobowitz dan@debian.org
+Mark Kettenis kettenis@gnu.org
+Stan Shebs stan@codesourcery.com
+Michael Snyder msnyder@vmware.com
+Tom Tromey tromey@redhat.com
+Ulrich Weigand Ulrich.Weigand@de.ibm.com
+Elena Zannoni elena.zannoni@oracle.com
+Eli Zaretskii eliz@gnu.org
+