3 ms·
A Mess in the Python Community
- floxy 2y agoI wonder what Tim thinks of Javascript. Seems like it keeps getting better.
- zahlman 2y agoYou could probably ask him privately by email - it's not hard to find the address and he seems unusually receptive to that sort of thing. That said, personally I don't think JavaScript is very Pythonic at all. Implicit type conversions create a huge mess (and TypeScript is, as far as I can tell, really the same kind of system as Python's new type annotations, but built on a shakier foundation).
- dekhn 2y agoSo if I infer correctly, the SC wants to remove Tim's fellow status due to historical behavior that people have complained about, but haven't really clarified with enough detail for the larger public to see the details to judge on their own, and in the meantime, Tim got involved in the rules change discussion and acted in a way that the SC didn't like, so they banned him (this is partly guesswork, as the SC didn't name Peters, nor give extensive details about the ongoing, persistent words or behaviors he used). If the SC was more forthright about the facts, they might manage to succeed here. However, their actions run the risk of alienating a lot of the community, such as those of us who have an extremely high tolerance for passionate people on the internet.
- zahlman 2y ago> this is partly guesswork, as the SC didn't name Peters Not really; there was clearly only one such suspension, and Peters publicly identified himself as the recipient. > nor give extensive details about the ongoing, persistent words or behaviors he used Well, yes, that's the point: they haven't clarified anything, but left several hints with obvious referents that imply a complete BS cause of action. And when called on this, the people responsible fall back to a nebulous claim that these are only examples of some supposed pattern of behaviour. Peters' conduct and phrasing throughout all of this, from what I have seen, have been exceptionally diplomatic. It's night-and-day different to the conduct that led to Stefan Krah's suspension (and subsequent resignation) in 2020 (https://mail.python.org/archives/list/python-committers@python.org/thread/ZIAN7ERZNF4ZE2B2SLYNRPVNERNACG5A/ https://mail.python.org/archives/list/python-committers@pyth...) - but even that situation, I believe, could have been avoided by better, less tone-deaf, more cognizant-of-neurodiversity handling earlier on.
- SpecialistK 2y agoThis line really highlights what I find to be unworkable within the situation: > Brendan Barnwell was also concerned that, based on ""the tenor of the comments from the moderation team/SC/PSF board"", the decision essentially comes down to: ""'If Person A does something and Person B interprets that in a way they find objectionable, it is automatically (or at least by default) Person A who must accept they are in the wrong.'"" But that is not fully reflecting the code-of-conduct guideline of ""'being [respectful] of differing viewpoints and experiences'"", he said. Sometimes Person B needs to rethink their interpretation too. It doesn't take much imagination to see how that could be abused.
- zahlman 2y agoIt comes across to me that they were quite explicit in framing the proposition that "Person B might need to rethink" as a petition for neurodivergent people to be "cut more slack" (i.e. be allowed to get away with stuff). It was very much not respectful of neurodivergence and they, at best, completely missed the point of Tim Peters' thread (https://discuss.python.org/t/how-can-we-better-support-neurodivergent-newcomers-to-the-community/58724 https://discuss.python.org/t/how-can-we-better-support-neuro...) while browbeating him into several edits to something that was already highly supplicative. They also deleted his comment from https://discuss.python.org/t/python-s-supportive-and-welcoming-environment-is-tightly-coupled-to-its-progress/59232 https://discuss.python.org/t/python-s-supportive-and-welcomi... after mere minutes, which started out with praise and offered only the mildest imaginable, completely constructive criticism. (The thread was locked almost a month later as part of a generic cleanup effort, even though nobody else had commented. One wonders why they didn't lock it immediately if that's how they planned to respond to any feedback whatsoever.)
- zahlman 2y agoRepeating my main point from last time (full comment at https://news.ycombinator.com/item?id=41543176 https://news.ycombinator.com/item?id=41543176): One thing that annoys me about the coverage is that it seems unaware of clear misrepresentations made by the CoC Work Group and the Steering Council related to this affair. In particular, they have repeatedly falsely insinuated that individuals like Peters and myself have tried to determine the identity of accusers or expected them to explain those accusations concretely. This is simply false. What I would appreciate, however, is for the CoC Work Group to explain properly how any person could in principle object to certain of the "examples that attempt to summarize an overall communication style that pushed boundaries too far", or what those supposed "boundaries" are or why they should exist, or indeed how any of that could possibly have "caused harm to multiple people in our community". Another key issue is that they mischaracterized complaints by, or on behalf of, neurodivergent individuals, as petitioning for said community members to be treated more leniently or with some other kind of favouritism. This, too, is not true. The goal, instead, was to get them to understand that neurodivergent people - more or less by definition - cannot be expected to infer the standards of behaviour that they're refusing to lay out explicitly, and do not see how the supposedly problematic conduct could be judged as violating the Code of Conduct as written.
- Hendrikto 2y ago> Utilizing emojis and turns of phrase in ways that can be misconstrued or perceived entirely differently by different people. Ridiculous. Absolutely anything can be misconstrued. As Peters said: > If you're determined to take offense, offense is what you'll find. > When someone tells you something said earlier was problematic, listen. That is not an opportunity for debate. That is an expression of pain. It is time to stop and reflect upon what has happened. Also ridiculous. Guilty by accusation, without even the possibility of proving one‘s innocence. > SC member Emily Morehouse pointed out that it is often difficult to communicate what led to a specific code-of-conduct action. If you cannot even explain your actions, it is very likely they were not justified, and you should not have taken them. > But it is not really a surprise that Peters is already missed. Serhiy Storchaka asked about contacting Peters for his technical expertise, which Wouters seemingly discouraged; Storchaka specifically said he was not trying to route around the SC decision, but might be able to continue to work with Peters through GitHub. Meanwhile, in a thread about possible changes to the voting system for SC elections, Guido van Rossum noted that the voting-system expert he knows is banned: "Maybe we can wait until his 3-month ban expires and ask him for advice?" Great way to get rid of technically excellent and highly valued contributors… what a shame.
- deleted 2y ago[deleted]