From: Alistair Francis <alistair23@gmail.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: overseers@sourceware.org, Alistair Francis <alistair.francis@wdc.com>
Subject: Re: glibc commit access
Date: Wed, 25 Sep 2019 20:45:00 -0000 [thread overview]
Message-ID: <CAKmqyKNwLO=JoKQbYApktOQFJcdeOzavW8E2EQjqCOHfhYi3=A@mail.gmail.com> (raw)
In-Reply-To: <b2ef4dde-fd34-5619-f300-a364394036a6@redhat.com>
On Wed, Sep 25, 2019 at 1:08 PM Carlos O'Donell <carlos@redhat.com> wrote:
>
> On 9/25/19 1:50 PM, Christopher Faylor wrote:
> > On Wed, Sep 25, 2019 at 09:19:57AM -0700, Alistair Francis wrote:
> >> On Wed, Sep 25, 2019 at 8:22 AM Carlos O'Donell <carlos@redhat.com> wrote:
> >>>
> >>> On 9/25/19 10:07 AM, Christopher Faylor wrote:
> >>>> On Tue, Sep 24, 2019 at 10:11:28PM -0700, Alistair Francis wrote:
> >>>>> Overseers,
> >>>>>
> >>>>> Please add me (alistair23) to the glibc group after verifying with
> >>>>> carlos@redhat.com.
> >>>>>
> >>>>> carlos@redhat.com vouches for my sanity and competence.
> >>>>>
> >>>>> I truly understand FSF copyright protocols, and always respect
> >>>>> per-branch policies on what I am allowed to touch and how.
> >>>>
> >>>> An account was just added for you for the glibc project yesterday.
> >>>
> >>> Perfect. Does that mean we're all done?
> >>
> >> I'm not sure, according to
> >> https://sourceware.org/glibc/wiki/MAINTAINERS I still need to have
> >> write permission added.
> >
> > When you were provided with an account in the glibc project you were
> > put in the glibc group.
> >
> > After reading the above link, I can see why you thought that you needed
> > an additional step. That web page does seem to instruct that you have
> > to send email here. That's not required, however. The only reason to
> > send email here is if you already have an account on sourceware and are
> > not a member of the glibc project. Otherwise, the new project form is
> > enough.
> >
> > Could someone change wording at https://sourceware.org/glibc/wiki/MAINTAINERS
> > be tweaked to avoid this understandable confusion?
>
> Tweaked. Please review?
>
> https://sourceware.org/glibc/wiki/MAINTAINERS#Becoming_a_maintainer_.28developer.29
That is clearer.
Maybe it's worth adding a note about people who already have accounts
and want to join a new project?
Alistair
>
> --
> Cheers,
> Carlos.
>
next prev parent reply other threads:[~2019-09-25 20:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 5:12 Alistair Francis
2019-09-25 14:07 ` Christopher Faylor
2019-09-25 15:22 ` Carlos O'Donell
2019-09-25 16:24 ` Alistair Francis
2019-09-25 16:43 ` Carlos O'Donell
2019-09-25 17:50 ` Christopher Faylor
2019-09-25 20:08 ` Carlos O'Donell
2019-09-25 20:45 ` Alistair Francis [this message]
2019-09-25 21:04 ` Carlos O'Donell
-- strict thread matches above, loose matches on Subject: below --
2013-10-09 19:53 Torvald Riegel
2013-10-09 19:55 ` Frank Ch. Eigler
2012-07-02 18:46 GLIBC " Maxim Kuvyrkov
2012-07-02 19:09 ` Roland McGrath
2012-07-09 13:23 ` Ian Lance Taylor
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='CAKmqyKNwLO=JoKQbYApktOQFJcdeOzavW8E2EQjqCOHfhYi3=A@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=carlos@redhat.com \
--cc=overseers@sourceware.org \
/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).