Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggested amends regarding the "pdoc3" controversy #347

Closed
wants to merge 1 commit into from

Conversation

FergusInLondon
Copy link

Apologies for the rather drab PR, but considering the discussion in issue #330 (courtesy of @saifkhichi96) I was wondering whether this would be a suitable compromise?

This aims to provide additional context to the situation regarding pydoc3 - whilst being more sensitive to the cultural significance of the symbolism involved. It aims to:

  • convey the conduct of the hostile fork in a factual manner,
  • still provides sign-posting to the original discussion,
  • and does so without the insensitivities currently contained in the README.

Rather than typing lengthy discussion posts on the issue, I thought it may be more worthwhile if I attempted to suggest a compromise that could satisfy both parties. I hope this PR is taken in the spirit it's intended - and that's the spirit of inclusivity and sensitivity to a topic that has perhaps been distorted/conflated.

This aims to provide additional context to the situation regarding pydoc3 - whilst being more sensitive to the cultural significance of the symbolism that has sadly been conflated with something quite different. It's with some irony that the existing text states that "everyone is treated with respect"-  but there's been a lack of meaningful dialogue over quite a sensitive topic. There's a full discussion in issue mitmproxy#330.
@mhils
Copy link
Member

mhils commented Feb 10, 2022

See #330 (comment).

@mhils mhils closed this Feb 10, 2022
README.md Show resolved Hide resolved
@FergusInLondon
Copy link
Author

Well that's sad, I was hoping this would've expanded on the situation whilst also being respectful.

It's quite surprising to see the cultural and religious importance explained, as well as examples of the symbolism in use in a modern context, and still be met with a refusal. The comment that you link to is also - once again - insensitive, and by suggesting that the faiths in question only belong to one region, you're erasing an entire diaspora as well as the faith of millions of converts. I suspect a look at a map of Buddhist and Hindu temples would contain many surprises.

There's some irony that the paragraph in question contains "healthy community where everyone is treated with respected" - perhaps a more accurate update would contain the obvious exceptions of those belonging to the Hindu or Buddhist faiths, or those originating from regions of South Asia.

I think I'll leave it there, and whilst I can't say I have any respect for the decision (or understanding behind it), I understand it's your prerogative. I'll remain hopeful that discussions amongst the other maintainers will lead to a more inclusive and respectful path.

@mhils
Copy link
Member

mhils commented Feb 10, 2022

@FergusInLondon: I'm sorry to hear that you feel my comment is insensitive. My point in closing this PR (and now locking it) is not to reject your changes right away, but to let emotions cool down and then discuss possible changes both internally and with folks who are impartial.

@mitmproxy mitmproxy locked as too heated and limited conversation to collaborators Feb 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants