From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 110417 invoked by alias); 18 Mar 2019 18:45:45 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 110330 invoked by uid 89); 18 Mar 2019 18:45:41 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-9.4 required=5.0 tests=AWL,BAYES_00,ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_PASS,USER_IN_DEF_SPF_WL autolearn=ham version=3.3.1 spammy=privately, horror, Google, google X-HELO: mail-oi1-f196.google.com Received: from mail-oi1-f196.google.com (HELO mail-oi1-f196.google.com) (209.85.167.196) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 18 Mar 2019 18:45:40 +0000 Received: by mail-oi1-f196.google.com with SMTP id u12so10973820oiv.1 for ; Mon, 18 Mar 2019 11:45:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/bUpe6nmCQT1TLbVLm9v2t9WFjlS+pWvkNqKPUwgdKo=; b=qKWPnzQdGFnxyeQMfSYRLOTuiW0e6hiVVmBImBQ5icFrcyPXfvLthfh/BxNGRxis1L lksabPhhCgotkNBdA9YgA9V3pXab/Rfs2Q/EdtzCGF6CnqKsx2HRgLRcCHzj4/Afw5f6 liBd0hBgyUn4khCic0KxOmE4SlOhPf7xHQ822mnyonYT0r2uUtr3SAMjGYH2lhVU/68Q yzTU/cKyTsqvmSu/DjoGd2vULmt6frg62AjZT4nQfE0hKR8GX+fWliCq6shg9xOQgKXY yJxZeXMQ4wKJrOjCFa6F0eRgXMULVEksw3Wf81DKkVh8IZe0UNFBV/SakoGEdTX5E+jd tkSA== MIME-Version: 1.0 References: <867c108f-1683-574f-91ef-104194beedbc@redhat.com> In-Reply-To: <867c108f-1683-574f-91ef-104194beedbc@redhat.com> From: "Stan Shebs via overseers" Reply-To: Stan Shebs Date: Mon, 18 Mar 2019 18:45:00 -0000 Message-ID: Subject: Re: Resetting my public key and gaining write access to glibc To: "Carlos O'Donell" Cc: Siva Chandra , overseers@sourceware.org, Brooks Moses Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2019-q1/txt/msg00061.txt.bz2 On Fri, Mar 15, 2019 at 3:55 PM Carlos O'Donell 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. :-)