Dev Chat Summary, June 3

Agenda, Slack log.

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. Merge Proposal (#)
@westonruter, @celloexpressions
We went through the feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. checklist and discussed if the 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 was fit for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. It was approved for merge, pending the following conditions:

Items that should be done before merge:

  • Complete a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). ( audit.
  • Address possible blockers.
  • Merge php tests.
  • Add JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. tests.

Then with/after merge:

  • Killswitch for plugin.
  • An outline for a fieldguideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. post.

Better Passwords (#)
New password UIUI User interface on Profile screen, via GH plugin. Generates and shows by default. Lets the user hide, or click into the field and type (in show/hide modes). Also, the strength meter has been more closely integrated. The color wraps around the field, and it is integrated as one “unit” instead of being this button-like thing that floats below it. Mark would like to get the current state turned into a 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. and merged, as he thinks it’s a fine inflection point, even if the next steps aren’t ready in time.

Adminadmin (and super admin) UI (#)
Got a lot of a11y fixes in play for list tables. A fair number of small/low-hanging fruit issues being noted, which aren’t crucial to hit before betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process., so they’ll keep focusing on the bigger items for now. They also started to sync up with #core-flow issues and getting those into the patch and review queue.

Networknetwork (versus site, blog) Admin UI (#)
Last week’s objectives and progress:

  • Wrap work on the edit site flow and MS sites list table and then take a look at the add site flow and validation in `update_blog_details()`. We made progress on the edit site flow and are nearing commit readiness for a few patches.
  • Continued progress on WP_Network, WP_Site, WP_Network_Query, and WP_Site_Query. We had quite a bit of discussion on the WP_Network ticketticket Created for both bug reports and feature development on the bug tracker. and in SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at Not much ticket progress, but we’re doing good at continuing to pay attention.
  • More thoughts on tracking scheme in wp_blogs for sites. We discussed this in the meeting yesterday and need to do some more research on impact. There’s some info in the recap, but we’ll also have a call for info/thoughts soon.
  • More flows and network admin UI tickets from those flows. We have iPhone 5s flows from @ubernaut. We need to do more creating of tickets and generating of additional flows.

Objectives for next week:

  • Have all 3 tickets related to the edit site flow closed and committed.
  • Additional iterations on WP_Network and WP_Network_Query. Please watch this.
  • Generate discussion around tracking site scheme. @jeremyfelt will gather a list of HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. related tickets and share.
  • Nexus (@kraft) and iPad (@earnjam) flows. Tickets created for bugs found in existing flows. Volunteers needed!

And the recap has all the juicy details:

Favicons (#)
Site Icon progress has been slow due to him being too busy, but he has a working implementation now which he will put up in a repo on GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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. tomorrow, then he’ll see about liaising with contributors to get feedback, and basically go from there.

Next chat will be on June 10 2015, 20:00 UTC

#4-3, #meeting