The #WordPress contributor Slack is turning into a clusterfuck.
-
Dylan </closingtags.com>replied to Terence Eden on last edited by [email protected]
@Edent The thing that frustrates me with this drama is the reasoning "Well its Matt's project. He can do what he wants with it."
That's such a slap in the face to the countless hours put in by all of the contributors that poured their souls into a project because they believed in the mission. WordPress was supposed to be bigger than Matt.
-
@Edent
"Why are you in this Slack, then?"
...holy crap the attitude on that dude. -
@Edent this Matt guy is uh, pretty embarrassing. His blog post where he flexes about buying out employees that don't agree with him is, wow. Just wow.
I never heard of the guy until all this started happening with WordPress, I wonder who else is learning of his existence through this lens of bizarre, childish behavior?
Seems like they really need to restructure things and unblur some lines so that he's not in charge of, y'know, the whole damn thing.
-
@Edent 🫡🫡🫡
-
As tediously predicted. Had lots of positive reactions to my message. But, of course, no dissent is tolerated in Open Source…⸮
Why do these tech-bros have such thin skins?
-
Pedro Machado Santareplied to Terence Eden on last edited by
@Edent I don't even... that's brutal.
-
@Edent I'm absolutely not suggesting you to blog the whole story and post it to HN, but I may
it if you do it 
-
@andreagrandi
Thanks. I think enough pixels have been bled over this. -
…DSAR sent to to WordPress's GDPR team regarding this decision.
I wonder if they'll actually comply with the law?
-
@Edent this whole palaver melts my brain and I'm sorry to see you're impacted. What a farce.
-
@Edent I'd like to suggest that it's not Open Source that has a no dissent policy. Suggesting that is disparaging everyone who works in Open Source, the vast majority of whoem are level headed and willing to hear disagreement.
-
Of course, the continuing #WPDrama reminds us that there really is no need for a centralised "app store".
The #WordPress plugin directory is useful for *discovery*. But it probably makes more sense for plugins and themes to update from their own site / git rather than a capricious host.
-
@Edent centralized repositories aren't perfect, but I'd argue they are extremely important for your average WP user because they are well vetted. Having a repository of free apps that are easy to search, review, and consistently be able to find details like "last updated" is so handy. The most important feature though, was that users didn't have to run through the tools themselves to look for malicious code.
Without a central repository, most beginner WP users might avoid installing plugins. -
@docpop
The problem is, that vetting doesn't exist.I used a popular plugin which, at some point, was compromised. The bad version was uploaded to the WP directory. WP then delivered it to my blog where it started serving malware to my users and creating compromised admin accounts.
The directory isn't as well vetted as, say Google Play.
-
@Edent The advantage I saw was some assurance of code quality & security as plugins were vetted & devs got some viral benefit to help build a plugin user base. If some community effort could go into a true NFP run plugin repositry that could satisfy growth & security without enabling theft in the future
-
@dalereardon the problem is, the WP directory doesn't actually do much code validation. Dodgy plugins with malware are frequently uploaded.
-
frank goossens 🇧🇪🇪🇺replied to Doctor Popular on last edited by
@docpop @Edent maybe @AspirePress can help us improve there?
-
Apparently the DPO at WordPress thinks messages related to a decision taken about me are exempt because… they're *internal* messages.
Well, yeah, I can read my public messages. I want to know what they said about me.
No doubt it'll bat back and forth until I have to get a regulator involved.
-
I finally got WordPress's DPO to see sense!
Looks like Matt is the sole arbiter of who gets to use the WordPress community slack.
