This doesn't directly affect the software as it currently stands.
It's mainly about the organisation. The people in charge have some a sequence of things that have increasingly alarmed people who care about the organisation of the project. More people are getting interested in what has happened with each step. This is one of the latest actions where even the key person who started Python has been impacted. This shows that the actions they were doing are important and worthy of attention as anyone who interacts within the organisation is within the reach of potential impact. No-one is untouchable. Outside though to the rest of us it's not directly impactful currently.
So then there is the impacts on wider things like software. As you say the community can just vote out the ones they dislike and vote in a new bunch. To me and many others, this sounds it should solve the situation. However I think some others see the problems as systemic, where the actions taken are a result of how the management organisation is structured and so the problems will occur again even if new people were in charge. If that's the case then more of a change might be demanded which could affect the software. (But in what ways is unclear)
On a HN scale, there's a wider sociological and cultural issue of how large open source software projects should be organised. And this is an example showing the problems of certain approaches especially as certain things were directly for reducing abuse and yet seem to be used in an abusive way. For many here on HN who are in various communities with similar structures, seeing what happens here is very important to them. There is a varying amount of personal investment in this story about the users own lives more than Python itself.
It's mainly about the organisation. The people in charge have some a sequence of things that have increasingly alarmed people who care about the organisation of the project. More people are getting interested in what has happened with each step. This is one of the latest actions where even the key person who started Python has been impacted. This shows that the actions they were doing are important and worthy of attention as anyone who interacts within the organisation is within the reach of potential impact. No-one is untouchable. Outside though to the rest of us it's not directly impactful currently.
So then there is the impacts on wider things like software. As you say the community can just vote out the ones they dislike and vote in a new bunch. To me and many others, this sounds it should solve the situation. However I think some others see the problems as systemic, where the actions taken are a result of how the management organisation is structured and so the problems will occur again even if new people were in charge. If that's the case then more of a change might be demanded which could affect the software. (But in what ways is unclear)
On a HN scale, there's a wider sociological and cultural issue of how large open source software projects should be organised. And this is an example showing the problems of certain approaches especially as certain things were directly for reducing abuse and yet seem to be used in an abusive way. For many here on HN who are in various communities with similar structures, seeing what happens here is very important to them. There is a varying amount of personal investment in this story about the users own lives more than Python itself.