Proposed new core developer -- Mariatta Wijaya
Hello all,
Mariatta Wijaya has been working hard to become a Python core developer. At this point she has worked with several of us and I think she has had two dozen or more accepted patches.
She is still green but is persistent, conscientious, and learning fast. She is more willing than most of us to work on the little tasks that so often go unattended.
Do you all think it is time that we accepted our first female core developer? I would like to see that happen before she speaks at Pycon this year and possibly right away if you all are in agreement.
I volunteer to continue to provide mentorship and assistance to her as needed after she is granted commit rights.
Raymond Hettinger
Hi,
I vote +1 for Mariatta Wijaya.
2017-01-26 9:04 GMT+01:00 Raymond Hettinger <raymond.hettinger@gmail.com>:
Mariatta Wijaya has been working hard to become a Python core developer. At this point she has worked with several of us and I think she has had two dozen or more accepted patches.
Oh, I didn't notice her name. I looked at commited changes. Most of them are related to documentation, and a patch to update OpenSSL in the macOS installer.
Sadly, too few developers care of the documentation (I plead guilty!), so yeah, it would be nice to get some help on this area. Around 15% of open issues (894/5736) are in the Documentation component.
Wait, I don't want to restrict Mariatta to documentation! In my experience, developers are able to restrict themself to areas where they feel confident. I guess that slowly she will contribute to the other parts of Python. I recall that my first commited patch was in the documentation, probably as most of us :-)
I volunteer to continue to provide mentorship and assistance to her as needed after she is granted commit rights.
Great! I was going to ask you if you would mentor her, so it's perfect.
Victor
2017-01-26 10:04 GMT+02:00 Raymond Hettinger <raymond.hettinger@gmail.com>:
Mariatta Wijaya has been working hard to become a Python core developer. At this point she has worked with several of us and I think she has had two dozen or more accepted patches.
She is still green but is persistent, conscientious, and learning fast. She is more willing than most of us to work on the little tasks that so often go unattended.
Do you all think it is time that we accepted our first female core developer? I would like to see that happen before she speaks at Pycon this year and possibly right away if you all are in agreement.
I volunteer to continue to provide mentorship and assistance to her as needed after she is granted commit rights.
On what areas she is focused? I never seen her patches.
+1
https://github.com/python/cpython/search?p=1&q=Mariatta&type=Commits&utf8=%E2%9C%93
Her English is definitely better than me :) And I feel it's easy to read for non native speaker.
On Thu, Jan 26, 2017 at 11:04 AM, Raymond Hettinger <raymond.hettinger@gmail.com> wrote:
Hello all,
Mariatta Wijaya has been working hard to become a Python core developer. At this point she has worked with several of us and I think she has had two dozen or more accepted patches.
She is still green but is persistent, conscientious, and learning fast. She is more willing than most of us to work on the little tasks that so often go unattended.
Do you all think it is time that we accepted our first female core developer? I would like to see that happen before she speaks at Pycon this year and possibly right away if you all are in agreement.
I volunteer to continue to provide mentorship and assistance to her as needed after she is granted commit rights.
I'd like to see some triaging, code review and more work on complicated patches first. I reviewed some of Mariatta's patches and they needed at least two review rounds to meet our documentation guidelines. See http://bugs.python.org/issue26149 for a recent example.
--Berker
On 26 January 2017 at 10:17, Berker Peksağ <berker.peksag@gmail.com> wrote:
On Thu, Jan 26, 2017 at 11:04 AM, Raymond Hettinger <raymond.hettinger@gmail.com> wrote:
I volunteer to continue to provide mentorship and assistance to her as needed after she is granted commit rights.
I'd like to see some triaging, code review and more work on complicated patches first.
While I don't have hard data to back it up, my suspicion would be that we have more simple patches pending than we do complicated ones.
I reviewed some of Mariatta's patches and they needed at least two review rounds to meet our documentation guidelines. See http://bugs.python.org/issue26149 for a recent example.
With Raymond volunteering as mentor, I think an approach where changes are still reviewed, but it's Mariatta that does the final commit would work.
That would be pretty similar to the way things worked when I recommended Yury for commit privileges - at the start, the only thing that changed was that the final step in the review process changed from "wait until I find time to commit the change" to "looks good to me, go ahead and make the change".
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
2017-01-26 14:49 GMT+01:00 Nick Coghlan <ncoghlan@gmail.com>:
With Raymond volunteering as mentor, I think an approach where changes are still reviewed, but it's Mariatta that does the final commit would work.
That would be pretty similar to the way things worked when I recommended Yury for commit privileges - at the start, the only thing that changed was that the final step in the review process changed from "wait until I find time to commit the change" to "looks good to me, go ahead and make the change".
Right. When I proposed Xiang Xhang, there was no 100% agreement, but I mentored him and put strong rules for the first weeks. He had to wait for at least one LGTM from another core dev and asks me for a final approval. IMHO it worked well, and Xiang is now autonomous. I now trust him to make the good choices ;-)
Victor
On 26.01.2017 16:52, Victor Stinner wrote:
2017-01-26 14:49 GMT+01:00 Nick Coghlan <ncoghlan@gmail.com>:
With Raymond volunteering as mentor, I think an approach where changes are still reviewed, but it's Mariatta that does the final commit would work.
That would be pretty similar to the way things worked when I recommended Yury for commit privileges - at the start, the only thing that changed was that the final step in the review process changed from "wait until I find time to commit the change" to "looks good to me, go ahead and make the change".
Right. When I proposed Xiang Xhang, there was no 100% agreement, but I mentored him and put strong rules for the first weeks. He had to wait for at least one LGTM from another core dev and asks me for a final approval. IMHO it worked well, and Xiang is now autonomous. I now trust him to make the good choices ;-)
Good approach.
IMO, enabling people to take on responsibility is the best way to create well working teams.
-- Marc-Andre Lemburg eGenix.com
Professional Python Services directly from the Experts (#1, Jan 26 2017)
Python Projects, Coaching and Consulting ... http://www.egenix.com/ Python Database Interfaces ... http://products.egenix.com/ Plone/Zope Database Interfaces ... http://zope.egenix.com/
::: We implement business ideas - efficiently in both time and costs :::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ http://www.malemburg.com/
On 2017-01-26 14:49, Nick Coghlan wrote:
With Raymond volunteering as mentor, I think an approach where changes are still reviewed, but it's Mariatta that does the final commit would work.
+1
I followed some of Mariatta's work. She does a good job. I trust both her and Raymond's judgement to do the right thing (tm).
On Thu, Jan 26, 2017 at 4:49 PM, Nick Coghlan <ncoghlan@gmail.com> wrote:
That would be pretty similar to the way things worked when I recommended Yury for commit privileges - at the start, the only thing that changed was that the final step in the review process changed from "wait until I find time to commit the change" to "looks good to me, go ahead and make the change".
Well, if I remember correctly Yury was already familiar with the internals of inspect module and has produced several high quality patches :)
--Berker
I cast a + 1 vote too.
Positives I imagine are:
- Her motivation to contribute.
- She addresses feedback provided on patches and follows up.
- Raymond's mentorship.
It will be better, if in near future
- She identifies a focus area and becomes an expert in that.
Thanks, Senthil
On Thu, Jan 26, 2017 at 12:04 AM, Raymond Hettinger <raymond.hettinger@gmail.com> wrote:
Hello all,
Mariatta Wijaya has been working hard to become a Python core developer. At this point she has worked with several of us and I think she has had two dozen or more accepted patches.
She is still green but is persistent, conscientious, and learning fast. She is more willing than most of us to work on the little tasks that so often go unattended.
Do you all think it is time that we accepted our first female core developer? I would like to see that happen before she speaks at Pycon this year and possibly right away if you all are in agreement.
I volunteer to continue to provide mentorship and assistance to her as needed after she is granted commit rights.
Raymond Hettinger
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/
On Thu, 26 Jan 2017 at 00:05 Raymond Hettinger <raymond.hettinger@gmail.com> wrote:
Hello all,
Mariatta Wijaya has been working hard to become a Python core developer. At this point she has worked with several of us and I think she has had two dozen or more accepted patches.
She is still green but is persistent, conscientious, and learning fast. She is more willing than most of us to work on the little tasks that so often go unattended.
Do you all think it is time that we accepted our first female core developer? I would like to see that happen before she speaks at Pycon this year and possibly right away if you all are in agreement.
I volunteer to continue to provide mentorship and assistance to her as needed after she is granted commit rights.
+1 from me. She's definitely keen and I don't think there's a worry of her overstepping her knowledge or abilities without asking for help. I've been reviewing her work on the peps repo to port all of the old plaintext PEPs to reST and she's been quick to respond, friendly, and the usual superlatives we want in a core dev. :)
On Jan 26, 2017, at 12:26 PM, Brett Cannon <brett@python.org> wrote:
On Thu, 26 Jan 2017 at 00:05 Raymond Hettinger <raymond.hettinger@gmail.com> wrote: Hello all,
Mariatta Wijaya has been working hard to become a Python core developer. At this point she has worked with several of us and I think she has had two dozen or more accepted patches.
She is still green but is persistent, conscientious, and learning fast. She is more willing than most of us to work on the little tasks that so often go unattended.
Do you all think it is time that we accepted our first female core developer? I would like to see that happen before she speaks at Pycon this year and possibly right away if you all are in agreement.
I volunteer to continue to provide mentorship and assistance to her as needed after she is granted commit rights.
+1 from me. She's definitely keen and I don't think there's a worry of her overstepping her knowledge or abilities without asking for help. I've been reviewing her work on the peps repo to port all of the old plaintext PEPs to reST and she's been quick to respond, friendly, and the usual superlatives we want in a core dev. :)
Thanks Brett. It looks like +1 all around. I'll let her know of the decision (with the caveat for continued mentorship and supervised checkins).
This is a watershed moment for all of us. Everyone should be happy today.
Raymond
participants (11)
-
Barry Warsaw -
Berker Peksağ -
Brett Cannon -
Christian Heimes -
INADA Naoki -
M.-A. Lemburg -
Nick Coghlan -
Raymond Hettinger -
Senthil Kumaran -
Serhiy Storchaka -
Victor Stinner