public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <codonell@redhat.com>
To: Siva Chandra <sivachandra@google.com>,
	overseers@sourceware.org, Stan Shebs <stanshebs@google.com>,
	Brooks Moses <bmoses@google.com>
Subject: Re: Resetting my public key and gaining write access to glibc
Date: Fri, 15 Mar 2019 20:55:00 -0000	[thread overview]
Message-ID: <867c108f-1683-574f-91ef-104194beedbc@redhat.com> (raw)
In-Reply-To: <CAGyQ6gxq-Jq2jYsFA2Ken0cLNfpR3-wNJBYHWbtmvEvfwm9YUg@mail.gmail.com>

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?

You should also add yourself to the developers list:
https://sourceware.org/glibc/wiki/MAINTAINERS#Maintainers_.28developers.29_for_libc

-- 
Cheers,
Carlos.

  reply	other threads:[~2019-03-15 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15 18:50 Siva Chandra via overseers
2019-03-15 20:55 ` Carlos O'Donell [this message]
2019-03-18 18:45   ` Stan Shebs via overseers
2019-03-28  4:17 ` Carlos O'Donell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=867c108f-1683-574f-91ef-104194beedbc@redhat.com \
    --to=codonell@redhat.com \
    --cc=bmoses@google.com \
    --cc=overseers@sourceware.org \
    --cc=sivachandra@google.com \
    --cc=stanshebs@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).