Terry Reedy and me propose to promote Cheryl Sabella as a core developer. To vote, please reply with “+1” or “-1” (it’s even better with a short message). I propose to open the vote for 1 week. If you prefer to wait longer, please explain why.
Cheryl made significant enhancements in IDLE. She mostly worked with Terry Reedy, I somehow mentored her (not really on technical stuff, more on the workflow). She proved her long term commitment (active for 1 year 1/2), good programming skills and the ability to discuss the find a proper solution.
Her first commit was at Aug 14, 2017. I counted that she got 81 commits merged into master between August 2017 and February 2019. Great job!
I gave her the bug triage permission in December 2017: Cheryl Sabella was promoted to get bug triage permission. Cheryl is very helpful on the bug tracker: she is able to properly understand issues and proposes a concrete action to move the issue forward. She told me that she likes to click on button to get a random issue until she finds an issue that she can help
–
I wanted to propose to promote her earlier (2 months ago), but I decided to wait until Python has a new governance and elects a new Steering Committee. Previously, it would put more pressure on the promotion vote, since the new governance gives more responsibilities to core developers: they are now more involved in the governance, like the vote to elect committee members.
When I first asked Cheryl if she would like to become a core dev, she said no. It is the first time in my experience with contributors that someone said no to me. IMHO it’s a great quality of Cheryl Obviously, she now accepted that I propose to promote her
The PEP 13 explains a little bit how and when a contributor becomes a core dev: https://www.python.org/dev/peps/pep-0013/#membership “It is granted by receiving at least two-thirds positive votes in a core team vote and no veto by the steering council.”
Victor
UPDATE: I fixed a typo.
UPDATE 2: Cheryl got 65+16 commits merged into master. I missed her first 16 commits made under a different Git author.
+1 vote for @csabella I have reviewed her patches too and found it always complete. She will be a great addition to the group of developers and I hope she keeps enjoying contributing to CPython.
Also, thank you @vstinner and @tjreedy for recognizing Cheryl’s contributions and pushing for her promotion.
Enthusiastic +1. She has done wonderful work. Thanks @tjreedy for the outstanding job mentoring and @vstinner for encouraging and bring this to a vote.
+1 from me. I worked with Cheryl on many issues, I’ve been following their triaging work on bugs.python.org, and code reviews on GitHub for more than a year. IMO, Cheryl’s contributions (active on bugs.p.o, doing code reviews, caring about documentation, and writing high quality code) are a great example of what we should look for when promoting contributors in the future.
(I was planning to create a thread myself last year, but I was quite busy planning my relocation.)
I can’t imagine anyone who has been following cpython development in recent times could in good conscience not vote +1 for @csabella, So let’s just get on with it!
Looking forward a bit, I wonder if the topic of promoting committers is something the steering committee is likely to take on. @willingc?
@vstinner, obviously the whole process of how we decide to give “commit-bit” privileges to people is an extremely important one as the role of Python core developer has traditionally come with a lot of assumptions about responsibilities, duties, and authorities. We’ve had a lot of informal discussions about the role over the years so it seems to me to be potentially a natural and important topic for the steering committee
.
