X-post: Design team weekly update October 7th

X-post from +make.wordpress.org/updates: Design team weekly update October 7th

X-post: Design team weekly update September 4th

X-post from +make.wordpress.org/updates: Design team weekly update September 4th

X-post: Gutenberg testing planning group chat

X-post from +make.wordpress.org/test: Gutenberg testing planning group chat

X-post: Community Conduct Project – Kick off meeting scheduled for 17:00 UTC on the 5th September 2017

X-Post from +make.wordpress.org/updates: Community Conduct Project – Kick off meeting scheduled for 17:00 UTC on the 5th September 2017

X-post: Design team weekly update 14th August

X-post from +make.wordpress.org/updates: Design team weekly update 14th August

X-post: Editor Focus & Paternity Leave

X-post from +make.wordpress.org/design: Editor Focus & Paternity Leave

X-post: Call for testing: Gutenberg

X-post from +make.wordpress.org/test: Call for testing: Gutenberg

4.1 development is under way

WordPress 4.1 development is under way. See the release schedule for the key dates.

Here’s an overview of the headline features for this release. If you’d like to get involved with mockups, design, development, documentation, testing – anything really – see the users and tickets listed below each item.

Other areas which will receive attention during this release:


Summary of 5 7 dev chat IRC log…

Summary of 5/7 dev chat (IRC log):

Proposed 4.0 ideas

  • Multisite enhancements: SSL, get site creation/editing UIs in line with the arbitrary domain/path support. Planning on weekly office hours.
  • Mobile experience: media modal and upload flow, Press This feature plugin.
  • oEmbed discoverability, usability, and caching improvements.
  • Widgets: JS API (#28093)
  • Taxonomy roadmap, part one.
  • Background images in the customizer.
  • Plugin installer improvements: better search and more information (needs .org API support), upgrading a plugin or theme via zip upload (#19641)
  • Export API improvements/overhaul (#22435)
  • Post meta: support for revisions (#20564)
  • APIs for posts/comment types/statuses. Ping @nacin if interested in collaborating (#12706).
  • Continuous a11y enhancements, particularly in the media modal.
  • Texturize patches, continuing on performance enhancements and bugfixes in 3.9.

If you are interested in any of the above, sound off in the comments below.

Potential themes for the release:

  • More visual cues in the admin for user tasks, as has been done for themes.
  • Continuing to improve the editing and media experiences.
  • Lots of under the hood things and API attention to make devs happy.

Feature Plugins

  • Front-end Editor looks like it’ll continue past 4.0, as enabled by being a feature as a plugin, but we should continuously keep an eye on it and see what improvements can be brought into core sooner.
  • Media Grid View and Press This are under way.
  • WP API continues to move forward.

Patches needing early dev attention

  • #17689: Terms should not be sanitized inside term_exists(). This is the first step in moving along with the taxonomy roadmap, so please look here if this has been of interest to you. Potentially needs more unit tests. Thanks to @aaroncampbell for the latest patch.
  • #14759: Improve the way oEmbed deals with caching (patch from @markjaquith).

And finally, 3.9.1 is out now, if you haven’t already updated or been updated.

#4-0, #dev-chat

Summary of last week’s dev chat on 4…

Summary of last week’s dev chat on 4/30 (IRC log):


Features as plugins

  • Met on 4/29 (IRC log)
  • Current potential considerations seem to be WP API and media grid.
  • Press This is getting some attention from an early stages working group, which could also be a part of the 4.0 release.
  • Admin Help is poised to shift into more of a continuous testing and advisory group, which is awesome.
  • Front-end editor is making good progress, but has UX issues that are getting worked on, needs iteration and experimentation and probably won’t be ready by 4.0, but should continuously be worked on, as is the goal of features as plugins in the first place. Developers needed.

Potential ideas and their suggesters:

Summary: we have good things in mind about more media improvements, more editing experience improvements, more visual media grid and better plugin installer experience (following in the footsteps of themes), and behind the scenes wins in taxonomy, multisite, and post type and comment APIs.

If you’re interested in any of the above or have other ideas, please sound off in the comments.

Getting involved

  • We are always looking for more people to be involved with Trac gardening, patch review, patch writing, or some combination thereof.
  • Component pages are running well, and most could still use the caretaking of a component owner or somebody who’d like to become well-versed in a particular area of core. To get started, just sign up for component notifications at https://make.wordpress.org/core/notifications/. No need to be an expert now – learning and persistence is more important.To help with a specific plugin, join their weekly chats and/or follow along wherever they post. See the Features as Plugins page for more information.
  • A reminder from @matt to always be dogfooding the product – use WordPress every day.

Bonus punnage, to the lead’s chagrin:

wonderboymusic will make a t-shirt for anyone who gets all 16 of those Cache tickets closed 🙂
> sams: “Cache Master”?
> wonderboymusic: Johnny Cache
> jorbin: If you fix the Cache, you’ll get the Credit. That Checks out.
> MarkJaquith: I’d put in a cache pun, but I don’t want to be sent to purgetory.
> johnbillion: You would have to be a cache machine to fix all 16

#4-0, #dev-chat