Description Wayne Beaton 2015-12-15 16:42:18 EST

Let's use this as an umbrella for issues of detail for Neon.

he idea here is to tackle some of the "little things" and improve the overall impression we leave with users. I'm motivated--at least in part--by the work done with last year's "Every Detail Matters for Mars" and the positive community response to some of the little things--like turning on line numbers by default--that we've done in the past.

This represents a shift to focus more on user experience.

This includes (for example):

* Website improvements (make it easier to find the right thing to download)
* Installation
* Making feature names consistent
* Categories and categorization of features in the simultaneous release repository
* General UI consistency (high level, lower level usability is a "big thing")
* Avoid use of code names in the UI

To avoid confusion/splitting the discussion, let's please avoid discussion specific issues/activities in detail on this bug. Open blocker bugs for specific issues and discussion. I'd prefer to keep the specific blockers on this bug at high/cross-project level (i.e. I prefer to avoid making any bugs for a specific project as a blocker).

As a community, we can decide what else this might include. Naturally, success depends on scoping this so that we can actually get the work done.

I'll review the blockers on Bug 457087 (overdue) to see if any of our "detail" bugs for Mars should be moved to Neon.