== Meeting information ==
 * #ubuntu-touch-meeting: Docviewer meeting, 03 Dec at 14:48 — 15:27 UTC
 * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2015/ubuntu-touch-meeting.2015-12-03-14.48.log.html]]



== Meeting summary ==




== Vote results ==




== Done items ==

 * (none)



== People present (lines said) ==

 * popey (65)
 * sverzegnassi (51)
 * meetingology (3)



== Full Log ==


 14:48 <popey> #startmeeting Docviewer meeting

 14:48 <meetingology> Meeting started Thu Dec  3 14:48:22 2015 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

 14:48 <meetingology> 

 14:48 <meetingology> Available commands: action commands idea info link nick

 14:48 <popey> sverzegnassi, hello!

 14:48 <sverzegnassi> hey, popey!

 14:48 <sverzegnassi> thanks!

 14:48 <popey> Hows it going?

 14:49 <sverzegnassi> fine, thanks! just finished the lesson! you?

 14:50 <popey> Great!

 14:51 <sverzegnassi> :)

 14:51 <sverzegnassi> I guess one of the today arguments is the release date. am i wrong?

 14:51 <popey> Ya!

 14:51 <popey> That's the main topic I think :)

 14:52 <popey> I'm just building trunk now for a bit of testing

 14:52 <sverzegnassi> I'm extensively testing docviewer since yesterday, and it seems ready

 14:52 <popey> \o/

 14:52 <sverzegnassi> I've found a couple of issue that could be suitable for the code-in

 14:52 <sverzegnassi> not big issue, just small UI fixes

 14:53 <popey> Oh great.

 14:53 <sverzegnassi> I will open new reports as soon as I get home

 14:53 <popey> ok.

 14:53 <popey> So I'm building it now, will test on my devices. Any reason not to upload later today?

 14:54 <sverzegnassi> translations?

 14:54 <popey> yeah, true.

 14:54 <sverzegnassi> (just brainstorming some reason)

 14:55 <popey> ah okay

 14:55 <popey> Hm, maybe best to wait until tomorrow morning

 14:55 <popey> so we get one more night of translation imports from launchpad?

 14:55 <sverzegnassi> ok. sounds reasonable to me!

 14:56 <popey> Because otherwise I'll upload this, then more translations come in, and everyone gets a 66MB download again next week when I push an update :)

 14:56 <popey> Ok, I'll do that tomorrow, and take a look at the state of translations.

 14:56 <sverzegnassi> do we still have the record for the biggest app in the store? is it true?! :D

 14:57 <popey> haha, sadly not

 14:57 <sverzegnassi> haha

 14:57 <popey> lets see...

 14:58 <popey> well, if I made a multi-arch package it _would_ be the biggest

 14:58 <popey> but I think phone users would complain about having 120MB of x86/amd64 binaries on their device

 14:58 <popey> so I won't do that

 14:58 <sverzegnassi> heh, it's better to avoid that

 14:59 <sverzegnassi> ok, two other questions i have:

 14:59 <popey> yeah

 14:59 <sverzegnassi> 1) trying to spot some tasks for the code-in, I've seen that we have 5 different styles for the empty state

 14:59 <popey> Across different apps?

 15:00 <sverzegnassi> yes. clock, docviewer, calculator use the same one

 15:00 <sverzegnassi> notes use its own, as also does address-book and others

 15:00 <sverzegnassi> the question is: given that we use the same strings in the same scenario of music-app (documents not found)

 15:01 <sverzegnassi> a task was to use the same style. so I was looking for the music-app design specs

 15:02 <popey> hmmm

 15:03 <popey> trying to find a document

 15:04 <sverzegnassi> well, i could simply have a look at the music-app code. my request was meant to make a similar task more "official" whenever it would be picked by some google code-in'r

 15:04 <popey> To make the apps consistent?

 15:04 <sverzegnassi> that's the goal

 15:05 <popey> Would need design input on that, for sure. I don't know which would be most current, or most correct from the design point of view.

 15:05 <popey> (as an aside, I just build docviewer and the .desktop file still referrs to the old icon filename - Icon=docviewer@30.png - so the new icon doesn't show up

 15:06 <popey> (unless I built it wrong)

 15:06 <sverzegnassi> when you tap and hold in the app scope?

 15:06 <sverzegnassi> I have installed it on my phone. i have the new icon

 15:06 <popey> hmmm

 15:07 <sverzegnassi> (well, the phone didn't had a previous release, since I flashed rc-proposed yesterday)

 15:07 <popey> I'll do a clean build.

 15:08 <popey> Ok, so for the empty state, we should get info from design on which is the preferred way, and modify the offending apps, right?

 15:08 <sverzegnassi> yes

 15:09 <popey> so that would include clock/doc/calc/notes which are all probably the wrong ones, if address-book is different

 15:09 <sverzegnassi> the most recent is the one from music-app (Jan 15 vs Sep 14)

 15:09 <popey> hm, okay.

 15:09 <sverzegnassi> didn't check for address-book to be honest

 15:09 <popey> We can get the right answer from design.

 15:09 <sverzegnassi> :D

 15:10 <sverzegnassi> ok, second question is about planning the next release

 15:10 <sverzegnassi> while i don't want to discuss about the single tasks yet,

 15:10 <sverzegnassi> i wonder if we should still kept the weekly planning

 15:10 <sverzegnassi> s/planning/milestones

 15:11 <sverzegnassi> or track them just every month

 15:11 <sverzegnassi> (and ideally release a new eversion every month)

 15:11 <popey> Monthly seems sensible to me.

 15:12 <popey> maybe every few months we sync the libreoffice build too

 15:12 <popey> but not every month

 15:13 <sverzegnassi> yeah, libreoffice sync should not follow that timing

 15:13 <popey> ok.

 15:13 <sverzegnassi> don't they release every six months?

 15:14 <popey> yeah, but they do security updates too

 15:14 <popey> and bug fixes etc

 15:14 <sverzegnassi> yeah, sure!

 15:15 <popey> So yes, monthly milestones. Or six-weekly if you want to be in sync with OTA updates

 15:15 <popey> 6-weeks feels too long to me, what do you think?

 15:15 <popey> (rebuilt docviewer and have the right icon now) :)

 15:16 <sverzegnassi> that was also my idea (6-week). then I thought that the last week could be useful for updating translations

 15:16 <sverzegnassi> it's up to you... for sure you have more experience than me :)

 15:16 <popey> Heh, okay.

 15:17 <popey> Yeah, 6-week cycle with focus on QA in week 5 and translations in week 6 ?

 15:17 <sverzegnassi> +1

 15:20 <popey> Excellent.

 15:20 <popey> in sync with OTA or offset?

 15:20 <popey> probably easier to do it in sync

 15:20 <popey> we can use the same milestone names etc.

 15:21 <sverzegnassi> yes! also, in case we need to do such tasks as the migration to uitk 1.3

 15:21 <sverzegnassi> it would be easier

 15:22 <popey> +1, agreed.

 15:23 <popey> Ok, anything else to discuss?

 15:23 <sverzegnassi> ok, that's all from me!

 15:23 <popey> Ok. I'll grab some new screenshots for the store, and add the new icon when I upload tomorrow.

 15:24 <sverzegnassi> great!

 15:24 <popey> Any documents you suggest for screenshots?

 15:24 <popey> Something complex :)

 15:25 <popey> the e4.5 manual is an obvious choice, a spreadsheet and a presentation too would be good.

 15:25 <sverzegnassi> some spreadsheet with charts?

 15:25 <popey> yeah

 15:25 <popey> I have a sheet with a couple of simple charts in, good idea

 15:25 <popey> Expect to see bug new reports over the weekend :)

 15:26 <popey> Ok, I had nothing else either. Thanks for getting this all ready for release, really looking forward to seeing it on devices.

 15:26 <sverzegnassi> i'm sure of that. let the spam begin! :)

 15:26 <popey> haha

 15:27 <sverzegnassi> It has been fun to work on this! :)

 15:27 <popey> Have a great weekend sverzegnassi, I'll ping you a mail when it's in the store, and you can announce it on your social stuff.

 15:27 <popey> \o/

 15:27 <sverzegnassi> ok, thanks!

 15:27 <sverzegnassi> have a great weekend you too, popey!

 15:27 <popey> #endmeeting



Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)