Skip to content
Jonathan Garbee edited this page Jun 9, 2015 · 2 revisions

Labels

Components

Each component has been provided a label. Add the labels for any component the issue is triggered by.

Documentation

If the issue is with a README file for a component, any of the doc pages, or something in the wiki then add the Documentation label. These are issues where the code provided doesn't need modification, but the reference materials do.

MD Alignment

When there is a question as to whether part of a component, or components working together, are adhering to the Material Design specification then apply the MD Alignment label. This means the component(s) in question should be referenced to Material Design in some way and verified they are working as specified.

MD Guidance Needed

The Material Design specification is still under heavy active development. When something isn't clear in the spec or a new thing is needed that isn't specified, we need guidance from the MD team. Issues with the MD Guidance Needed label should proceed with a "best guess" and then align with MD once specified.

Priorities

P0, P1, and P2 are the priority labels. 0 being the highest and 2 being the lowest. Assigning these depend on the situation, however regressions that need fixing should always be P0.

Performance

The Performance label should be applied to any issue that is displaying a problem that affects page performance. This can either be a problem with how something is built or a request for a new feature that would help developers build more performant sites.

Template Request

The Template Request label applies to any issue that requests a new template for the demonstrations.

Future

The Future label is for any issue that should be worked on, but for any reason it won't be worked on/accepted as a PR anytime soon. These should be scheduled into future Milestones.

Research

The Research label applies when an issue needs research beyond simple MD Alignment to detail what is incorrect.

Tooling

The Tooling label is used when an issues action needs to be handled by modifying the tooling files. These are, gulpfile.js, bower.json, package.json, .jscsrc, .jshintrc, .editorconfig, .gitignore, and .gitattributes.