Differences between revisions 94 and 95
Revision 94 as of 2014-07-23 00:31:32
Size: 9850
Editor: AllanMcRae
Revision 95 as of 2014-07-23 00:35:14
Size: 9715
Editor: AllanMcRae
Comment: Remove ports references
Deletions are marked like this. Additions are marked like this.
Line 104: Line 104:
 * aarch64 (ports)  * aarch64
Line 106: Line 106:
 * arm (ports)  * arm
Line 109: Line 109:
 * alpha (ports)  * alpha
Line 111: Line 111:
 * hppa (ports)  * hppa
Line 114: Line 114:
 * i386, x86_64, x32 (libc)  * i386, x86_64, x32
Line 118: Line 118:
 * ia64 (ports)  * ia64
Line 120: Line 120:
 * m68k (ports)  * m68k
Line 122: Line 122:
 * linux-generic (ports)  * linux-generic
Line 124: Line 124:
 * microblaze (ports)  * microblaze
Line 126: Line 126:
 * mips (ports)  * mips
Line 128: Line 128:
 * powerpc (libc)  * powerpc
Line 131: Line 131:
 * powerpc (ports)
Line 133: Line 132:
 * s390 (libc)  * s390
Line 136: Line 135:
 * sh (libc)  * sh
Line 139: Line 138:
 * sparc (libc)  * sparc
Line 141: Line 140:
 * tile (ports)  * tile


If you would like your name added or removed from this list, please do so yourself.

Becoming a maintainer (developer)

So you want to become a maintainer (developer) eh?

This is how you do it:

  • Start by signing a copyright assignment for glibc, that will allow you to contribute to the parts of the project that require copyright assignment (almost all of it except for locales).

  • Once you have established that you are doing good work and following the contribution checklist, you may be approved for commit access as a maintainer (developer). Talk to the senior developers and ask them if being a maintainer (developer) is right for you. If the senior developers agree, then proceed to the next step.
  • The first step towards commit access is to follow these instructions to get an account on sourceware.

  • Once you have a sourceware account ask one of the existing senior developers for authorize your commit access. If the existing senior developer authorizes you for commit access follow these instructions to get commit access.

  • Once you have commit access you should immediately add yourself to the list of maintainers (developers). If you can't edit this page you should follow these instructions to get edit access to the wiki.

  • Get yourself a patchwork account on patchwork.sourceware.org and go through the Patch Review Workflow

You're a maintainer (developers) now! Huzzah!

Project stewards (GNU package maintainers)

The following people have agreed to be responsible for glibc to the GNU Project (alphabetical order by last name):

  • Ryan S. Arnold (rsa,ryanarn)
  • Mark Brown
  • Paul Eggert (eggert)
  • Jakub Jelinek (jakub)
  • Maxim Kuvyrkov (maximk,mkuvyrkov)
  • Roland McGrath (roland)

  • Joseph Myers (jsm28)
  • Carlos O'Donell (carlos)
  • Alexandre Oliva (aoliva)
  • Andreas Schwab (schwab)

These people are the GNU package maintainers of glibc, with the associated responsibilities. Other people listed are "developers" in GNU project terms.

Maintainers (developers) for libc

Write after Consensus and/or approval from machine maintainer (alphabetical order by last name):

  • Ryan S. Arnold (rsa,ryanarn)
  • Jeff Bailey (jbailey)
  • Petr Baudis (pasky)
  • Philip Blundell (pb)
  • Thomas Bushnell (tb)
  • Liubov Dmitrieva (ldmitrie)
  • Ulrich Drepper (drepper)
  • Paul Eggert (eggert)
  • Mike Frysinger (vapier)
  • Richard Henderson (rth)
  • Daniel Jacobowitz (drow)
  • Andreas Jaeger (aj)
  • Aurelien Jarno (aurel32)
  • Jakub Jelinek (jakub)
  • Geoffrey Keating (geoffk)
  • Mark Kettenis (kettenis)
  • Kaz Kojima (kkojima)
  • Jan Kratochvil (jkratoch)
  • Maxim Kuvyrkov (maximk,mkuvyrkov)
  • Jeff Law (law)
  • Dmitry V. Levin (ldv)
  • H. J. Lu (hjl)
  • Greg McGary (gkm)

  • Roland McGrath (roland)

  • Allan McRae (allan)

  • Luis Machado (luisgpm)
  • Chris Metcalf (cmetcalf)
  • Jim Meyering (meyering)
  • David S. Miller (davem)
  • Brooks Moses (brooks)
  • Steven Munroe (sjmunroe)
  • Joseph Myers (jsm28)
  • Will Newton (willnewton)
  • Jonathan Nieder (jrnieder)
  • Carlos O'Donell (carlos)
  • Alexandre Oliva (aoliva)
  • Paul Pluzhnikov (ppluzhnikov)
  • Marek Polacek (mpolacek)
  • Siddhesh Poyarekar (siddhesh)
  • Torvald Riegel (torvald)
  • Maciej W. Rozycki (macro)
  • Andreas Schwab (schwab)
  • Thomas Schwinge (tschwinge)
  • Carlos Eduardo Seo (cseo)
  • Marcus Shawcroft (mshawcroft)
  • Franz Sirl (sirl)
  • Alfred M. Szmidt (amszmidt)
  • Tom de Vries (vries)
  • Florian Weimer (fw)
  • Adhemerval Zanella (azanella)

Operating system port maintainers

  • GNU Hurd
    • Roland McGrath (roland)

  • Linux
    • the respective machine maintainers

Machine maintainers

  • aarch64
    • Marcus Shawcroft (mshawcroft)
  • arm
    • Philip Blundell (pb)
    • Joseph Myers (jsm28)
  • alpha
    • Richard Henderson (rth)
  • hppa
    • Carlos O'Donell (carlos)
    • Jeff Bailey (jbailey)
  • i386, x86_64, x32
    • Community review.
    • Carlos O'Donell (carlos)
    • Andreas Jaeger (aj)
  • ia64
    • Mike Frysinger (vapier)
  • m68k
    • Andreas Schwab (schwab)
  • linux-generic
    • Chris Metcalf (cmetcalf)
  • microblaze
    • David Holsgrove (davidholsgrove)
  • mips
    • Joseph Myers (jsm28)
  • powerpc
    • Adhemerval Zanella (azanella)
    • Steven Munroe (sjmunroe)
    • Ryan S. Arnold (rsa,ryanarn)
  • s390
    • Andreas Krebbel (zommi)
    • Martin Schwidefsky (schwidefsky)
  • sh
    • Kaz Kojima (kkojima)
    • Thomas Schwinge (tschwinge)
  • sparc
    • David S. Miller (davem)
  • tile
    • Chris Metcalf (cmetcalf)

Distribution Maintainers

At the distribution level there are developers who are responsible for glibc in their particular distribution. These developers are an excellent point of contact when we have distribution related issues or questions and they should be consulted on issues that have far reaching effects on the distributions.

In alphabetical order by distribution:

Maintainers for the website

Blanket commit with the understanding that consultation and discretion are required. We maintain two websites, the official FSF website and another site at sourceware.org that forwards to the FSF one. See the Website Maintenance.

  • Carlos O'Donell (carlos)

Maintainers for the wiki

We maintain the text captchas on the wiki. You need login to sourceware.org followed by the ability to edit /wiki/glibc.py to add or modify existing captchas. The following people have permission to edit the wiki captchas:

  • Carlos O'Donell (carlos)

Maintainers for Bugzilla

Changes to bugzilla should be discussed by the entire community.

  • Carlos O'Donell (carlos)
  • Roland McGrath (roland)

Maintainers for linuxthreads add-on

  • The linuxthreads add-on is no longer being actively maintained. The last official maintainer was Daniel Jacobowitz (drow).

Reviewers by component

This is not a table of designated component-wise maintainers (yet). The intent of this table is to record which project members are either interested in or consider themselves capable of reviewing changes in the respective components. The component list is taken from bugzilla. Over time, an additional column could be added to record component owners.




Roland McGrath


Carlos O'Donell


Roland McGrath, Thomas Schwinge


Petr Baudis (don't block on him)


Carlos O'Donell


Roland McGrath


Andreas Jaeger




Carlos O'Donell


Petr Baudis (don't block on him)




Everything else

Carlos O'Donell

Accounts on Sourceware.org

The glibc source is graciously hosted by Red Hat on sourceware.org. You will need an account on sourceware.org before you can become a developer. Use this handy dandy form to make that request: http://sourceware.org/cgi-bin/pdw/ps_form.cgi

Source Control ACLs

Senior developers in the project are responsible for authorizing commit access (through overseers@sourceware.org ) to the glibc group for the glibc and glibc-ports repositories. Once you are in the glibc group you will have write access to the repositories. Developers requesting commit access should email overseers@sourceware.org , CC the senior developer granting access (the senior developer will acknowledge the authorization), and include your sourceware account name and that you would like glibc group access to commit to the glibc repository.

Contacting maintainers

The normal way to contact maintainers about bugs is via the Bugzilla Procedures. Important security-related bugs, where public notification may cause harm to users, can be reported privately to the maintainers via the abovementioned email addresses. People are also welcome to report bugs via more-formal approaches, e.g., the U.S. Computer Emergency Readiness Team (US-CERT). There is a formal channel between US-CERT and the GNU C library developers.

Common sense is advised for deciding how important a security-relevant bug is. Triage tools are available.

LinkedIn Group

We have a LinkedIn Group for GLIBC Developers. The group is moderated by Carlos O'Donell.

Ohloh Group

We have an Ohloh Project for tracking glibc. The project is moderated by Carlos O'Donell.

None: MAINTAINERS (last edited 2019-08-12 11:44:03 by Stefan Liebler)