On pią, 2017-07-21 at 10:36 -0400, Philippe Chaintreuil wrote:
> 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?

I will try to reword but I can't promise I will achieve much. I'd like
to avoid starting with a lot of 'if's.

> 	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.

I don't want to prioritize either. Right now the order is purely
lexical.

> 	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

-- 
Best regards,
Michał Górny