[Bug 288064] Antisemitism and hate speech in official FreeBSD wiki
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 288064] Antisemitism and hate speech in official FreeBSD wiki"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 11 Jul 2025 13:07:59 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288064 --- Comment #9 from Mark Linimon <linimon@FreeBSD.org> --- Status report. fwiw, if I knew how to lock PRs so that no further comments could be made, I would have done that the first evening this PR came in. I think we are now at private email #30 or so. We have gotten to the "well, what is the wiki _for_, anyway" stage. The underlying problem is that we had never defined Terms & Conditions for using the wiki. In fact, it was stood up years ago as an experiment, with the unstated assumption that it would be strictly about technical topics, and that contributors would collaborate. And so now we are in a position where we are demanded to iterate over Terms & Conditions, and then, "language-lawyer" over what all that means. I will state my extremely strong opinion that none of this improves the quality of any of our software or documentation. Those are my chief interests and the reasons why I have stayed with the Project so long. Also, as hard as it may be to believe, both dch@ and I have had real-world responsibilities that we had already scheduled, during the last 48 hours. I have done my best to hold my temper with everyone commenting here but I have to admit right now I am finding it hard to do so. Anyone who thinks a bunch of computer nerds will be able to solve real-world problems that have frustrated all attempts over the years, probably needs to go take a good, hard, look in the mirror. I continue to search for some wording that will allow everyone to feel "heard" but frankly it seems impossible. I would like to ask that everyone take a breath and avoid further comments while dch@ and I work on the issue in the meantime. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.