It’s a bit late here, so I’ll keep it short-ish:
While I think community governance of and resources for performance work is valuable, I’m not sure I feel the same urgency to start making these big decisions right now. A lot of us are currently traveling and busy with conference activities, so I think waiting at least a couple of weeks for the dust to settle makes sense. For example, I expect to have a lot more clarity around my own role at Microsoft after the conference is over.
Regarding design decisions, community maintainability (and the active solicitation of community involvement) has always been a primary goal of our work. I’ve made this point repeatedly, from the original Brno discussion, to the Christmas Eve PR poem, to PEP 744, and every time I’ve spoken about the JIT since. This is something I think our project did really well, for precisely the reasons that we’re experiencing now.
So I’m not sure that “radical shifts” in our approach are necessary. I still feel personal ownership over much of the work that’s in-flight, and will continue to support it in my personal role as a core dev. I want people to try setting PYTHON_JIT=1 in 3.14, providing feedback, reporting bugs, and making it possible for others to try the JIT downstream, rather than worrying that things are going to start getting ripped out this week or whatever. Progress will be slower, but in my mind there’s really no need for the roadmap to change too much.
Besides, several people I’ve spoken with at the conference plan on sprinting on the JIT with me next week. The community is alive and well. 