[python-committers] RFC: Process to become a core developer

Terry Reedy tjreedy at udel.edu
Fri Dec 8 15:06:39 EST 2017

On 12/8/2017 11:20 AM, Victor Stinner wrote:
> 2017-12-08 14:19 GMT+01:00 Ezio Melotti <ezio.melotti at gmail.com>:
>> In my opinion, the role of the mentor should boil down to:
>> 1) be a reference for the new core dev and be available in case
>> everything else fails (e.g. if no one else answers a question);
>> 2) be responsible for the mistakes the new core dev might make (e.g.
>> help fixing up a bad merge or a broken buildbot caused by the new core
>> dev).
>> The mentor shouldn't babysit the new core dev and be in the only point
>> of contact.
> I can only agree with you on these points :-)
>> The new core dev should:
>> 1) interact with the other core devs and the community in general;
>> 2) reach to the mentor only when necessary (i.e. no one else replied,
>> something import/urgent/"personal").
> Hum, maybe the process document should give a few pointers to the
> proper place to ask questions at each step? For example,
> core-mentorship before coming a core, and then maybe more on
> python-committers after becoming a core?

Committers should not ignore core-mentorship for general technical 
questions.  Core-mentorship is where I finally got an answer on how to 
get tkinter working with a repository build -- from a non-coredev.  At 
least one non-coredev contributed answers to my questions about using git.


More information about the python-committers mailing list