public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>, proxy-maint@gentoo.org
Subject: Re: [gentoo-dev] Gentoo-dev whitelisting
Date: Sun, 13 May 2018 15:38:43 -0400	[thread overview]
Message-ID: <CAAr7Pr8F0spT=6R0RST2_iPePM5eEz90ji1i9Q6Y=tM+Ta2Jng@mail.gmail.com> (raw)
In-Reply-To: <CAJW3Cey1-uZbZinnfV-=zr8mHNm7iaP4xe_mx4=7itvU=xb7CA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]

On Sun, May 13, 2018 at 3:23 PM, Geaaru <geaaru@gmail.com> wrote:

> Hi,
>
> I'm not a gentoo dev but currently I have an official issue to
> bugs.gentoo.org as proxy ebuild maintainer for same packages.
>

Contact proxy-maint@gentoo.org and ask that they sponsor you.

We may want to consider just whitelisting all proxy-maintainers; proxy
maint, is there a list someplace?

-A


>
> What is the right process for require insert of my email in whitelist?
>
> Thanks in advance.
>
> G.
>
>
> On Sun, May 13, 2018, 20:57 Alec Warner <antarus@gentoo.org> wrote:
>
>> Dear Gentoo Community,
>>
>> Gentoo-dev whitelisting[1][2] is nearly ready for deployment. The new
>> posting guidelines to post on gentoo-dev@lists.gentoo.org the following:
>>
>>  - You must be a member of the list to post.
>>  - You must be on the whitelist to post.
>>
>> The whitelist automatically whitelists all @gentoo.org addresses.
>> Additions of addresses to the whitelist can be made by any developer. To
>> modify the whitelist, please read this wiki page for instructions:
>>
>> https://wiki.gentoo.org/wiki/Project:Infrastructure/
>> Mailing_Lists#Managing_the_Gentoo-Dev_whitelist
>>
>> [1] https://bugs.gentoo.org/650964
>> [2] The whitelist is not yet live, but I wanted to give folks an
>> opportunity to populate the whitelist before enabling it; so have at it.
>>
>>
>>

[-- Attachment #2: Type: text/html, Size: 8075 bytes --]

  reply	other threads:[~2018-05-13 19:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13 18:57 [gentoo-dev] Gentoo-dev whitelisting Alec Warner
2018-05-13 19:01 ` Toralf Förster
2018-05-13 19:05   ` Alec Warner
2018-05-13 19:06     ` Alec Warner
2018-05-13 19:23 ` Geaaru
2018-05-13 19:38   ` Alec Warner [this message]
2018-05-13 19:51     ` Geaaru
2018-05-13 20:17 ` [gentoo-dev] Re: [gentoo-project] " Kristian Fiskerstrand
2018-05-13 21:25 ` [gentoo-dev] " Paweł Hajdan, Jr.
2018-05-13 21:28   ` Alec Warner
2018-05-14  5:35     ` Michał Górny
2018-05-14  6:59       ` Paweł Hajdan, Jr.
2018-05-14  5:50 ` [gentoo-dev] Re: [gentoo-project] " Michał Górny
2018-05-14 13:04 ` [gentoo-dev] " Sam Jorna
2018-06-10 19:21 ` [gentoo-dev] " Alec Warner
2018-09-24 20:16   ` Alec Warner

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='CAAr7Pr8F0spT=6R0RST2_iPePM5eEz90ji1i9Q6Y=tM+Ta2Jng@mail.gmail.com' \
    --to=antarus@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=proxy-maint@gentoo.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