Even though I agree with your sentiment that this event was not handled correctly in many ways, I don’t feel that a “vote of no convidence” is the appropriate measure. I simply don’t believe that bad intentions played part in the process, which would make it a viable approach.
That said, I also don’t believe that the SC should be in charge of handling CoC cases or implementing any related actions at all. This should be solely in the realm of the PSF Board.
The SC should focus on what it’s best set up for, namely managing the Python programming language design and it’s CPython reference implementation.
I’m working on a longer proposal to address the process issues uncovered by the recent events. This will address and clarify the roles in our overall governance setup, the interactions between the PSF and the SC, as well as make suggestions for governing the PSF communication resources in a more ordered and transparent way, with the hope of getting us on a better track for helping the community grow.
Part of this will be to update PEP 13 and remove the power to “Enforce or update the project’s code of conduct”, as mentioned above.