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