From: Philippe Chaintreuil <gentoo_bugs_peep@parallaxshift.com>
To: "Michał Górny" <mgorny@gentoo.org>, gentoo-proxy-maint@lists.gentoo.org
Subject: Re: [gentoo-proxy-maint] [RFC] New doc & policy
Date: Mon, 24 Jul 2017 13:59:20 -0400 [thread overview]
Message-ID: <40890c05-a6c5-5361-1203-96373f03aa0c@parallaxshift.com> (raw)
In-Reply-To: <1500660995.29801.4.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 754 bytes --]
On 7/21/2017 2:16 PM, Michał Górny wrote:
>> Additionally, I'd like to see a section on what a new proxy-maintainer
>> should do when they need help. Especially when working in
>> "maintainer-needed" ebuilds where it's not obvious.
>
> Isn't the team contact data (IRC, e-mail) enough on the top project
> page? Remember that this is the page you would supposedly hit second,
> after reading the top project page [1]. Note that the section on getting
> started there will be updated to match the changes in this doc.
>
> [1]:https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers
Apologies, I thought this was replacing that page too. If that's the
case, then it greatly alleviates my worries from the previous e-mail.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
prev parent reply other threads:[~2017-07-24 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 8:02 [gentoo-proxy-maint] [RFC] New doc & policy Michał Górny
2017-07-20 8:33 ` Kristian Fiskerstrand
2017-07-20 15:02 ` Michał Górny
2017-07-20 9:36 ` Sam Jorna
2017-07-20 15:15 ` Michał Górny
2017-07-21 5:11 ` Sam Jorna (wraeth)
2017-07-20 21:06 ` Michał Górny
2017-07-21 5:14 ` Sam Jorna (wraeth)
2017-07-21 5:29 ` M. J. Everitt
2017-07-21 14:36 ` Philippe Chaintreuil
2017-07-21 18:16 ` Michał Górny
2017-07-24 17:59 ` Philippe Chaintreuil [this message]
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=40890c05-a6c5-5361-1203-96373f03aa0c@parallaxshift.com \
--to=gentoo_bugs_peep@parallaxshift.com \
--cc=gentoo-proxy-maint@lists.gentoo.org \
--cc=mgorny@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