Hi, 2018-01-25 0:29 GMT+01:00 Eric V. Smith <e...@trueblade.com>: > +1. I actually thought [Nathaniel Smith] was a committer already.
By the way, if you notice an active contributor is good candidate to become a core dev in the long term, you may start the process that I described here: https://github.com/vstinner/misc/blob/master/cpython/pep-core_dev_process.rst My proposed process is made of small steps to build a trust relationship and to train contributors until they produce "commit-ready change". For you, the main requirement is time, be available to review changes and answers to questions by email :-) Last weeks, I looked at contributors who got the most commits merged into master in the last 6 months. That's how I selected Cheryl Sabella, Sanyam Khurana and Pablo Galindo Salgado. I also asked two contributors if they would like to become core, but they declined my offer. I added a new section in my process document: ยง "Becoming A Core Developer Is Not a Goal". I'm not sure that it's the best title ever. """ CPython isn't the easiest place to start. The development process is rather enterprisy with long release cycles (release every 18 months) and rigid backwards compatibility policy. CPython also support many different platforms and CPU architectures. Are you sure that CPython itself is the best project for you? Depending on your interests and skills, you may enjoy better to contribute to another Python project with lower backward compatibility constraints and a faster release cycle. Being a CPython core developer involves responsibilities and usually requires a lot of time. Long-term commitment is also a major expectation, even if it's not a strict requirement. Becoming a core developer should not be seen as a recognition of a contributor work, but more as a constraint :-) Merging a change implies becoming responsible regressions, backward compatibility, security, etc. of this code. It is perfectly fine to contribute to CPython without being a core developer. In most cases, not being able to merge your own work is not a blocker issue. """ I'm not sure about this sentence: "Becoming a core developer should not be seen as a recognition of a contributor work, but more as a constraint :-)". My intent is to discourage people who "want to become a core dev" for the bad reasons (to become famous? I don't know exactly) without understanding the expected responsibilities. Victor _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
