Although WP Engine must win the legal battle, for the strength of the ecosystem, we need to build a stronger Foundation to win the war.
journal.rmccue.io/438/a-stroβ¦
That is correct. I started and lead the WP REST API project until merging into core. I also wrote the Requests HTTP library which powers WP_HTTP, the core of the systems powering developer.w.org, and other contributions.
It speaks volumes that the "big group of heavy hitters in the WordPress project" who signed this letter felt they had to stay anonymous. There is such a culture of fear that it is stifling. therepository.email/wordpresβ¦
βThe culture of WordPress in the past few weeks has become a culture of fear among senior and established contributors.β
therepository.email/core-conβ¦
Excited to announce three new React tools/libs for WordPress: react-wp-scripts (create-react-app for WP), Repress (WordPress + Redux = β€οΈ), and react-oembed-container (to fix your Twitter/etc embeds). humanmade.com/2018/03/12/ourβ¦
You do not need to distribute physical copies of GPL software or sell support in order to charge for software. The FSF's own FAQ covers this: gnu.org/licenses/old-licenseβ¦
Itβs clear that we need a change in #WordPress, and that has to start with proper leadership. We have to do something to save this project.
I fully support this effort by @jdevalk and @karimmarucchi.
It's clear the #WordPress world needs a change. So I wrote a post about exactly that:
Breaking the Status Quo: A vision for a new WordPress era
buff.ly/4grFfIA
We've hit problems with WordPress sites with lots of users, so @joe_hoyle's experimenting with moving roles to taxonomies. Anyone else hit the same issue? github.com/humanmade/roles-tβ¦
For clarity, I have never worked at Automattic. There are also many people who left or stayed there for reasons unrelated to the current situation, so I would not judge anyone on the basis of that decision. :)
We built a brand new Publication Checklist plugin from the ground up for the block editor: github.com/humanmade/publica⦠- One of our headline features in Altis v2!
(Proper release post coming soon.)
We specifically designed the API schemas to be independent of the implementation, so should be fairly easy. (My hope was that itβd become a de facto standard for CMSes.)
Although I don't currently have access to the WP Slack, I am still here :) My hope remains that we can get back to some sense of normalcy - I just want to get back to work!
To help the WordPress ecosystem push forward into a user-friendly future, Automattic, XWP, the AMP team and Google have formed a unique collaboration to bolster the plugin capabilities & enable full AMP experiences by default!
#AMPConf YouTube playlist β goo.gl/Fu1Yy7
#AMPConf - Fast by default: AMP powering WordPress
Watch the #AMPConf recorded sessions on the AMP YouTube Channel!
Did some experimentation with the navigation components in Gutenberg, based on the existing work in WooCommerce, as a standalone plugin. Give it a try! github.com/rmccue/experimentβ¦
In the lead up to State of the Word at #wcus, I figured it was a good time to look back with a State of the REST API in 2017: journal.rmccue.io/380/state-β¦
Thanks to @jrf_nl, Requests for PHP has a new home: github.com/WordPress/Requestβ¦ - living under the WP GitHub organisation means less bus factor on me, and hopefully a bright future βοΈ
I've had no communication about either case, and most of my work on the WP Slack was in DMs or private channels (like the security channels). I keep my personal opinions separate to my work in any case. :)
Iβve said it before, but it bears repeating: the ONLY way for open communities to function is through respectful, honest discourse.
This fear suppresses any real discussion and is paralysing the project and community.
Nowadays, plugin search in #WordPress admin suggests a product/add-on. I see the future of these suggestions to be used by plugin authors to keep their product first in certain plugin search terms for upsells like admin notices.
What do you think about this? #DontHijackWPAdmin
Something I feel is constantly underestimated is the work involved in productionising cool things. Building sustainable, scalable, operational things is hard.
But moreover, donβt let anyone tell you how to work. Explore and be curious, but donβt feel like any less of a developer just because youβre not using something; do what works for you.
Regardless of whether this is an actual βwe should remove thisβ statement or not, this is just toxic behaviour, and is harmful to the whole ecosystem.
So we spend months building a @WordPress plugin for Unsplash and then @photomatt comes in and says it shouldn't be listed in the plugins directory, even though it absolutely meets all the criteria, because he doesn't like the Unsplash License?
Putting it out there: if youβre speaking about the WordPress REST API at any event (meetup, WordCamp, or other conf), I am always happy to help, edit, review, or answer Qs.
What prevents the Foundation from using a subsidiary organisation, such as WordPress Community Support PBC? Such a setup seems to work for addons.mozilla.org. (I am not sure how the PSF hosts commercial packages on pypi.org if disallowed for 501c3s.)