21:56:53 < akrane> do you have burning questions re: 009 tickets?
21:57:12 <@rmurphey> i think jeremy has some 009 points to discuss with you
21:57:32 <@rmurphey> my personal opinion is that none of the mobile stuff can or should happen in 009

21:58:00 <@rmurphey> it is not sufficiently spec'd and there is not time to sufificiently spec it and do so such that we will not revisit
                     it yet again in two more weeks
21:58:28 < akrane> if you would like to discuss that, pls be more specific on what is "not sufficiently specc'd"
21:58:36 <@rmurphey> every ticket beginning with mobile:
21:58:51 <@rmurphey> but i'd prefer that you discuss it with jeremy
21:59:02 < akrane> it sounds like i will.
21:59:31 <@rmurphey> it seems to me that generally we are trying to do too much front end stuff in a release and that we are doing it
                     without sufficient consideration of it
21:59:45 <@rmurphey> which leads to redoing the work in following weeks
22:00:08 < akrane> i'm clear that this is your concern.
22:00:13 <@rmurphey> and that we should instead be doing focused, well-considered changes
22:00:38 < akrane> so you are opposed to putting feeds onto mobile
22:00:44 <@rmurphey> i want us to understand what the feeds feature *is* before we try to deploy it to mobile
22:00:51 <@rmurphey> i want to flesh it out on desktop
22:01:05 < akrane> that's not our strategy, actually
22:01:08 <@rmurphey> well

22:01:10 < akrane> if anything, we should be flushing out on mobile first
22:01:15 <@rmurphey> then i'll leave it to jeremy to discuss
22:01:16 < akrane> because mobile is more important.
22:01:19 < akrane> ok.
22:01:37 <@rmurphey> that is my opinion, with which he seemed to agree yesterday
22:01:44 <@rmurphey> not from a strategy standpoint
22:01:50 <@rmurphey> simply from the standpoint of what makes sense
22:02:00 <@rmurphey> the mobile tickets yet again undo a bunch of work i just did
22:02:10 < akrane> the tabs?
22:02:17 <@rmurphey> and i simply do not believe that the tickets have been sufficiently considered to merit us working on them now
22:02:35 <@rmurphey> considering that they weren't even in 009 until yesterday
22:03:03 < akrane> clearly I have misunderstood what jeremy meant when he suggested doing mobile stuff next week instead of the originally
                   planned features.
22:03:12 < akrane> but i will discuss this with him, as it is probably more productive.
22:03:22 <@rmurphey> will he be around this evening?
22:03:33 <@rmurphey> it seems at this point that no qa is going to happen befor emonday

22:03:43 < akrane> correct.
22:03:51 <@rmurphey> that is frustrating to me
22:03:55 <@rmurphey> i dropped a qa release on friday
22:04:00 <@rmurphey> we could have identified these issues then
22:04:09 <@rmurphey> instead we didn't identify them til almir had left
22:04:42 < akrane> who's fault
22:04:46 <@rmurphey> dunno
22:04:58 <@rmurphey> can't say it's anyone's just that's what happened
22:05:15 < akrane> i'm going to talk to jeremy about 009.
22:05:21 < akrane> we will decide what to do.
22:05:30 < akrane> i'm happy to incorporate you into that decision if you wish,
22:06:11 < akrane> however, that would necessitate you being more open minded and flexible
22:06:17 <@rmurphey> well
22:06:22 < akrane> and not constantly questioning the direction
22:06:23 <@rmurphey> i'm just caling it how i see it
22:06:29 <@rmurphey> the mobile tickets are simply not ready

22:06:30 <@rmurphey> period
22:07:00 <@rmurphey> and
22:07:01 <@rmurphey> again
22:07:17 <@rmurphey> i simply do not believe that they have been considered sufficiently such that they merit development time being spent
                     on them
22:07:19 < akrane> i shouldn't be talking ot you about this. i''ll talk to jeremy.
22:07:46 < akrane> feel free to be more specific w/ respect to actual tickets
22:07:50 <@rmurphey> and that's not questioning strategy

22:07:58 <@rmurphey> that's just saying, they're not ready
22:08:37 < akrane> again, specific feedback (in tickets) would be appreciated
22:08:51 < akrane> stylistic tickets lack spec
22:08:56 < akrane> my hope is that at this point you can inuit
22:09:07 <@rmurphey> here's the thing
22:09:21 <@rmurphey> how are these designs different from the multiple previous designs i've implemented?
22:09:21 < akrane> i rushed to make these tickets because i *thought* you were in favor of doing mobile
22:09:24 < akrane> rather than new features.

22:09:28 <@rmurphey> i never said
22:09:30 <@rmurphey> that
22:09:34 < akrane> ok, well,
22:09:45 < akrane> re: your question: these designs are for a *new feature*&
22:09:51 < akrane> these designs are for *feeds*
22:09:57 < akrane> it does not exist on mobile, therefor is not being redesigned
22:09:59 <@rmurphey> the games list are a new feature?
22:10:04 <@rmurphey> the tabs are a new feature?
22:10:06 <@rmurphey> no they're not

22:10:30 < akrane> like i said, if you have a problem with a ticket, respond in kind ot that ticket, don't categorically reject the
                   entirity of mobile
22:10:33 <@rmurphey> i feel like these designs have been rushed to meet a timeline instead of considered so as not to spend yet more dev
                     time on yet more code that will only be discarded
22:11:02 <@rmurphey> #1463: not a new feature
22:11:05 < akrane> that's not true. we decided to get rid of tabs weeks ago
22:11:09 <@rmurphey> #1461: not a new feature
22:11:24 < akrane> do you want to chat on skype about this
22:11:25 <@rmurphey> #1464: not a new feature
22:11:26 < akrane> or just drop it
22:11:33 <@rmurphey> please talk to jeremy and let me know the outcome