The reality is that no one is more concerned about the impact of AI on society than the people who are building it. Almost always, the more someone knows, the higher his or her concern level is.
Some might ask, “Isn’t it their fault? Aren’t they the ones building the technology that is going to replace workers?” But technologists, VCs, and entrepreneurs are simply doing all they can to push their companies and products forward. It is not their fault that the gains are being concentrated in the hands of a very few, and it’s nearly impossible for them to know and account for the downstream social and economic impacts. It’s OUR job—that is, it’s the responsibility of our government and leaders to account for the impact of innovation on human well-being.
Unfortunately, we are decades behind. And we need to speed up fast.
One investor said something to me on Tuesday that struck me as profound. “At this point, we don’t even need much more technological innovation. We could be busy for a long time just applying the tech we already have. What we really need is much more social innovation.” He’s on to something. He’s a good man who is supporting my campaign. And there are many others like him.Andrew Yang – Yang 2020
This was originally posted on make.wordpress.org/hosting.
Looking for something to do at Contributor Day? We could use your help!
The Gutenberg Migration Guide is a crowdsourcing project to document WordPress Classic Editor customization points and their Gutenberg equivalents (if such exist).
media_buttons is the quintessential example; whereas you might’ve used this action previously in the Classic Editor to register a button, it no longer exists in Gutenberg and the block inserter is its direct equivalent.
We want the migration guide to be as comprehensive as it can be. This is defined as:
- Identifying as many integration points as we can find. For instance, there are already 14 actions / filters listed. Some are commonly used, while others are not. As long as we have a good example for how the integration point is used, it makes sense to include in the guide.
- Whenever possible, documenting how feature parity can be achieved with Gutenberg. Some integration points do already have Gutenberg equivalents. Others don’t yet, and that’s alright.
You can help make the migration guide more comprehensive. If you don’t have any examples of your own to include, here are a couple of places you can start looking:
- Our plugin compatibility database has a good number of plugins marked incompatible. Some even have descriptions of the problems!
- The [Type] Plugin / Theme Interoperability and Backwards Compatibility labels in the Gutenberg GitHub repository have some number of reasonably documented conflicts.
Everyone can contribute to the migration guide, regardless of skill set. All you need to do is open a new GitHub issue and report the incompatibility you’ve found. Screenshots and GIFs are tremendously helpful. If you know the underlying problem, then please include that too. If all you know is that a given plugin’s feature doesn’t work in Gutenberg, no worries; simply open an issue and we can help track down the cause. Identifying examples of breakage are what we need help with most.
Feel free to join
#hosting-community in the WordPress.org Slack if you have any questions, etc. Thanks for your help!
Want to have a huge impact on Gutenberg’s rollout to a larger number of users? Here are some high value issues that would benefit from a pull request over the next week:
- Persist custom CSS classes during block conversion when block supports additional classes
When a WordPress user converts existing HTML to a block, or manually edits the block HTML to include a class, we should persist their custom CSS class into the additional classes field.
- Autosaving somehow triggers a full save when metaboxes exist, causing too many revisions
Gutenberg 3.0 included a bunch of new autosave functionality that still needs some work. Track down this bug before Adam Silverstein does!
- Drag and drop uploading should respect WordPress multisite max upload size
We need to make sure file size is validated both client-side and server-side. Felix Arntz started a patch for core that we’ll want to land in Gutenberg first.
Drafted last time I flew and to be revised next time.
- Board the plane last, to maximize your use of airport wifi and minimize sitting in the plane seat.
- Walk everywhere you can, because you’re probably sitting otherwise. If the opportunity comes up to walk two miles to your next destination, take it without hesitation.
- Drink water at every opportunity. You are more likely to get dehydrated while traveling, and dehydration can ruin your trip.
- Minimize alcohol and sugar consumption. The golden amount is zero / zero. If you need to consume one, you’ll probably want alcohol for the social occasions over sugar.
- TSA Pre is the easiest way to not hate the airport. I’m typically through a security checkpoint in under two minutes.
- Bring lunch from home for your first day of travel. If possible, also bring non-perishable snacks from home for throughout the trip.
Not quite, but almost.
On Saturday, I ran the Spray Half to the tune of 1:48:22.
It was a great event and I was really happy with my performance. Notably, I hit faster and faster splits in the last five miles: 8:19 (mile 9), 8:02 (mile 10), 7:44 (mile 11), 7:51 (mile 12), and 7:23 (mile 13).
We left Spray on Sunday but we weren’t done yet.
On Monday, Leah and I subjected Ava and Charlie to a grueling ~14 mile hike around Timothy Lake.
For better or for worse, this is the epitome of our marriage — “should we turn around now?” is left unanswered and we keep going. Fortunately, our kids are more hardcore than we are.
An A+ Memorial Day weekend for the year in review book.
ADU legislation, pro-housing density efforts, software eats retail, and PDX exploring.
- ADU Legislative Initiatives Abound (Kol Peterson) — While Senate Bill 1051 is requires all cities to “allow ADUs”, the Oregon Department of Land Conservation and Development guidance recommends dropping owner occupancy requirements, dropping off street parking requirements, allowing detached ADUs up to 800 sq ft by right, and even allowing two ADUs.
- ‘My Generation Is Never Going to Have That’ (POLITICO)— Pro-housing density efforts in Seattle from the affected tech population. See also Jeff Kaufman (Boston) and Kevin Burke (California).
- Mickey Drexler and the death of a supply-driven world (Loose Threads) — Software eats retail: how J.Crew, Gap, Ralph Lauren, Abercrombie & Fitch, American Apparel, and others were blindsided by technology.
- Pedaling from Portland to Hood River (Bike Portland) — Neat 100 mile bike route off the beaten path.
Still need guidance getting your site ready for Gutenberg?
On Tuesday, June 5th at 10 am PT, I’m heading up a webinar with Pantheon to cover how you can get your site ready. More specifically, we’ll cover:
- How to formulate a testing plan.
- Common Classic Editor customizations and their equivalents.
- What to keep an eye out for in the near future.
But wait, there’s more! The webinar is just one in a series of five, including Mel Choyce and Josh Pollock. You should sign up so Tessa and I aren’t terribly lonely on June 5th.
This post originally appeared on make.wordpress/core.
Since I last wrote two weeks ago, we’re making progress! Key achievements for Gutenberg and the REST API include:
- Support for
who=authorswas added to
GET wp/v2/users, making it possible to accurately query for authors. WordPress, for better or for worse, defines an author as
user_level!=0. See WordPress/gutenberg#6361 for the context on why we can’t add this logic client-side (#42202 for WordPress 4.9.6).
- Improved performance for the
_fields=query parameter (e.g.
GET wp/v2/pages?_fields=id,title) by ensuring WordPress core will only process the fields requested for the response. Notably, this helps us avoid running
the_contentwhen we don’t need to be (#43874 for WordPress 4.9.7).
- Minor enhancements to reflect existing WordPress behaviors:
- Disables the Preview button when post type isn’t viewable (WordPress/gutenberg#6232 for Gutenberg 2.7)
- Filters the Post Format list to only formats that are supported (WordPress/gutenberg#6296 for Gutenberg 2.8)
- Only displays Featured Image UI when theme supports it too (WordPress/gutenberg#6541 for Gutenberg 2.8)
The “Merge Proposal: REST API” GitHub milestone represents the distance we still need to close. Slowly, steadily, we’re bridging the gap, but we could use your help. Here are some of the issues we’re still working through:
- To ensure all necessary data is available to Gutenberg, we’ve settled upon permitting unbounded
per_page=-1REST API requests for authorized users. This landed for
GET wp/v2/users(WordPress/gutenberg#6627), is in-progress for
GET wp/v2/(pages|blocks)(WordPress/gutenberg#6657), and needs to be addressed for categories, tags, and custom taxonomies. We also need to patch core with this enhancement (#43998 for WordPress 4.9.7?)
- Capabilities can’t be processed directly client-side (WordPress/gutenberg#6361), so we’ve introduced a new
targetSchemaconcept to communicate which actions a user can perform. See it in action with
wp:action-assign-author(WordPress/gutenberg#6630). There are a few other actions we will need to work out, and then we’ll need to patch core (no ticket yet).
- Adam is putting together an improved autosaves implementation (WordPress/gutenberg#6257) that I literally cannot wait to see complete. I’m sure he could use some help testing in the near future.
- Felix is implementing a
WP_REST_Search_Controllerendpoint (WordPress/gutenberg#6489) to power the link search UI.
Join us tomorrow, Thursday, May 10 at 17:00 UTC in
#core-restapi office hours if you’d like to chat through any questions you have.