Re: Resetting my public key and gaining write access to glibc

["Stan Shebs via overseers" <overseers@sourceware.org>]

On Fri, Mar 15, 2019 at 3:55 PM Carlos O'Donell <codonell@redhat.com> wrote:
>
> On 3/15/19 2:49 PM, Siva Chandra via overseers wrote:
> > Hello overseers,
> >
> > I have a sourceware.org account with username "sivachandra". I have write
> > access for binutils-gdb, and would now like to gain write access to glibc.
> > I will mainly be committing to the google/* branches.
> >
> > Since it has been a few years that I last committed to the GDB repo, I have
> > lost the public key I set up for it. How do I restore my ssh credentials?
>
> Siva,
>
> Send me your authorized_keys file privately.
>
> Please follow the the new maintainer process for glibc:
> https://sourceware.org/glibc/wiki/MAINTAINERS#Becoming_a_maintainer_.28developer.29
>
> I understand that your primary interest is in committing to the google/*
> branches, but that permission still grants you access to the entire repo.
>
> (1) You have copyright assignment via Google. Please consider a personal assignment also
>      if you want to send patches from your own email address.
>
> (2-5) Please setup the normal community accounts if you need them, at a minimum you need
>        wiki edit access to add yourself as a developer (anyone in the community, including
>        Stan or Brooks can give you EditorGroup access).
>
> (6) Which steward for the project is granting you commit access? Feel free to ask me
>      to grant the access.
>
> (7) Don't forget to add yourself to the developers list, *and* the committer list for
>      the google/* namespace:
>      https://sourceware.org/glibc/wiki/GlibcGit#Branch_Name_Space_Conventions
>
> Stan,
>
> Do you authorize Siva to commit to the google/* branch namespace?

Yes, we're sucking him into the horror. :-)