Archives

Konstantin Obenland 8:58 am on June 11, 2015
Tags: ,   

Dev Chat Summary, June 10

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. Status Update (#)
@westonruter
The 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). (https://en.wikipedia.org/wiki/Accessibility) review did not unveil any blockers, although it wasn’t done on the feature branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". the team is currently working on. Introduction of a blockerblocker A bug which is so severe that it blocks a release. there was deemed unlikely however. 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party version can’t be released since it’s now dependent on some coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. patches being applied.

For the rest of the requirements: The biggest blockers are almost complete, Customizer setting re-architecture and sub-menu drag & drop. The settings re-architecture has been integrated into JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. for the nav menu items, allowing nav menus to be edited, added, removed all with 100% previewability and not making any changes to the DB. Once Save & Publish is done, any newly created nav menu items get inserted at that time. Same goes for nav menu deletion. The submenu drag & drop has been merged into the same branch and it is all working together now.

The biggest outstanding pieces are:

  • adding back the ability to add/remove entire menus
  • updating keyboard-accessible reordering to work with new menu settings
  • more unit testing for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher, and write tests for JS

Estimated time of completion is June 11, which leaves 5 – 6 days to merge.

Adminadmin (and super admin) UIUI User interface (#)
@helen
Even more prep work has gone into list tables, now working on the responsive part on #32395. They have gotten some feedback so far, would love more even on the rough cuts. Helen will be at wordcampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. philly’s contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. this weekend, looking to knock through a bunch of the low hanging fruit on the screen sweep spreadsheet, and find takers for some make-flow tickets (#29906 in particular). She has some catch up to do with other contributors on visual regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. testing and media-new, which will happen at tomorrow’s meeting.

Networknetwork (versus site, blog) Admin UI (#)
@jeremyfelt

Objectives from last week:

  • #32434 is in. Jeremy is still poking at #22383 and #32503 with a target of this evening.
  • They had no additional iterations on WP_Network and WP_Network_Query, but @jjj is working on having something this week.
  • Did not yet generate discussion around 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.. Moving this objective along to this week.
  • They made quite a bit of progress with flows. @kraft added Nexus and @earnjam has iPad screencaptures he will be publishing shortly. Their next push is to start creating tickets. Jeremy wrote a post to try and drum up support – https://make.wordpress.org/core/2015/06/05/help-test-and-capture-the-network-admin-ui/ – and they had a handful of people hop in. Pretty optimistic that they’ll start making progress here, especially with a couple contributor days this weekend.

Objectives for this week:

  • New tickets to address found issues in flow. These issues logged in the screen sweep spreadsheet.
  • Iterations on WP_Site and WP_Network. Discussion around iterations.
  • #22383 and #32503 committed.
  • Write post, generate discussion around HTTPS in multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site.

Better Passwords (#)
@markjaquith
Mark turned the plugin 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. for the new UI. After a cleanup, that can land, and we can iterate a bit, as well as tackle the new user password flow, which is different. The expiration of reset links (#32429) needs testing (human and unit), before that lands. And the “notify users of password and email changes” patch (#32430) needs a review on the hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. in it. I’m not sure we’re passing the right things along. Like, email instead of the whole user array.

Favicons (Site Icon) (#)
@johnbillion
There’s been a status update on make/core. It’s looking like #29211 would be a better approach to a reusable control with image cropping functionality. So John is wondering whether we should aim for 29211 for 4.3 and site icon for 4.4. On the topic of using the Customizer or not: much of the image cropping control for the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. image is also used on the old header image screen (it’s mostly media library and ajax functionality), so it’s not necessarily tied to being a customizer control.
Let’s meet today June 11 2015, 20:00 UTC to discuss what a good approach could look like.

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

#4-3, #meeting

Konstantin Obenland 2:26 pm on June 10, 2015
Tags: ,   

Dev Chat Agenda for June 10

Here’s the agenda for today’s Dev Chat in the #core channel on Slack.

Time/Date: June 10 2015 20:00 UTC:

  1. 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. Status Review – @westonruter
  2. Feature Updates
    1. Adminadmin (and super admin) UIUI User interface – @helen
    2. Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site Admin UI – @jeremyfelt
    3. Passwords – @markjaquith
  3. Component Updates (if time permits)

Feature Leads: Let’s review last weeks goals and set new ones for next week.

Recommended reading: Trust, Live Preview, and Menus in the Customizer.

#4-3, #agenda

Konstantin Obenland 5:59 am on June 5, 2015
Tags: ,   

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 WordPress.org Plugin Directory https://wordpress.org/plugins/ 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). (https://en.wikipedia.org/wiki/Accessibility) 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 (#)
@markjaquith
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 (#)
@helen
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 (#)
@jeremyfelt
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 https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. 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: https://make.wordpress.org/core/2015/06/03/multisite-office-hours-recap-june-2-2015/

Favicons (#)
@johnbillion
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. https://github.com/ 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

Konstantin Obenland 6:21 am on June 3, 2015
Tags: ,   

Dev Chat Agenda for June 3

Here’s the agenda for today’s Dev Chat in the #core channel on Slack.

Time/Date: June 3 2015 20:00 UTC:

  1. Consider 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. 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party for merge [Proposal] [Plugin]
    If you haven’t looked at either of the merge proposals yet, please spend some time today before the meeting. Please comment on the post if you haven’t already.
  2. Feature Updates
    1. Adminadmin (and super admin) UIUI User interface – @helen
    2. Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site Admin UI – @jeremyfelt
    3. Passwords – @markjaquith
    4. Site Icon – @johnbillion
  3. Component Updates (if time permits)

Feature Leads: Let’s review last weeks goals and set new ones for next week.

Recommended reading: Features as Plugins.

#4-3, #agenda

Konstantin Obenland 12:59 pm on May 27, 2015
Tags: ,   

Dev Chat Agenda for May 27

Here’s the agenda for today’s Dev Chat in the #core channel on Slack.

Time/Date: May 27 2015 20:00 UTC:

  1. #32396: Settings Reduction for 4.3
  2. Feature Updates
    1. Adminadmin (and super admin) UIUI User interface – @helen
    2. Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site Admin UI – @jeremyfelt
    3. Partial Refresh – @westonruter
    4. 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. – @celloexpressions / @westonruter / @voldemortensen
    5. Passwords – @markjaquith
    6. Site Icon – @johnbillion
  3. Component Updates

Feature Leads: Let’s review last weeks goals and set new ones for next week.

#4-3, #agenda

Konstantin Obenland 9:45 pm on May 20, 2015
Tags: ,   

Dev Chat Summary, May 20

Agenda, Slack log.

Committers Update (#)
@nacin
New guest committers: @iseulde, @westonruter, and @obenland, renewed guest committers: @jorbin, @jeremfelt, permanent committers: @pento, @boone, and @johnbillion
Also see https://make.wordpress.org/core/2015/05/20/new-committers-for-4-3/

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

Adminadmin (and super admin) UIUI User interface (#)
@helen
@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 (#)
@jeremyfelt
They talked through aspects of the Edit Site 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 Make/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 (#)
@westonruter
Now has support for refreshing menus changed by Menu Customizer: https://github.com/xwp/wp-customize-partial-refresh/pull/12/files
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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party release.

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 (#)
@markjaquith
They’ve been working on a mockup of the password UI: http://codepen.io/markjaquith/pen/GJjZbJ
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 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. https://github.com/.
#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
@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).

Other:
@ocean90 is looking for feedback on #29783!

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

#4-3, #meeting

Konstantin Obenland 3:52 pm on May 20, 2015
Tags: ,   

Dev Chat Agenda for May 20

Here’s the agenda for today’s Dev Chat in the #core channel on Slack.

Time/Date: May 20 2015 20:00 UTC:

  1. Feature Updates
    1. Editor – @azaozz / @iseulde
    2. Adminadmin (and super admin) UIUI User interface – @helen
    3. Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site Admin UI – @jeremyfelt
    4. Partial Refresh – @westonruter
    5. 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. – @celloexpressions / @westonruter / @voldemortensen
    6. Passwords – @markjaquith
    7. Site Icon – @johnbillion
  2. Component Updates

Feature Leads: Let’s review last weeks goals and set new ones for next week.

Recommended reading:

#4-3, #agenda

Konstantin Obenland 6:14 pm on May 14, 2015
Tags: ,   

Dev Chat Summary, May 13

Agenda, Slack log.

Editor (#)
@azaozz, @iseulde
@azaozz has been looking at the “WordPress integration” parts the last couple of days, a lot of things that can be improved there. It removes some of the oddities, like running the post content through wpautop() before outputting it in the textarea, but only when TinyMCE is expected to be loaded, etc. @iseulde is working on the mobile toolbar and is hopeful she can get 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. ready this week. By next week’s meeting they want to have the mobile toolbar working (except in iOSiOS The operating system used on iPhones and iPads.), as well as #31655, #30949, and maybe #31441 in.

Adminadmin (and super admin) UIUI User interface (#)
@helen
@helen has largely been working on prepping things (tickets, examples, links, etc.) for Thursday’s UI meeting. More about the meeting (including agenda) can be found here: https://make.wordpress.org/core/2015/05/11/weekly-core-ui-meetings-for-4-3/

Networknetwork (versus site, blog) Admin UI (#)
@jeremyfelt
Recap of Multisite office hours: https://make.wordpress.org/core/2015/05/12/multisite-office-hours-recap-may-12-2015/
Things they want to have done by next week:

  • Mockups for the Edit Site / Add New Site improvements by @hugobaeta.
  • Having more flows posted to Make Flow for the network admin, via @sofiarose @kraft, and @ubernaut.
  • Get some decent progress on `WP_Site` and `WP_Network` with @jjj.

Partial Refresh (#)
@westonruter
Weston hopes to add initial integration between 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. and Partial Refresh this weekend. Due to client projects he’ll have to work on Concurrency _concurrently_ with Partial Refresh so he doesn’t hold up Menu Customizer. By next week Partial Refresh should be abstracted enough for the Menu Customizer to work with.

Menu Customizer (#)
@voldemortensen, @celloexpressions
Now that it’s object-oriented they’re ready to start ramping up work. They’ll be going through 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. https://github.com/ issues and come up with the next milestone for possibly the end of the week. By next week they’re planning on getting lazy-loading of both all menu item controls and the add-menu-item panel done, as well as better error handling for duplicate menu names and the like.

Better Passwords (#)
@markjaquith
By next week, Mark wants a HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers., CSSCSS Cascading Style Sheets., JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. working demo of the password setting UI, and tickets for that and all other items on their hitlist. If there’s time beyond that, they could knock off one of the easier ones like notifying users of their password/e-mail changes.

AccessibilityAccessibility 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). (https://en.wikipedia.org/wiki/Accessibility) component update (#)
@joedolson
There’s been a ton of work done on the List Table class and associated areas. Joe has a set of 10 tickets with patches that he’d like to see committed by next week: #32150, #32254, #32255, #32028, #32152, #32147, #32189, #31654, #32253, #32170.

Build tools component update (#)
@jorbin
QUnit update seems to have gone off without a hitch. There are 7 npm dependencies that need to be updated. 6 are ready to go. grunt-sass needs a bit more digging in. This week, @jorbin is going to update the build tools roadmap he wrote up after WCSF and then pester a lead (likely @helen) to give it a read so that it can finally be published.
Not exactly build related, but test related: Bug scrub identified that we don’t have any tests for nav menus, especially around the classes we add. @johnbillion has agreed to write some tests there so that we can fix all the bugs around that.

Favicons (#)
@obenland
Support for managing favicons seems like a rudimentary thing, and its absence in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. does seem odd to some. We still need plugins to handle favicon and other media icons in the admin, there is currently no good way for users to do that. We’ve been talking about adding support for a favicon manager for a long time ( #16434 ), let’s make 4.3 the release that finally adds it. @johnbillion volunteered to lead the feature for 4.3, with help from @brandondove, @kraftbj, @sofiarose, and possibly @dh-shredder.

Next chat will be on May 20, 2000 UTC

#4-3, #meeting

Konstantin Obenland 10:25 pm on May 12, 2015
Tags: ,   

Devchat Agenda for May 13

Here’s the agenda for tomorrow’s Dev Chat in the #core channel on Slack.

Time/Date: May 13 2015 20:00 UTC:

  1. Feature Updates
    1. Editor – @azaozz / @iseulde
    2. Adminadmin (and super admin) UIUI User interface – @helen
    3. Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site Admin UI – @jeremyfelt (if available)
    4. Partial Refresh – @westonruter
    5. 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. – @celloexpressions / @westonruter / @voldemortensen
    6. Passwords – @markjaquith
  2. Component Updates
    1. AccessibilityAccessibility 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). (https://en.wikipedia.org/wiki/Accessibility) – @joedolson
    2. Build tools – @jorbin
  3. Site Icon feature proposal – @obenland
  4. Open Floor – Looking for dev feedback on a ticketticket Created for both bug reports and feature development on the bug tracker.? Use this part of the meeting to let us know!

Recommended reading:

#4-3, #agenda

Konstantin Obenland 10:09 pm on May 7, 2015
Tags: ,   

Dev Chat Summary, May 6th

Agenda, Slack log.

Editor (#)
@azaozz, @iseulde
Spent last week to go over the things they want to work on. @iseulde will work on the mobile editor toolbar first. They’ll milestone tickets as they get patches. For posterity and everyone who wants to follow up, the Editor game plan for 4.3 can be found here: https://make.wordpress.org/core/2015/05/01/editor-wish-list-for-4-3/

Adminadmin (and super admin) UIUI User interface (#)
@helen
Not much to talk about yet as @helen was out last week and will be out for the next few days. She will schedule a meeting for next week, likely May 14 17:00 UTC. location to be determined.

Networknetwork (versus site, blog) Admin UI (#)
@jeremyfelt
There was a good chat about NA UI on Tuesday. First steps are documenting pain points now and move forward with tickets, etc. Multisite chat summary: https://make.wordpress.org/core/2015/05/06/multisite-office-hours-recap-may-5-2015/

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. (#)
@westonruter
Noteworthy from Monday’s chat is that Menu Customizer was added to the 4.3 roadmap for the Customizer, while Transactions were taken off it. No other news besides that: https://make.wordpress.org/core/2015/05/04/customizer-chat-summary/

Better Passwords (#)
@markjaquith
Weekly meetings are on Monday 17:00 UTC in #core-passwords. Right now they’re throwing ideas around, by Monday @markjaquith wants to have gone through that and have a make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post that outlines the major goals for this release, so they can get to work.

AccessibilityAccessibility 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). (https://en.wikipedia.org/wiki/Accessibility) component update (#)
@joedolson
The accessibility team has spent a lot of time generating tickets for tabular data, based on user feedback gathered during the 4.2 cycle. It’s about 8 tickets right now, all prefixed with “List Table:”. They have also been focusing on establishing a new heading hierarchy for the admin. Resolving the H1 issue is fairly simple, but has broad impact across the admin; should probably get this in ASAP. It shouldn’t have much impact in normal usage, but e team is unsure what kinds of edge cases might be out there. There are two separate issues: implementing H1 across pages and addressing the hierarchy within pages; @joedolson suggested to handle just the primary H1 to start, then start looking at the internal issues.

Build tools component update (#)
@jorbin
Started upgrading dev dependencies and our version of QUnit. @jorbin will finish those updates this week. People will likely need to do some npm installs to ensure they have the up to date versions.

Next chat will be on May 13, 20:00UTC

#4-3, #meeting