Carol's also served on the PSF board of directors for a number of years. +1

Alex

On Tue, May 23, 2017 at 2:15 PM, Brett Cannon <brett@python.org> wrote:

While at the PyCon US sprints the idea came up of offering Carol Willing developer privileges. Everyone at the table -- about 6 of us -- liked the idea and Carol also said she would happy to become a core dev, so I'm officially putting her forward for consideration.

For those of you who don't know Carol, she basically knows our developer workflow better than most of us. :) ; she's very active on the devguide and core-mentorship. Carol has also attended the PyCon US language summit two years in a row as a representative for the Jupyter project. She is actually so good with new people that she managed to get my wife to make her first open source contribution (something I never managed to do).

As usual, if you support/object to this idea, please say so. :)

---

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/

-- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: D1B3 ADC0 E023 8CA6

I was impressed with Carol’s leadership at HackIllinois

+1

On 23 May, 2017, at 14:15, Brett Cannon <brett@python.org> wrote:

As usual, if you support/object to this idea, please say so. :)

---

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 Tue, May 23, 2017 at 11:15 AM, Brett Cannon <brett@python.org> wrote:

While at the PyCon US sprints the idea came up of offering Carol Willing developer privileges. Everyone at the table -- about 6 of us -- liked the idea and Carol also said she would happy to become a core dev, so I'm officially putting her forward for consideration.

For those of you who don't know Carol, she basically knows our developer workflow better than most of us. :) ; she's very active on the devguide and core-mentorship. Carol has also attended the PyCon US language summit two years in a row as a representative for the Jupyter project. She is actually so good with new people that she managed to get my wife to make her first open source contribution (something I never managed to do).

As usual, if you support/object to this idea, please say so. :)

+1

-- Zach

On 23May2017 1115, Brett Cannon wrote:

While at the PyCon US sprints the idea came up of offering Carol Willing developer privileges. Everyone at the table -- about 6 of us -- liked the idea and Carol also said she would happy to become a core dev, so I'm officially putting her forward for consideration.

For those of you who don't know Carol, she basically knows our developer workflow better than most of us. :) ; she's very active on the devguide and core-mentorship. Carol has also attended the PyCon US language summit two years in a row as a representative for the Jupyter project. She is actually so good with new people that she managed to get my wife to make her first open source contribution (something I never managed to do).

As usual, if you support/object to this idea, please say so.

+1. Would love to have Carol in a position where she can mentor contributors all the way through to completion, and I trust that she'll use her powers for good :)

Cheers, Steve

tl;dr +1 for me as well

2017-05-23 13:15 GMT-05:00 Brett Cannon <brett@python.org>:

For those of you who don't know Carol, (...)

To be honest, I just met Carol at the Pycon US (yeah! that's the purpose of such event, no?). I wasn't aware of her amazing work on CPython. The thing is that I'm a "code" nerd: I basically ignore everything related to CPython, except of the code in the CPython repository.

With the amazing work done on the CPython workflow *leaded* by Brett Cannon (Brett was also helped by a cool task force made of many people doing many tasks all around), I realized that CPython is *much* larger than just the code. Well, a friend is trying to explain me that for years, but well, I'm slow :-)

Let me explain differently:

• if you remove the team who maintained bug tracker, users will be unable to report new bugs or to reply -- sadly, issues on the authentication occurs often (every 6 months?) for an unknown reason, but hopefully it's always fixed quickly

• if you remove the core-workflow team, CPython would still be using patch files attached to our bug tracker, we would still have to run tests manually and hope (did I say pray?) that only a few buildbots will break, etc. Well, I don't think that it's worth it to elaborate on that part, the new workflow became so simple for contibutors *and* core developers to publish, review and merge changes!

• if you remove the PyPI, haha... it's hard to imagine that, but ok, let's say that pypi.python.org doesn't exist: trust me, the Python community would simply not exist and Guido would have to serve his lord Larry Wall (fear!).

• if you remove python.org... how would you get Python? how do you find the documentation? where are the latest Python news? how can I get information on Pycon events? etc.

• if you remove buildbots, Python wouldn't be at that quality level

• if you remove the security team, Python wouldn't be used in some area for good reasons

• if you remove the Python infra team, say hello to PyPI down time, "hey! is PyPI working for you?" -- do you recall this old time which was no so long ago?

• if you remove Pycon events, ...

• if you remove mailing lists and our postmaster, ...

• ...

Sorry, I have to catch my flight, so I cannot finish my list, but I guess that you now got my point :-)

So to come back to Carol: she is very active on mentoring newcomers, guide them, take time to write kind emails, and obvious she helps a lot on the devguide. Carol told me that she wants to start working on the CPython documentation. Promoting her would only encourage that.

Same rationale for my previous vote to promote Mariatta, I expect that mentoring and documentation would be a trampoline to extend their interest in other areas. (I'm not saying that it's a requirement, just that being recognize for our work gives good feeling and helps to remain motivated since it's sometimes hard to write a change or to a get a change merged.)

I hope that Carol would be an example for us to promote other people working hard in CPython but remaing in the shadow of the "code" cloud.

I also expect that getting more core dev in other areas than the code will help to notice active contributors to mentor them and maybe later promote them as well as core dev.

As Barry reminded me in the keynote, the Python community is also kind and welcome thanks to humour and the Monty Python. So I would like to share that song with you:

https://www.youtube.com/watch?v=SJUhlRoBL8M

/And...always look on the bright side of life.../ /Always look on the light side of life.../

Victor

On 23 May 2017 at 19:15, Brett Cannon <brett@python.org> wrote:

While at the PyCon US sprints the idea came up of offering Carol Willing developer privileges. Everyone at the table -- about 6 of us -- liked the idea and Carol also said she would happy to become a core dev, so I'm officially putting her forward for consideration.

For those of you who don't know Carol, she basically knows our developer workflow better than most of us. :) ; she's very active on the devguide and core-mentorship. Carol has also attended the PyCon US language summit two years in a row as a representative for the Jupyter project. She is actually so good with new people that she managed to get my wife to make her first open source contribution (something I never managed to do).

As usual, if you support/object to this idea, please say so. :)

Definitely +1 from me. Paul

On May 23, 2017 11:23, "Brett Cannon" <brett@python.org> wrote:

While at the PyCon US sprints the idea came up of offering Carol Willing developer privileges. Everyone at the table -- about 6 of us -- liked the idea and Carol also said she would happy to become a core dev, so I'm officially putting her forward for consideration.

For those of you who don't know Carol, she basically knows our developer workflow better than most of us. :) ; she's very active on the devguide and core-mentorship. Carol has also attended the PyCon US language summit two years in a row as a representative for the Jupyter project. She is actually so good with new people that she managed to get my wife to make her first open source contribution (something I never managed to do).

As usual, if you support/object to this idea, please say so. :)

Even when considering this is not a reward for her awesome work, but rather enabling her to do more, as well as applying peer pressure to actually *do* more... Yes, +1 ;-P

On 05/23/2017 11:15 AM, Brett Cannon wrote:

While at the PyCon US sprints the idea came up of offering Carol Willing developer privileges

I've always been impressed with her interactions.

+1

-- ~Ethan~

On 24 May 2017 at 04:15, Brett Cannon <brett@python.org> wrote:

While at the PyCon US sprints the idea came up of offering Carol Willing developer privileges. Everyone at the table -- about 6 of us -- liked the idea and Carol also said she would happy to become a core dev, so I'm officially putting her forward for consideration.

For those of you who don't know Carol, she basically knows our developer workflow better than most of us. :) ; she's very active on the devguide and core-mentorship. Carol has also attended the PyCon US language summit two years in a row as a representative for the Jupyter project. She is actually so good with new people that she managed to get my wife to make her first open source contribution (something I never managed to do).

As usual, if you support/object to this idea, please say so. :)

Definite +1 from me (I was actually thinking of emailing Carol about the idea before I saw this thread)

Cheers, Nick.

-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia