Device Naming and Editing about fxa HOT 9 CLOSED

Guys, we need to break this work down sooner rather than later so we can move it into next and now columns as work for 43. Who should be involved in this discussion? Unless I hear something here I will assume Rfeeley, Rkelly, Zach?

from fxa.

See mozilla/fxa-auth-server#1009

from fxa.

I want my FF devices to be logically named

Sync already has some logic for choosing a default device name. Do we need additional work on top of that, or simply need to lift that information up into FxA?

@billmaggs also should this have "Firefox 43" milestone set here, or does that only happen when it gets into a certain state in aha?

from fxa.

should this have "Firefox 43" milestone set here, or does that only happen when it gets
into a certain state in aha?

Actually, I see a bunch of the metrics-related issues have "Firefox 43" milestone here in github, but are scheduled under "Firefox 42" in aha. Is that managed by aha or something that we've layered on top of it?

from fxa.

That logic does not yet map across, AFAIK. Will check.
On Aug 12, 2015 10:53 PM, "Ryan Kelly" [email protected] wrote:

I want my FF devices to be logically named

Sync already has some logic for choosing a default device name. Do we need
additional work on top of that, or simply need to lift that information up
into FxA?

@billmaggs https://github.com/billmaggs also should this have "Firefox
43" milestone set here, or does that only happen when it gets into a
certain state in aha?

—
Reply to this email directly or view it on GitHub
#32 (comment).

from fxa.

Thinking about it, I realize I'm making a lot of implicit assumptions about the scope of this bug.

Sync already has a notion of device names, with non-terrible defaults and the ability to edit them in the sync-preferences panel. So I'm assuming this bug is mostly about lifting that ability up into core FxA rather than doing it down in sync, and e.g. allowing you to edit the description directly in some web-based devices view. Do we need to clarify the user experience a little more here before we can break it down into units of work?

from fxa.

I am thinking that the Ux discussion is part of the breakdown work. From my
point of view and some others in our discussions the device names we
mostly lift are the bare minimum and we should see if we can do more, and
yes it should become a core part of understanding (and eventually managing)
services across all your FF devices.
On Aug 12, 2015 11:00 PM, "Ryan Kelly" [email protected] wrote:

Thinking about it, I realize I'm making a lot of implicit assumptions
about the scope of this bug.

Sync already has a notion of device names, with non-terrible defaults and
the ability to edit them in the sync-preferences panel. So I'm assuming
this bug is mostly about lifting that ability up into core FxA rather than
doing it down in sync, and e.g. allowing you to edit the description
directly in some web-based devices view. Do we need to clarify the user
experience a little more here before we can break it down into units of
work?

—
Reply to this email directly or view it on GitHub
#32 (comment).

from fxa.

SGTM, I think the right path forward then is for me to continue working bottom-up on infra and APIs in mozilla/fxa-auth-server#1009, and concurrently kick off UX and design work with @ryanfeeley.

from fxa.

Exporting these FEATURE cards from Aha has not turned out to be useful in practise, I'm closing them in favour of more direct use of Aha.

This feature lives at: https://mozilla.aha.io/features/FXA-18

from fxa.