public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Fangrui Song <maskray@google.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: overseers@sourceware.org, Stan Shebs <stanshebs@google.com>
Subject: Re: Request from Fangrui Song
Date: Mon, 8 Jun 2020 14:31:55 -0700	[thread overview]
Message-ID: <20200608213155.mqbm6fedl74ibdyx@google.com> (raw)
In-Reply-To: <89a24c88-7b33-c8fd-83d5-e3c6f7549b68@redhat.com>

On 2020-06-08, Carlos O'Donell wrote:
>On 6/5/20 5:08 PM, Fāng-ruì Sòng wrote:
>> On Fri, Jun 5, 2020 at 1:56 PM Stan Shebs <stanshebs@google.com> wrote:
>>
>>> On Fri, Jan 31, 2020 at 10:55 PM Carlos O'Donell <codonell@redhat.com>
>>> wrote:
>>>>
>>>> On 1/25/20 4:42 PM, Christopher Faylor wrote:
>>>>> On Fri, Jan 24, 2020 at 11:07:10PM -0000, maskray.google.com via
>>> overseers wrote:
>>>>>> Fangrui Song 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=2263303.54129
>>>>>
>>>>> Sorry, but if I read the rules right at:
>>> https://sourceware.org/glibc/wiki/MAINTAINERS
>>>>> you need to be approved by a project steward for access and Stan is
>>> not,
>>>>> AFAICT, one of those.those.
>>>>
>>>> Christopher, That is correct. Stewards approve write access.
>>>>
>>>> Stan, Please feel free to reach out to me so I can resolve this issue
>>> for you. Likewise you can reach out to any other steward. We mostly want to
>>> make sure that everyone is following correct copyright protocol.
>>>
>>> I guess this has been in limbo?  In any case, I would like for you to
>>> approve Fangrui's write access to glibc; copyrightwise he's a Google
>>> employee and therefore covered under the company's general assignment.
>>> Thanks!
>>>
>>
>> Thanks Stan for pinging this thread.
>>
>> Dear overseers, I have 3 commits to glibc and 10 commits to binutils-gdb
>> now. Hope the request is not unreasonable.
>
>I'm happy to approve you. Do you have a sourceware account? If you don't,
>please apply for that first and I'll approve that. Then we can add you to
>the commit ACLs for glibc.
>
>-- 
>Cheers,
>Carlos.
>

Thanks, Carlos.

I just visited https://sourceware.org/cgi-bin/pdw/ps_form.cgi ,
filled in the forms (Fangrui Song, maskray, maskray@google.com, glibc, SSH pubkey),
wrote your email address as the approver.

> Thanks for your request. It must be approved by the person you named as
> approver, as well as manually validated and processed by an overseer, so
> do not expect an instant response. If there has not been a reply after
> several days, and you are sure the person named as approver has approved
> it, do not resubmit your request, but instead mail the overseers at
> overseers@sourceware.org

  reply	other threads:[~2020-06-08 21:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24 23:07 maskray.google.com via overseers
2020-01-25 21:42 ` Christopher Faylor
2020-02-01  4:55   ` Carlos O'Donell
2020-06-05 20:56     ` Stan Shebs
2020-06-05 21:08       ` Fāng-ruì Sòng
2020-06-08 21:13         ` Carlos O'Donell
2020-06-08 21:31           ` Fangrui Song [this message]
2020-06-08 21:36             ` Carlos O'Donell
2020-06-08 21:44               ` Fangrui Song
2020-06-08 21:28 maskray

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=20200608213155.mqbm6fedl74ibdyx@google.com \
    --to=maskray@google.com \
    --cc=carlos@redhat.com \
    --cc=overseers@sourceware.org \
    --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).