Getting glibc write access

[Siddhesh Poyarekar]

On Tue, Jun 03, 2014 at 02:09:49PM +0100, Wilco wrote:
> Hi,
> 
> I applied for write access a few weeks back, but nothing seems to have
> happened since. How does this work?
> 
> Wilco
> 
> -----Original Message-----
> From: Christopher Faylor [mailto:cgf-use-the-mailinglist-please@sourceware.org] 
> Sent: 14 May 2014 15:29
> To: Wilco Dijkstra; overseers@sourceware.org
> Subject: Re: Request from Wilco Dijkstra
> 
> On Tue, May 13, 2014 at 03:26:51PM -0000, wdijkstr@arm.com wrote:
> >Wilco Dijkstra would like to be added to sourceware.org.
> >
> >For more information, check out:
> >http://sourceware.org/cgi-bin/pdw/queue.cgi
> >
> >Or, check the specific request here:
> >http://sourceware.org/cgi-bin/pdw/details.cgi?file=6255933.15820
> 
> I'm not sure what the rules are for giving access to glibc.  I
> don't see a MAINTAINERS file in the top-level.
> 
> Perhaps one of the maintainers could clarify.

There's a MAINTAINERS wiki page instead:

https://sourceware.org/glibc/wiki/MAINTAINERS

You need a senior developer to refer you for commit access.  The term
'senior' has usually been pretty vague, but for commit access I'd read
it as one of the project overlords, err, stewards.

Siddhesh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20140603/e3989093/attachment.sig>