[12:19]  * gmb lunches
[13:29] <gary_poster> benji, bac, I have some thoughts on the mockups.  I'd like us to run user tests on two or three new variations.  Versions would be these.
[13:29] <gary_poster> (1) we do as many of the recommendations as possible, but eliminating the confusing "events" options
[13:29] <gary_poster> (2) we do as many of the recommendations as possible, and rearranging the "events" options
[13:29] <gary_poster> (3) (if we can) we do as many of the recommendations as possible plus changes that require more dramatic changes to the events story (i.e., those that would require changes to the server side)
[13:29] <gary_poster> I have some ideas on #2 and maybe #3 that I'd like to work out and propose.
[13:29] <gary_poster> Matthew says that he could do testing as soon as tomorrow, if we get mockups to him by his tomorrow morning.  He can deliver these mockups to different users.
[13:30] <gary_poster> bac benji gmb: mumble/kanban in, oh, nowish :-P
[13:30] <gmb> Yep
[13:39] <benji> gary_poster: the mockup ideas sound good to me.  I assume Matthew doesn't think there are too many variations.
[13:40] <gary_poster> benji, yeah, he was for it
[13:41] <benji> cool
[13:41] <gary_poster> benji, do you know where I can see the current mockups?
[13:41] <benji> by rearranging events you mean splitting out the transition bits from the comments/metadata bits, right?
[13:42] <benji> gary_poster: bzr+ssh://bazaar.launchpad.net/~yellow/launchpad/subscription-widget-mockups
[13:42] <gary_poster> benji, yeah.  The basic constraint for #2 is "what can we propose with no changes, or minimal changes, to the server side"
[13:42] <gary_poster> thank you
[13:49] <gary_poster> bac, I imagine I'm supposed to look at "subscribe to bug mail user testing.bmml" mostly?  It has a lot of "image not found"s on it
[13:49] <gary_poster> don't worry about replying now if on call
[13:53] <bac> gary_poster: let me look.  balsamiq is sometimes not good about carrying around assets
[13:54] <gary_poster> cool thanks
[13:54] <bac> gary_poster: actually, look in the 'subscribe to bug mail' subdirectory
[13:55] <bac> gary_poster: can you load any of those bmmls?
[13:55] <gary_poster> bac, I can load those bmmls, and I see those are the right ones, but I'm missing a lot of images.  If I had to guess
[13:55] <gary_poster> I would say they are the background images
[13:55] <gary_poster> of the bug page
[13:55] <gary_poster> and the arrows
[13:56] <bac> gary_poster: ok.  let me grab the branch on a different machine and see if i can sort it out
[13:56] <gary_poster> thanks bac
[14:05] <gary_poster> bac, benji, another question.  If I go to https://qastaging.launchpad.net/lazr.enum/+subscribe , I see that I can only subscribe myself or one of the teams of which I am an administrator.  In the mockups, it seemed like I could subscribe anyone.  Was that an intended change, or a misunderstanding of mine?
[14:07] <benji> gary_poster: since the subscribing anyone part is currently only for direct subscription, I don't think we're changing that
[14:08] <gary_poster> benji, cool thanks
[14:42] <bac> gary_poster, benji: the mockups have been updated and have the assets within the branch.
[14:42] <gary_poster> awesome thanks bac.
[14:43] <bac> tip: dragging images onto the mockup does not work for portability.  you must import them and have balsamiq copy to an assets folder
[14:43] <gary_poster> cool, I was wondering
[14:44] <gary_poster> Confirmed working for me, fwiw.
[14:46] <bac> ugh, actually:  1) place image place holder on mockup, 2) in the control panel for that item select 'import', and 'copy to assets'
[15:52] <gary_poster> bac, benji, if you update the branch, gary-alt contains a strawman for the "(2) we do as many of the recommendations as possible, and rearranging the "events" options" one.  I'm thinking about #3 now.
[15:52] <benji> cool
[15:52] <bac> gary_poster: ok
[15:59] <bac> gary_poster:  i see no update to lp:~yellow/launchpad/subscription-widget-mockups
[16:00] <bac> is gary-alt a new branch or a subdirectory in the old branch?
[16:00] <gary_poster> bac, subdirectory.  maybe didn't push, checking
[16:00] <gary_poster> oh pushed to ~gary :-P
[16:02] <bac> ok
[16:02] <gary_poster> I think I might have just pushed it to yellow, bac
[16:02] <gary_poster> got an odd message from bzr
[16:03] <bac> i was able to pull from yellow
[16:03] <gary_poster> cool
[16:04]  * bac loves the contradiction of 'bzr pull :push'
[16:04]  * gary_poster doesn't know what that incantation does
[16:04] <bac> uses the push location as shown in 'bzr info'
[16:05] <gary_poster> ah, cool
[16:05] <bac> pulls from the push location
[16:05] <bac> all of those destinations can be used by specifying :dest
[16:05] <gary_poster> bac and benji do you have any strawmen you want to prepare?  I have a team leads call at 12 which provides a nice hard timelimit to a mockup discussion.  OTOH, we can put it off till later and use some other mechanism o prevent marathons
[16:06] <gary_poster> o->to
[16:06]  * bac looking at gary-alt now
[16:06] <gary_poster> cool
[16:07] <gary_poster> hopefully "strawman" conveys the "it's a discussion starter" aspect I want it o have
[16:07] <benji> I'm fresh out of strawmen.
[16:07] <gary_poster> ...o->to...
[16:08] <benji> o->to looks like a motorcycle
[16:08] <gary_poster> it does kinda
[16:13] <bac> gary_poster: the horrible alignment of your twisties is *so* distracting!  :)
[16:14] <gary_poster> bac, lol, sorry, I fixed it locally, do you want me to commit and push the change? :-)
[16:14] <bac> beuno tip: select an item and use arrow keys for fine tuning position
[16:14] <bac> hellz no
[16:14] <bac> it looks good, gary_poster
[16:14] <gary_poster> yeah, I know.  it is out of alignment because I adjusted the accordian underneath it
[16:15] <gary_poster> thank you
[16:15] <bac> i talked to julian and he has a pretty compelling reason to opt out of getting email for 'fixed released'
[16:15] <gary_poster> what, our qa bot?  :-/
[16:16] <bac> that being, when launchpad does a major release and we run our scripts to migrate all bugs he gets a ton of messages that are annoying
[16:16] <gary_poster> ah
[16:16] <bac> i too find it annoying but they are easily ignored so it never registered
[16:16] <gary_poster> yeah
[16:16] <gary_poster> so he wants "bugs are added or comments are made"?
[16:16] <gary_poster> or "everything except fix released"?
[16:16] <bac> yeah
[16:17] <bac> yeah to the first
[16:17] <gary_poster> gotcha
[16:17] <gary_poster> he could do the second with what we have now
[16:18] <gary_poster> but he wants to filter out the transition, not comments made after the transition has occurred
[16:19] <gary_poster> [ ] Filter out transitions to...
[16:19] <gary_poster>     [ ] Fix released
[16:19] <gary_poster>     [ ] uh...
[16:22] <bac> gary_poster: i guess we missed our window for a call.  i'm going to go grab some lunch.
[16:22] <gary_poster> (3)
[16:22] <gary_poster> Filter out [ ] comments   [ ] status changes   [ ] linking branches   [ ] importance changes
[16:22] <gary_poster> ?
[16:22] <gary_poster> ok bac, sounds like an escape plan. :-)  let's plan to talk around...2, bac and benji?
[16:23] <benji> +1
[16:23] <bac> ok, we'll be bounded by our 2:30 call
[16:23]  * gary_poster tries to remember Wed 2:30 call
[16:23] <bac> or is it tomorrow?
[16:24] <gary_poster> but we can try to be bounded by 2:30 anyway ;-)
[16:24] <gary_poster> yeah, tomorrow
[16:24] <bac> ok, we'll be bounded by our thursday 2:30 call.  not as good.
[16:24] <gary_poster> lol
[16:24] <benji> heh
[16:24] <gary_poster> ok talk to you all then.  thanks
[16:30] <gary_poster> gmb, what kind of metadata changes can trigger a notification?  status changes, importance changes, privacy changes, linked branches...can you suggest somewhere to look, or do you know off-hand?
[16:32] <gmb> gary_poster: If you look in lib/lp/bugs/adapters/bugchange.py you should see a whole bunch of BugChange objects. Each of those has (or should have, if danilo's branch has landed) a change_level property, which describes what BugNotificationLevel that change lives at. METADATA is the default, IIRC.
[16:32] <gary_poster> ah-ha! thank you
[16:32] <gmb> gary_poster: Short version: if it's not declared to be anything else, it's METADATA.
[16:32] <gary_poster> right, cool
[16:33] <gary_poster> yes, there's more than one or two of those...
[17:04]  * benji lunches.
[17:12] <gary_poster> bac, benji, I added some more versions to my directory in the branch.  2-alt- and 3-alt- add in extra checkboxes for the #3 goal ("(3) (if we can) we do as many of the recommendations as possible plus changes that require more dramatic changes to the events story (i.e., those that would require changes to the server side)").  Similarly, 3-bigger-alt and 4-bigger-alt also add assignee (not particularly well).
[18:39] <bac> gary_poster: i added 4-even-bigger-alt-assignee.bmml
[18:39] <gary_poster> bac, awesome.  I just changed things around a bit, mostly to make the ordering more obvious
[18:39] <gary_poster> about to merge your change, then push
[18:42] <gary_poster> pushed, now looking at your change
[18:43] <gary_poster> Yeah, I thought about that.  We can talk about it.  I'll move it into gary-alt-3 which is the new home of the assignee stuff
[18:46] <gary_poster> bac, your mockup is now gary-alt-3/big-assigneee.bmml .  gary-alt is the original--my proposal for the goal of not changing anything on the server side.  gary-alt-2 has changes for allowing more filtering based on the kind of changes that happen.  gary-alt-3 adds assignee to gary-alt-2
[18:47] <gary_poster> (so gary-alt-2 and gary-alt-3 are both in category 3 of "server side work needed")
[18:47] <bac> ok, it needs server work to filter by assignee?
[18:47] <gary_poster> yeah
[18:48] <gary_poster> it's a proposal because it is one of the recommendations (and it would come in handy for me too)
[18:48] <gary_poster> (as a representative user ;-) )
[18:49] <bac> sure
[20:13] <gary_poster> bac, did you deliver your pngs to mrevell by pointing him to the branch, or some other way?
[20:19] <bac> gary_poster: i put them on people.canonical.com
[20:20] <gary_poster> ok thanks bac
[20:20] <bac> specifically, http://people.canonical.com/~bac/bug-sub-mockups/
[20:49] <gary_poster> bac, I'm going to move your "User testing review with Matthew and design followup card to "Done-done".  Agree?
[20:49] <gary_poster> ...add a quote after "followup"...
[20:50] <gary_poster> the #clojure channel has a n s-expression bot, which is nice.  You can say s/followup/followup"/ and the bot will repeat your statement with the correction
[20:50] <gary_poster> kinda fun
[21:11] <benji> gary_poster: have a second to talk about my current card?
[21:11] <gary_poster> sure benji
[21:12] <gary_poster> here or mumble?
[21:12]  * benji flips a coin
[21:12] <benji> mumble
[21:12] <gary_poster> :-)
[21:12] <gary_poster> k