launchpad-dev team mailing list archive

[Huw Wilkins <huw.wilkins@xxxxxxxxxxxxx>]

On 07/06/2011 02:23 AM, Matthew Revell wrote:
> On 5 July 2011 16:20, Andrea Corbellini <corbellini.andrea@xxxxxxxxx> wrote:
>> Hi Matthew,
>>
>> On Tue, 2011-07-05 at 14:13 +0100, Matthew Revell wrote:
>>> Here's how I imagine it'd work. Let's say we're adding an in-line
>>> commenting feature to diffs in merge proposals. When someone was
>>> looking at a merge proposal page, we could pop-up a JS overlay that
>>> invites them to take part in a phone/Skype call. They'd have the
>>> option to enter their phone number/Skype ID/whatever, or select "Ask
>>> me another time" or "Never ask me about this again".
>> While I like the general idea, I think this particular behavior is too
>> much "spamish". Active popups that show up while you're working asking
>> you unrelated questions can be really, really annoying.
> Yeah, I think that can be a problem and one that we'd, obviously, want to avoid.
>
> Do you have any suggestions of what would lessen the "spam" aspect of this?
>
I think this is a really good idea. If we're collecting the feedback
from inside Launchpad we could only show the message after an action or
workflow has been completed. This would allow us to gather data from
users just after they've used the feature. It would also only interrupts
users that use the feature and users that don't use the feature never
see it. It possibly allow us to be more disruptive in the type of
notification.

Using matthew's in-line commenting example: If a user opens a merge
propsal page and a popup appears that asks them to give feedback on the
feature it is annoying because it stops them from doing the action they
came to the page to do. They also can not give good feedback because
either they haven't used the feature yet or it is not fresh in their mind.

On the other hand if they were to open a merge proposal, add an in-line
comment and when they submit the comment it then brings up a popup
asking them to give feedback on the feature they've just used it is less
disruptive (they've just finished the action they wanted to take) and
the user has just used the feature we want feedback on.