On May 13, 2019, at 01:14, Victor Stinner <vstinner@redhat.com> wrote:
> I'm no longer sure myself that I can define them. I prefer to repeat
> what others say :-) Basically, a core developers is someone who
> produces commits :-) That's one definition.
But, IMHO not a correct one. The full quote from PEP 13:
——snip snip——
Python core team members demonstrate:
• a good grasp of the philosophy of the Python Project
• a solid track record of being constructive and helpful
• significant contributions to the project's goals, in any form
• willingness to dedicate some time to improving Python
As the project matures, contributions go beyond code. Here's an incomplete list of areas where contributions may be considered for joining the core team, in no particular order:
• Working on community management and outreach
• Providing support on the mailing lists and on IRC
• Triaging tickets
• Writing patches (code, docs, or tests)
• Reviewing patches (code, docs, or tests)
• Participating in design decisions
• Providing expertise in a particular domain (security, i18n, etc.)
• Managing the continuous integration infrastructure
• Managing the servers (website, tracker, documentation, etc.)
• Maintaining related projects (alternative interpreters, core infrastructure like packaging, etc.)
• Creating visual designs
Core team membership acknowledges sustained and valuable efforts that align well with the philosophy and the goals of the Python project.
——snip snip——
I’m quite convinced that both Mark and Abhilash meet these requirements. And they are almost by definition the experts in the email package. You can certainly see the nature of their work in the Mailman repos, and I would be willing to mentor them through the first few commits to the CPython repo, though I think it will be mostly perfunctory.
> Having a sustainable Mailman project is great. But how does that
> relate to Python itself? Are you talking about the email module? Do
> Mark Sapiro and Abhilash Raj plan to maintain the email module?
Yes, that is the intent.
> In the meanwhile, they don't have to be core devs to help to maintain
> the email module, no?
Do we have any core developers who want to maintain it? Not me :) and apparently not RDM.
I think these two make sense as email module maintainers from a demonstrated domain expertise point of view.
But you'll probably have an easier time convincing others who want to see some PRs first if you just go ahead and have them do some work on the email module in the form of PRs to start with. ie: Don't let being dubbed core developers or not yet block you from starting to mentor them on initial email module maintenance.
-gps
-Barry
_______________________________________________
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/