* The dev team has a disagreement about putting one of the company’s own projects on the available plugins carousel or whatever inside their main product.
* They eventually decide not to.
* The CEO says “this has been an important part of our product for 20 years. It’s silly that we’re even debating this”, and put it there anyway.
And that’s about it? Based only on what I read here, there wasn’t any compelling engineering reason not to do a thing, and the CEO made a product decision to do it. That sounds like something I’ve heard 1,000 times at different shops and I’m not sure what the problem is.
Perhaps I’m misreading this, and the main point isn’t “CEO overrides valiant dev team”, but “CEO makes recalcitrant dev team stop bikeshedding”.
I say this out of no love for Matt’s… “interesting”… decision making the last couple of years. This sounds reasonable to me though.
But it seems the clean, sustainable, long-term way to do this was to have the akismet plugin simply self-register. Why was this hack easier than just doing that?
Comment spam is terrible and will continue to get worse.
Decent alternatives exist.
Increasing the visibility of Akismet should help increase revenue.
This is 100% a financial move.
AlienRobot•40m ago
>Fueled-sponsored core committer Peter Wilson
>Bluehost-sponsored core committer Jonathan Desrosiers
>Human Made-sponsored core committer John Blackbourn
This is a terrifying way to describe people.
mooreds•29m ago
renewiltord•24m ago
nixosbestos•22m ago
When I did OSS work paid for by my employer, I was careful to note and credit who paid for the PR.