georgehotelling
Joined 13 years ago
Joined 13 years ago
Can you share a link? I haven't been able to find that. A prohibition on contributions seems like a bad policy, because at some point WP Engine will want a change in Core and they need the political capital to make that happen.
However, if they can influence the direction of the project, they can align it with your business goals. That gives them a competitive advantage, that gives them an incentive.
The challenge is that Matt is acting as a BDFL of the open source project. If Matt doesn't want your change added, your change isn't going to get added. There is no one to appeal to, Matt has absolute authority over the code that goes into the open source project that WP Engine's business is built on. Matt is also the CEO of WP Engine's competitor, Automattic.
This conflict of interest has come to a head in the past week and shone a spotlight on the lack of community stewardship of the WordPress project.
Keep in mind that Automattic requires its employees to get approval for any paid side gigs related to software because Matt believes that it creates conflicts of interest. You cannot work on WordPress for Automattic during the day and then freelance making paid WordPress plugins at night, due to the misaligned incentives. The fact that Matt isn't being paid a salary for his work on WordPress is irrelevant, given Automattic's equity is tied to the value of WordPress.
I think private equity skews heavily towards value extraction over value creation. I think that people who build businesses off of open source have a moral obligation to give back to the projects. I think that giving Automattic money to spend on WP core work will make WordPress better.
However, breaking the trust of the community does exponentially more damage to the future of WordPress than any freeloading company. The community trusts that the trademark licenses will not change to target them. The community trusts that their software will benefit from security updates and the plugin ecosystem. That trust is the foundation of WordPress and this week's actions have done damage.
Matt talked about going nuclear, and I think that the metaphor is apt, because when the smoke clears we may be left with no winners.
(I'm a former Automattic employee who roots for open source, WordPress, Automattic, and the vision of the open web Matt Mullenweg has shared.)
I've read that is what the underlying precipitation "models" did as well, but obviously can't confirm.
I recommend everyone sharing social media links to see what it looks like in a private browser window, because the logged out experience is usually bad and sometimes unusable.
The paperless-ngx's core team focused on gathering a group of people to support it to avoid any burnout problems and keep the project sustainable.
That's actually why I landed on Home Assistant. It's Open Source so I know that if things ever go bad someone will fork it and I won't have invested deeply in a dead-end ecosystem.
Getting started for me felt like the first time I learn a new board game. The rules seem incomprehensible and everything is unfamiliar, but that's the price of trying something new. Eventually the concepts started to click and I saw how things fit together.
I will say that telling my spouse to install an app with a web GUI was much easier than it would have been to get her on IRC to control the house.
I would be interested if OP could glean enough from GPT to build the search index as well, a much more complicated project.
I'm pretty sure that pre-dated Futurama too.