From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 65497 invoked by alias); 19 Jan 2019 06:58:10 -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 65486 invoked by uid 89); 19 Jan 2019 06:58:09 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=BAYES_00,SPF_HELO_PASS,SPF_NEUTRAL autolearn=no version=3.3.2 spammy=becoming, H*Ad:U*overseers, Hx-spam-relays-external:ESMTPA X-HELO: cgf.cx Received: from external.cgf.cx (HELO cgf.cx) (107.170.62.102) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 19 Jan 2019 06:58:08 +0000 Received: from ednor.casa.cgf.cx (pool-96-230-71-89.bstnma.fios.verizon.net [96.230.71.89]) by cgf.cx (Postfix) with ESMTPA id 7F60D40607; Sat, 19 Jan 2019 01:58:05 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.11.0 cgf.cx 7F60D40607 Received: by ednor.casa.cgf.cx (sSMTP sendmail emulation); Sat, 19 Jan 2019 01:58:04 -0500 Date: Sat, 19 Jan 2019 06:58:00 -0000 From: Christopher Faylor To: Carlos O'Donell Cc: "overseers@sourceware.org" Subject: Re: Request for commit access to glibc Message-ID: <20190119065804.GA7703@ednor.casa.cgf.cx> Mail-Followup-To: Carlos O'Donell , "overseers@sourceware.org" References: <20190118040549.GA14528@ednor.casa.cgf.cx> <4497db54-1fe7-46ab-17de-3bf347bd9c00@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4497db54-1fe7-46ab-17de-3bf347bd9c00@redhat.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-SW-Source: 2019-q1/txt/msg00018.txt.bz2 On Fri, Jan 18, 2019 at 01:51:12PM -0500, Carlos O'Donell wrote: >Did we roll the glibc group access setup into one step? > >We have it as a distinct step in the glibc account setup process right now. > >"Becoming a maintainer (developer)" >https://sourceware.org/glibc/wiki/MAINTAINERS#Becoming_a_maintainer_.28developer.29 > >"Source Control ACLs" >https://sourceware.org/glibc/wiki/MAINTAINERS#SourceControlACL Sourceware account creation has always granted you access to the project for requested project. sourceware accounts are only for source control access so providing an account with no attached project wouldn't make any sense. The only time that follow-on email to overseers is required is when you are requesting access to additional project other than the one mentioned in the initial account creation, e.g., when you have a glibc account and want additional write access to gcc. cgf