[python-committers] Requirements / Guidelines for module maintainers? [was: PEP 594]

2019-05-31 Thread Ethan Furman

Greetings!

I have a non-core dev willing to help maintain the cgi/cgitb modules along with 
myself.

Would this consist of adding the both of us as experts on those modules, and 
then I would be responsible for the mechanics of approving/merging any PRs?  
Assuming this individual does well we should make them a core-dev at some 
point, but presently they have no experience contributing to the Python 
codebase.

--
~Ethan~
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/


Re: [python-committers] Requirements / Guidelines for module maintainers? [was: PEP 594]

2019-05-31 Thread Brett Cannon
On Fri, May 31, 2019 at 11:33 AM Ethan Furman  wrote:

> Greetings!
>
> I have a non-core dev willing to help maintain the cgi/cgitb modules along
> with myself.
>
> Would this consist of adding the both of us as experts on those modules,
> and then I would be responsible for the mechanics of approving/merging any
> PRs?


I don't think there's anything technically preventing folks who are not
core devs from being added there, but I would expect them to at least be
triagers as they will get nosied on appropriate issues.


>   Assuming this individual does well we should make them a core-dev at
> some point, but presently they have no experience contributing to the
> Python codebase.
>

I assume it would be the same as what Barry is doing with two other folks
on the 'email' package: treat it like a mentoring situation and if they
work out you an put them forward to become a core dev.
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/