| https://www.linkedin.com/in/rachellewise/ | |
| GitHub | https://github.com/WiseArts |
| CodePen | https://codepen.io/wisearts |
| https://www.linkedin.com/in/rachellewise/ | |
| GitHub | https://github.com/WiseArts |
| CodePen | https://codepen.io/wisearts |
Today my WordPress.org account was disabled unexpectedly. I did not request that and I have received no communications with reasoning ahead of time or at the time of that being disabled (like most people who were deactivated on Slack or .org disabled).
This puts the @pods project at risk on .org since we've used the security best-practice of having release confirmations enabled on the Pods plugins on .org since they added that feature. To confirm a release, you must log into .org
With all this talk about bullying in WordPress, I was inspired to βopen-sourceβ some receipts from my recent experience with bullying in #WordPress.
Because βthe only way to deal with a bully is to fight.β
IRT findings re: https://www.wpwatercooler.com/2023/09/22/a-call-for-accountability-sharing-my-wordpress-code-of-conduct-report/
Matt quote from: https://www.therepository.email/mullenweg-threatens-corporate-takeover-of-wp-engine
π£ Hey #WordPress community!
Contribute to .org? STRIKE. β
Pay for Jetpack? Cancel your subscriptions. β
Pay for Akismet? Cancel your subscriptions. β
Take back WordPress!
We need collective action. Otherwise, we have no power.
I propose a boycott of Automattic products.
#WordPress MUST NOT be burned down from the whims of an out-of-control leader.
Like many in web development, Wordpress has been a semi-regular feature in my professional life and, for most of it, my impression was that it suffered from the usual infighting and mismanagement you see in free or open source software, but that it was otherwise as well run as you could expect of a long-running project built on layers and layers of legacy code.