1179193 - [meta] Panel conversation list visual refresh

Status: RESOLVED FIXED

(Hello (Loop) :: Client, defect, P2)

Comment 1

[Victoria Gerchinhoren [:vicky]]

Attachment: [Visual Specs] PanelUI_ConversationAndContacts.png

Comment 2

[Mike de Boer [:mikedeboer]]

Romain, do we want to keep the 'Beta' ribbon on the panel after the visual refresh, or is this the good time to get rid of it?

Comment 3

[Dan Mosedale (:dmosedale, :dmose)]

Comment on attachment 8630980 [details]
[Visual Specs] PanelUI_ConversationAndContacts.png

I've obtained links to two current exports of the mocks needed and put them in the user-story, which can be edited. 

For now, we'll need to edit the user-story to point to new exports when the sources change.

What I hope we can do sooner rather than later is to have permalinks that point to the most current (stable?) mocks so that these things stay up-to-date automagically.

Doing a needinfo on :vicky and :mikedeboer just to be sure that were on the same page, and that I haven't done anything crazy.

Comment 4

[Dan Mosedale (:dmosedale, :dmose)]

RT/Vicky, displaying the other person's presence next to the buddy icon, as well as the ability to set one's own status as "Away", as shown in the common elements page, involves us supporting distribution of presence information, which is a hard-to-implement problem at scale.  I don't think we want to entrain that in the visual refresh, and I suspect we're unlikely to consider it from an architectural point of view until we get XMPP support.  I've removed it from the acceptance criteria of this user story for now; if you want to discuss putting it back, let me know.

Comment 5

[Victoria Gerchinhoren [:vicky]]

(In reply to Dan Mosedale (:dmose) - needinfo? me for response from comment #4)
> RT/Vicky, displaying the other person's presence next to the buddy icon, as
> well as the ability to set one's own status as "Away", as shown in the
> common elements page, involves us supporting distribution of presence
> information, which is a hard-to-implement problem at scale.  I don't think
> we want to entrain that in the visual refresh, and I suspect we're unlikely
> to consider it from an architectural point of view until we get XMPP
> support.  I've removed it from the acceptance criteria of this user story
> for now; if you want to discuss putting it back, let me know.

It's ok. Not a priority just the ideal UX.

Comment 6

[Victoria Gerchinhoren [:vicky]]

(In reply to Dan Mosedale (:dmose) - needinfo? me for response from comment #3)
> Comment on attachment 8630980 [details]
> [Visual Specs] PanelUI_ConversationAndContacts.png
> 
> I've obtained links to two current exports of the mocks needed and put them
> in the user-story, which can be edited. 
> 
> For now, we'll need to edit the user-story to point to new exports when the
> sources change.
> 
> What I hope we can do sooner rather than later is to have permalinks that
> point to the most current (stable?) mocks so that these things stay
> up-to-date automagically.
> 
> Doing a needinfo on :vicky and :mikedeboer just to be sure that were on the
> same page, and that I haven't done anything crazy.

Mike, for that reason I have all mockups in a dropbox folder, I just updated the US with the good links. Thanks for bringing this up. Today I will also add size specs for the implementation.

Comment 7

[Victoria Gerchinhoren [:vicky]]

Sorry, I wanted to say DAN ;)

Comment 8

[Victoria Gerchinhoren [:vicky]]

Visual specs sizes and margins: 
https://www.dropbox.com/s/5zpalcwlg0wd8em/Hello_PanelUI_measurements.png?dl=0

Comment 9

[Mike de Boer [:mikedeboer]]

Both approaches are pretty fragile. Links get lost, user stories updates are easy to forget, unless you're RT. ;-)

The only really solid method of keeping the latest and greatest design sheet/ spec/ whatever that I've worked with is by keeping it as close to its context as possible: an attachment to the meta bug in question. Or to a UX bug that this or any other meta bug is depending on.

I'd like to propose that we - as a project - move over wholesale to using the attachment mechanism as provided by our tool that does most, if not all, of our record keeping.
The older attachment can be marked as obsolete, so it won't appear in the list of attachments anymore.

I'm awarding brownie points to everyone who prefixes their attachment summaries with a version number!!

Comment 10

[Mike de Boer [:mikedeboer]]

(In reply to Mike de Boer [:mikedeboer] from comment #9)
> Links get lost, user stories updates are easy to forget, unless you're RT. ;-)

I meant to say: Links get lost in long bug comment threads and it's easy to forget to update a user story, unless you're RT. ;-)

Comment 11

[Victoria Gerchinhoren [:vicky]]

I put links in the metabugs, but the meta of all metas is AHA! for us and not bugzilla, is where the epics live. For the moment, you should do fine with the dropbox links, and in the future, when interaction specs are more tidy and unified, they can link to the visual work (i am talking about every screen linking to their visual artifact.).

Comment 12

[Victoria Gerchinhoren [:vicky]]

@Mike, completely agree, but we're not getting there as we started with different ways of working, my proposal is this in slide 22: https://docs.google.com/presentation/d/1FUp_7Z0WZaA87gm5n3UXGQ-f0yjbvkDX82zq10ofkm0/edit?usp=sharing 

Cheers.

Comment 13

[Mike de Boer [:mikedeboer]]

(In reply to Victoria Gerchinhoren [:vicky] from comment #12)
> @Mike, completely agree, but we're not getting there as we started with
> different ways of working, my proposal is this in slide 22:
> https://docs.google.com/presentation/d/1FUp_7Z0WZaA87gm5n3UXGQ-
> f0yjbvkDX82zq10ofkm0/edit?usp=sharing 
> 
> Cheers.

I agree with that slide - it looks like that proposes the flow I talk about in comment 9. Let's bring this topic to the table when we meet later this week.

Comment 14

[Romain Testard [:RT]]

(In reply to Mike de Boer [:mikedeboer] from comment #2)
> Romain, do we want to keep the 'Beta' ribbon on the panel after the visual
> refresh, or is this the good time to get rid of it?

Please let's keep the "Beta ribbon" for now.
Vicky can you please make sure it remains part of your visuals?

Comment 15

[Romain Testard [:RT]]

(In reply to Dan Mosedale (:dmose) - needinfo? me for response from comment #4)
> RT/Vicky, displaying the other person's presence next to the buddy icon, as
> well as the ability to set one's own status as "Away", as shown in the
> common elements page, involves us supporting distribution of presence
> information, which is a hard-to-implement problem at scale.  I don't think
> we want to entrain that in the visual refresh, and I suspect we're unlikely
> to consider it from an architectural point of view until we get XMPP
> support.  I've removed it from the acceptance criteria of this user story
> for now; if you want to discuss putting it back, let me know.

Yes, to be clear we don't suggest implementing a presence solution.
That said the visual refresh includes an update to the current "Do not disturb" functionality and this is what the user story mention was about - apologies if this was confusing. So just to be clear, a visual update to the current "Do not disturb" indicator is required as part of this bug.
Vicky could you please update the visual and use the strings currently in use to avoid confusion on this feature - i.e replace "Unavailable" with "Do Not Disturb"?

Comment 16

[Victoria Gerchinhoren [:vicky]]

(In reply to Romain Testard [:RT] from comment #14)
> (In reply to Mike de Boer [:mikedeboer] from comment #2)
> > Romain, do we want to keep the 'Beta' ribbon on the panel after the visual
> > refresh, or is this the good time to get rid of it?
> 
> Please let's keep the "Beta ribbon" for now.
> Vicky can you please make sure it remains part of your visuals?

You can keep the ribbon as it is, style wise is really subtle so it won't be off. Thanks!

Comment 17

[Victoria Gerchinhoren [:vicky]]

Please, see that I have updated the conversation mockups with fixed height of the panel, the not signed in scenario and how the conversation list looks like when scrolled.

Thanks!

Comment 19

[Mark Banner (:standard8)]

We've now implemented pretty much everything here, and the remaining items are bug fixes/follow-ups that we'll track individually.