# C API Working Group vacancy

**URL:** <https://discuss.python.org/t/c-api-working-group-vacancy/54015>\
**Category:** C API\
**Created:** [May 23, 2024, 4:49am UTC](https://discuss.python.org/t/c-api-working-group-vacancy/54015 "2024-05-23T04:49:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![guido](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/guido/32/21_2.png) [@guido](https://discuss.python.org/u/guido)\
**Post date:** [May 23, 2024, 4:49am UTC](https://discuss.python.org/t/c-api-working-group-vacancy/54015/1 "2024-05-23T04:49:36Z")

</div>

This is a call for volunteers to serve on the C API Working Group. The WG’s charter was established by [PEP 731](https://peps.python.org/pep-0731/#members). Our founding member Irit Katriel has indicated she’d like to resign her WG membership. We thank Irit for her contributions to the WG’s work, in particular as editor of [PEP 733](https://peps.python.org/pep-0733/) (“An Evaluation of Python’s Public C API”).

According to the [PEP](https://peps.python.org/pep-0731/#operations-and-process), we (the remaining WG members) are calling for nominations from the core developer community (a term I propose to interpret in the widest sense possible).

We will then decide on Irit’s replacement based upon the available nominations. Self-nominations are all right. You can nominate by replying to this message or via email to any of the remaining WG members. I propose that we allow a week to collect nominations (similar to the length of time new-core-dev votes are open, to give people time to respond).

---

<div class="post-metadata">

**Author:** ![erlendaasland](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/erlendaasland/32/4378_2.png) [@erlendaasland](https://discuss.python.org/u/erlendaasland)\
**Post date:** [May 23, 2024, 1:03pm UTC](https://discuss.python.org/t/c-api-working-group-vacancy/54015/2 "2024-05-23T13:03:06Z")

</div>

A big thanks to Irit for all her good work with the PEP and the C API WG!

I’m nominating myself; I’ve reviewed many C API additions, I am a co-maintainer of the [pythoncapi-compat](https://github.com/python/pythoncapi-compat) project, and I have a strong passion for well-designed APIs. I’ve been following the C API WG closely and I would be glad to take Irit’s place.

---

<div class="post-metadata">

**Author:** ![storchaka](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/storchaka/32/217_2.png) [@storchaka](https://discuss.python.org/u/storchaka)\
**Post date:** [May 23, 2024, 4:01pm UTC](https://discuss.python.org/t/c-api-working-group-vacancy/54015/3 "2024-05-23T16:01:53Z")

</div>

I usually hate to participate in various committees, but since I am an active user of the C API and have some experience in the C API development, and participate in some C API discussions in any way, you might consider my candidacy.

---

<div class="post-metadata">

**Author:** ![guido](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/guido/32/21_2.png) [@guido](https://discuss.python.org/u/guido)\
**Post date:** [May 30, 2024, 3:16pm UTC](https://discuss.python.org/t/c-api-working-group-vacancy/54015/4 "2024-05-30T15:16:34Z")

</div>

The remaining WG members have deliberated, and we’ve selected Erlend. Erlend, welcome to the C API WG! We’ll contact you privately with the gory details. Serhiy: you are a strong candidate, and if we have another vacancy you are our number one pick. (And I say that without irony.)

---

<div class="post-metadata">

**Author:** ![storchaka](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/storchaka/32/217_2.png) [@storchaka](https://discuss.python.org/u/storchaka)\
**Post date:** [May 30, 2024, 5:50pm UTC](https://discuss.python.org/t/c-api-working-group-vacancy/54015/5 "2024-05-30T17:50:11Z")

</div>

Agree about Erlend. I nominated myself when there were no other comments. I just took a long time to write my comment. I probably wouldn’t have nominated myself if I seen other nominations.
