This is related to the proposal made in Adopting the concept of "Teams" (from PEP 8015), that Python move away from having groups with names like “XYZ Authority” / “XYZ-SIG” / “XYZ community” to a single naming style – “XYZ team” – where each team is SC-ratified.
As I understand it, the effect that this proposal would have on Async-SIG is a renaming (to something like “Async Team”) and that it would get listed in the list of SC-approved teams. How do existing members of Async-SIG feel about such a renaming?
FWIW, currently, Async-SIG is an example of a group that doesn’t strictly conform to the “definition” of the word it uses (SIG), as defined today on the python.org website:
It does not have a charter or coordinator (as far as I can tell).
Why change things? That will just confuse people who are used to this existing group. What problem are you trying to solve? It sure sounds like a case of “refactor code because I don’t understand it”.
I am aware of that discussion and I am tired even just reading about it. Given Paul Moore’s response I’m not the only person who thinks that way. And thanks for the trip down to memory lane – it helps me to understand you better. I am not changing my opinion though.