Dev Chat Summary, May 20

Agenda, Slack log.

Committers Update (#)
New guest committers: @iseulde, @westonruter, and @obenland, renewed guest committers: @jorbin, @jeremfelt, permanent committers: @pento, @boone, and @johnbillion
Also see

Editor (#)
No update here. Will discuss goals for this week and next week outside of dev chat.

Adminadmin (and super admin) UIUI User interface (#)
@helen is plugging away at some groundwork for the CSSCSS Cascading Style Sheets. roadmap, @stephdau should be taking a look at the first steps for list tables in the next day or so. Will discuss goals for next week in tomorrow’s UI meeting.

Networknetwork (versus site, blog) Admin UI (#)
They talked through aspects of the Edit Sitesite (versus network, blog) and Add Site flows yesterday to help @hugobaeta with mock-ups. Hopeful to see a mock up of these soon. They have a couple flows in Makemake A collection of P2 blogs at, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility)./Flow with more on the way. The 5s flow highlighted an issue with text inputs overflowing. There’s also an updated `WP_Network` patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing..

Things they want to have done by next week:

  • Android and iPad flows.
  • Conversation around updated `WP_Network` patch and a first attempt at `WP_Site`.

Partial Refresh (#)
Now has support for refreshing menus changed by Menu Customizer:
It’s much simpler than partial refresh for widgets, and @westonruter thinks that maybe it could safely be on by default, instead of requiring opt-in as is currently done for widgets. The concern with on-by-default would be if menus get some dynamic behaviors added to them with JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors., so maybe it’s just something that theme authors would need to account for.
Also waiting on feedback and testing from the Menu CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings., merging the corresponding PR for Menu Customizer, to then merge the PR for Customize Partial Refresh and do a new pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software..

Goals for next week: Take what was done for Menus and then abstract a level again to facilitate plugins easily adding their own partial-refreshing.

Menu Customizer (#)
@voldemortensen, @celloexpressions
Lazy loading and error handling were committed. Will discuss goals for next week outside of dev chat.

Better Passwords (#)
They’ve been working on a mockup of the password UI:
Probably best to create a temporary hook in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for the password-set UI in the profile, to allow the team to work on this as a plugin. @markjaquith can take care of that core change, and start the plugin on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner.
#32428 is on hold until the Password UI is usable. @voldemortensen started work on expiring reset keys #32429, but hopes to get it showcase-able by the end of the week. @rmarks made a first pass at #32430 but it needs more work.

Goals for next week:
1. Hook in core to enable plugin for PW change UI.
2. Working version of PW change UI on the Profile screen (that is, you can change your password with it… show/hide… back compatback compat Backward compatibility - a desire to ensure that plugins and themes do not break under new releases - is a driving philosophy of WordPress. While it is a commonly accepted software development practice to break compatibility in major releases, WordPress strives to avoid this at all costs. Any backward incompatible change is carefully considered by the entire core development team and announced, with affected plugins often contacted. It should be noted that external libraries, such as jQuery, do have backward incompatible changes between major releases, which is often going to be a greater concern for developers. for the pw confirmation field… not promising the strength hint stuff yet).
3. #32430 ready for commit.
4. Working patch for #32429.

Favicons (#)
@johnbillion made a start on the site favicon manager. As discussed during dev chat last week and in #16434 it has an APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. so plugins/themes can register new sizes for favicons/touch icons/etc if the need arises. I’ll be pushed to a GitHub repo by tomorrow. The main thing that will need to be discussed is whether this should just be a customizer setting or not. @johnbillion will post about the repository location and meeting times on this blogblog (versus network, site).

@ocean90 is looking for feedback on #29783!

Next chat will be on May 27 2015, 20:00 UTC

#4-3, #meeting