Hello! I’m planning on stepping down from Typing Council. It’s been about a year since Jelle and I wrote PEP 729. It was always my intention to cycle membership — I think it’s great to get people involved. I’ll still be around… one of several nice things about how the Typing Council has played out in practice is how little of the work actually requires being on the Typing Council. As a corollary, I encourage people to contribute to the conformance test suite, improve guides and tutorials, review PRs to python/typing, identify areas of underspecification or divergent behaviour in impls, etc
Quoting from PEP 729:
If there is a vacancy and there are three or more remaining members, it is up to the Council to decide whether to appoint a new member. To determine replacements, nominations will be collected from the typing community. Self-nominations are allowed. The existing Typing Council will then decide the replacement member(s) from the nominees. The expectation is that this would be done by fiat, but the Typing Council can choose a replacement by any means they see fit, including a vote.
If you have people (including yourself) you’d like to see on the Council, please reply to this thread (or send me a discourse DM, or email me at hauntsaninja at gmail). We’ll wait one week for nominations. And while I’m here, please also get in touch if you have any feedback on the Typing Council.
And while I’m here, please also get in touch if you have any feedback on the Typing Council.
Not exactly a feedback, but I would appreciate it if you could have a look at #35 before stepping down (the sign-off list has your name specifically!).
There are no formal requirements (see the “spec” in PEP 729 – Typing governance process | peps.python.org). In practice, every member so far has been a maintainer of a type checker, a CPython core developer, or both, but I’d be open to adding a member who is not a current maintainer of a type checker but has a track record of contributions to the typing ecosystem.
What’s the criteria for being in the typing council?
Since the Typing council will be making technical decisions that affect multiple stakeholders, presumably the criteria should include:
being a typing expert
having a history of engaging productively with some of the stakeholders
With respect to expertise, the starting list of topics is a guide. If a person doesn’t know what these words mean, then being on the typing council might not be a good idea:
I’d like to nominate myself as a candidate. The Council’s activity is work I’ve been following with a lot of interest, and the work building the new typing spec is something I’ve already spent a reasonable amount of time participating in and reviewing.
My typing CV includes:
CPython core developer, and maintainer of the stdlib typing module, for nearly two years
Maintainer of typeshed for several years
Maintainer of the typing_extensions package
Longtime triager with mypy
Currently part of a small team building a new type checker for Python at Astral
I’d like to nominate @JukkaL. It’s a simple statement of truth that Python typing would not be the same without him. I think his perspective, experience and work on mypy would be valuable on Typing Council. On a personal note, I’ve learnt a lot about open source as a result of Jukka.
On behalf of the Typing Council, I am happy to announce that we have invited Jukka Lehtosalo (@JukkaL) to join us and take Shantanu’s seat. As the creator of mypy and one of the originators of typing in Python, he brings an extremely valuable perspective to the Typing Council. Thanks Jukka for agreeing to serve.
Thanks also to Shantanu for his many contributions to the Typing Council, and thanks to the other candidates who stepped forward to nominate themselves.
