Drupal 8 HTML5 Initiative Meeting #8

Below is a summary of what was discussed during today's IRC meeting. The full log is attached to the main post.

Issue Discovery and Organization

We currently have a big discovery and maintenance problem in the issue queue. There is no easy way to easily track all of the issues that affect markup and CSS at the moment. Issues are categorized inconsistently, often assigning the originating module as the component, or using tags which we don't monitor, like "accessibility."

There are duplicate efforts going on at the same time. I've noticed recently that the accessibility team is working on the same issues we are working on. We need this to stop. We have to join forces, or things are going to get really frustrating, really fast.

We desperately need to do a round of cleanup in the issue queue to make this happen. Recently the old, and poorly-named "drupal.css" component was renamed to "CSS." So, now we have Markup, CSS, and JavaScript components and a chance to properly categorize most of the issues.
I proposed and asked for help with the following:

• Look through the issues in other components and reassign those issues that primarily affect CSS and Markup to the proper component.
• Only tag issues "html5" when it is actually an HTML5 issue (.e.g. not CSS).
• Monitor issues in both places: Markup and CSS components will cover the majority of issues for HTML5 and CSS. Issues tagged HTML5 will have overlap, but will sufficiently cover the rest. In an ideal situation, we'd have 1 link for everything, but we have to make do with what we have right now.

The @drupal8html5 twitter account has been updated to include issues for all of these components combined. There's a lot more traffic on it since I've made this switch, but it's mostly been positive (replies and retweets).

Modernizr

The topic of dealing with Poylfills in core has come up numerous times over the last couple of months. This conversation always leads to people asking for Modernizr to be included in Drupal core. The details of the previous conversations that are available here:

• Comments in the 6th HTML5 Initiative meeting
• Add a polyfill loading solution to core

The full discussion is available in the log (attached to the main post), but here is summary:

• Some would like to see Modernizr added to core, along with a UI to customize the build the way it's done at http://www.modernizr.com/download/. The rationale is that core themes and modules like Overlay and Toolbar need it, and that Drupal should allow client side feature detection through drupal_add_js().
• Some of us think this is too much and too presumptuous for core, and would be difficult to maintain to boot. The rationale is that individual themes and modules can add only what is needed, and that the choice to use Modernizr or something similar should be made by the theme, instead of having it be forced, and that currently the core use-cases are non-existent.

We didn't come to an agreement either way, but have decided to continue the discussion and document solid core uses cases and revisit.