15:08 <popey> #startmeeting Calculator meeting 15:08 <meetingology> Meeting started Thu Jun 11 15:08:31 2015 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 15:08 <meetingology> 15:08 <meetingology> Available commands: action commands idea info link nick 15:08 <popey> rpadovani: I submitted calculator for QA approval 15:08 <rpadovani> popey, seen the mail \o/ 15:09 <popey> r182 15:09 <popey> oh yes, I cc'ed you :) 15:09 <popey> duh 15:09 <popey> sorry, long day :) 15:09 <rpadovani> popey, np :-) Well, apart of this, don't think there are news 15:10 <nik90> hey guys, who is working on implementing the new designs for the calculator app which are shown at https://docs.google.com/presentation/d/1EiIELGizPHrd0TY7JdNwULbiqPYfOyEEI5CS87n7QlY/edit#slide=id.g7b6f8ee55_01 ? 15:10 <rpadovani> popey, do you think update will be included in OTA-4? 15:10 <nik90> they look really good and would be nice to have ;) 15:10 <rpadovani> nik90, actually, we haven't started yet, also because some things are to be finalized 15:11 <rpadovani> nik90, they miss some usercases 15:11 <nik90> rpadovani: ah ok 15:11 <rpadovani> nik90, anyway, if you want to do some branches, you're more than welcome, I don' t have time yet 15:12 <nik90> I dont mind touching some really low hanging fruits like updated buttons layouts etc without braking autopilot hopefully 15:12 <popey> That would be awesome. 15:12 <popey> We got that new New NEW set of designs after we'd just finished the previous new New ones 15:13 <popey> So we decided to get the older one out the door, into the store, first 15:13 <nik90> ack. 15:13 <popey> Would be great to break up those new ones and start working on them 15:14 <nik90> I need more details like the color hex to use, sizing etc that the presentation doesnt seem to have 15:14 <popey> We can get that from james when he returns from holiday next week. 15:14 <nik90> I notice a dropbox link on slide 5 that links to more visual designs but it seems broken 15:14 <nik90> ok 15:16 <popey> probably because that person left the company 15:16 <popey> will have to get a new link, hosted somewhere else 15:17 <popey> I'll mail James and ask. He can look when he's back. 15:17 <nik90> ok 15:18 <popey> done. 15:20 <rpadovani> thanks nik90! 15:20 <popey> So the big question is how much of this can be done incrementally? 15:20 <popey> Or does it need a "reboot" 15:20 <nik90> I don't think we would need another reboot IMHO. I'll let rpadovani confirm that since he is more familiar with the codebase 15:21 <nik90> I would first start with the button rearrangement, followed by bottom edge rewrite from Favourites to History 15:21 <nik90> I don't see anything else new compared to the calc app in the store atm 15:22 <popey> Agreed. 15:22 <rpadovani> I confirm what nik90 is saying 15:22 <popey> Ok, good. 15:23 <rpadovani> the thing that need more works is autopilot tests I think 15:23 <popey> In what way? 15:23 <popey> Need more of them or need love to existing ones? 15:23 <rpadovani> all our tests check history, but if we move history to bottom edge, all tests have to open history first 15:24 <rpadovani> we just have to edit them when we edit the design 15:24 <popey> Right, that's expected, of course. 15:25 <popey> However, if we make significant design changes, which break AP tests, I would rather disable a test while we prototype and manually test and review it 15:25 <popey> then fix the AP test after 15:25 <popey> rather than constantly iterate both the app and the test together, which will slow everything down 15:25 <popey> IMO 15:25 <popey> Other opinions sought.... 15:26 <popey> I suspect what I said may give balloons a heart attack 15:26 <popey> :) 15:26 <nik90> lol 15:27 <rpadovani> I like that approach :D 15:27 <balloons> rofl 15:27 <nik90> I will stay neutral in this topic :P +0 15:27 <balloons> design changes can happen first.. but once finished it makes sense to update the tests 15:28 <balloons> if you have to scale back on the number at first, I guess so be it. But landing a big feature without tests is :-) 15:28 <balloons> ymmv 15:28 <rpadovani> tbh I think autopilot tests changes are not so big, now I think well 15:29 <rpadovani> because we can just inject a function to open bottomedge 15:29 <popey> Up to you guys really. 15:29 <rpadovani> and I'm sure somewhere there is already one 15:29 <balloons> also remember to right-size your testing. We have some tests that might make more sense as lower level tests; which are not as fragile 15:29 <popey> I just don't want us to spend 80% on tests and 20% on functionality 15:29 <popey> which is what we seem to do in some projects :S 15:29 <balloons> and easier to right 15:29 <balloons> *write 15:30 <rpadovani> well, we start from changes that dont break autopilot 15:30 <rpadovani> we have to define some features yet 15:30 <rpadovani> with new design 15:30 <rpadovani> I've the same perplexity I had two months ago 15:31 <popey> Ok, so maybe hangout with james next thursday? 15:31 <popey> I plan to meet with him before then, so can prep him for your "perplexity" 15:32 <rpadovani> sounds good 15:33 <popey> Ok, so anything else we should discuss? 15:34 <rpadovani> not on my side 15:34 <nik90> I will come up with these branches this week..I will propose them using a common branch that all members of the calculator app team can write to 15:34 <nik90> this way someone else can pick up my work in case I cannnot complete it 15:34 <popey> Awesome, thanks nik90 15:35 <rpadovani> thanks nik90 ! 15:35 <popey> Have a great weekend guys. 15:35 <popey> #endmeeting