Labels

Filesystem-related issues to address when developing a stable release of the `atom-fs` module.

Unable to address issue until actions are taken elsewhere (e.g., merging a pull-request).

Loud, hideous changes to package APIs and configuration which require a major version bump.

Confirmed defect in package logic, deprecation notices, and PRs which fix them.

Noticeable changes to default styling, icons, or package behaviour.

Issues related to monkey-patching of core packages prior to Atom consuming the new icon-service.

Threads for open-ended discussion with users.

Updates and improvements to package documentation files, including readmes and change-log entries.

Duplicate of an already-reported issue.

Feature requests or suggested improvements.

New file-extensions or filename patterns associated with an existing icon.

Something a maintainer is unable to address on their own, or lacks adequate time to do so.

Trivial changes: typos, whitespace fixes, dead code removal, and other janitorial tasks.

Old label used prior to consolidating the package's icon-fonts in different repositories.

Issue closed due to unresponsive reporter, insufficient information, or flaky "phantom" issues.

User questions and issues related to package installation and download failures.

Inconclusive, irrelevant, or unrelated issue.

Ongoing task or future project involving non-trivial time and effort.

New icons added to the package's icon-font.

Unrelated, unimportant, or meaningless reports.

Reporter was asked to provide more detail. Issues without response are subject to closing.

Issues related to Facebook's Nuclide, which early v2.0.* releases of file-icons didn't support.

Issues with the package's speed or CPU usage, including startup time.

Help requests and general enquiries from users.

Questions and bugs related to package and user stylesheets.

Triaged tasks not started yet.

Unreproducible error observed by user, or an unclear bug requiring further investigation.

Valid issue, wrong package. Stuff that file-icons has no control or responsibility over.

Feedback pending from reporter, or waiting for an upstream release to land.

Requested changes that a maintainer has chosen not to fix, or is outright impossible to do.