- Promote Stéphane Wirtel
- Don’t promote Stéphane Wirtel
Julien Palard and me (Victor) propose to promote Stéphane Wirtel as core developer. We open a vote until March 31 (~one week). “[A promotion] is granted by receiving at least two-thirds positive votes in a core team vote and no veto by the steering council.”
Some of you already met him at Pycon US or EuroPython.
Stéphane is contributing to Python since 2014. He fixed bugs in various parts of the code, but also implemented some nice features:
- -d option of “python3 -m http.server -d DIRECTORY” to serve a specific directory using Python builtin HTTP Server
- –fast and --best options on gzip CLI: “python3 -m gzip [options] file”
(Julien told me that he frequently uses “python3 -m http.server -d DIRECTORY” to read the Python documentation :-))
In my experience, Stéphane likes getting review and is fine to make any change on his code. It’s not an issue to work with him, it’s more the opposite For example, he doesn’t get mad if one of his PR is rejected (I’m saying that because I sometimes get mad about that, sorry for being emotional :-))
He got 57 commits merged into the master branch of Python: authored 46 commits + co-authored 1 commit + 10 commits before Git (“Patch written by Stéphane Wirtel”).
He organized a Python conference at FOSDEM 5 times in a row (between 80 and 800 persons per year) and got a PSF Community Service Awards in June 2016 for that: “Stéphane Wirtel for his work organizing a Python User Group in Belgium, for his continued work creating marketing material for the PSF, for his continued outreach efforts with spreading the PSF’s mission.”
He is also helping to organize EuroPython, by working on the website or being a volunteer on-site.
He gave a lot of Python talks all around the world at many Pycon (France, EuroPython, Canda, Italy, Ireland, UK, San Sebastiàn, Slovakia, Ukraine) and at FOSDEM (Belgium). For example, he gave talks about Python internals (bytecode, parser), and on Python development workflow and Pull Requests.
He is always volunteer to help the Python project, not only the code. For example, he is a committer on the developer guide (devguide).
He is helping other contributors get their bugs fixed or to get their changes merged. He participated to not less than 218 PR: ping the right core dev who can review/help, test manually to validate and provide good feedback, propose enhancements, etc. Sometimes, he just says “Thank you for your contribution” which is IMHO a good practice for a healthy community (we don’t do that often enough!)
Stéphane is involved in Python for 5 years. To be honest, he should have been promoted earlier, but I (Victor) wasn’t sure to promote him myself because I know him too well, and so I wasn’t objective about his work. But well, now it’s time, and Julien is supporting his promotion as well
I offer to mentor Stéphane once he would become a core dev for 1 month for help him to deal with his new responsibilities. I would require him to ask me before merging any PR during the mentoring.
Julien and Victor