From: Philippe Chaintreuil <gentoo_bugs_peep@parallaxshift.com>
To: gentoo-proxy-maint@lists.gentoo.org
Subject: Re: [gentoo-proxy-maint] [RFC] New doc & policy
Date: Fri, 21 Jul 2017 10:36:28 -0400 [thread overview]
Message-ID: <e80a2f30-c9bd-95ae-0342-d9d53c0e96a4@parallaxshift.com> (raw)
In-Reply-To: <1500584775.746.11.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1445 bytes --]
On 7/20/2017 5:06 PM, Michał Górny wrote:
> On czw, 2017-07-20 at 10:02 +0200, Michał Górny wrote:
> Here's v2, taking into account suggestions from k_f and wraeth:
> ==How to become a proxied maintainer==
This whole section seems to assume a lot of knowledge of infrastructure
that I don't think someone wanting become a proxy-maintainer will have.
It also seems to me that it has a lot of "all you need to do is this one
simple thing", followed by 3-4 reasons there will be other things you
need to do before that one simple thing. This section would do better
with a checklist of steps followed by explanations of "why" as needed in
my opinion.
Imagine being a total neophyte and seeing "maintainer needed" on a
package you have a vested interest in. What is your first step of
contact? The current text makes me think that it's a cold-called
Pull-Request planting your flag in the metadata.xml. Is that the
intention? Or should people be joining this mailing list and getting a
list of things that will need to be fixed before that pull-request?
Also, if proxy-maintainers taking control of existing packages are more
common than creating new packages, it would seem to me that section
should come first.
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.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
next prev parent reply other threads:[~2017-07-21 14:36 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 [this message]
2017-07-21 18:16 ` Michał Górny
2017-07-24 17:59 ` Philippe Chaintreuil
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=e80a2f30-c9bd-95ae-0342-d9d53c0e96a4@parallaxshift.com \
--to=gentoo_bugs_peep@parallaxshift.com \
--cc=gentoo-proxy-maint@lists.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