== Meeting information ==
 * #ubuntu-touch-meeting: music app meeting, 17 Jul at 11:12 — 12:01 UTC
 * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2014/ubuntu-touch-meeting.2014-07-17-11.12.log.html]]



== Meeting summary ==

''LINK:'' https://code.launchpad.net/music-app/+activereviews https://trello.com/b/Ie2rAS3W/core-apps-management
''LINK:'' https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1341814 
''LINK:'' https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1336563 



== Vote results ==




== Done items ==

 * (none)



== People present (lines said) ==

 * ahayzen (110)
 * popey (68)
 * vthompson (62)
 * nik90 (3)
 * meetingology (3)



== Full Log ==


 11:12 <popey> #startmeeting music app meeting

 11:12 <meetingology> Meeting started Thu Jul 17 11:12:34 2014 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.

 11:12 <meetingology> 

 11:12 <meetingology> Available commands: action commands idea info link nick

 11:13 <ahayzen> https://code.launchpad.net/music-app/+activereviews https://trello.com/b/Ie2rAS3W/core-apps-management

 11:13 <popey> First thing I wanted to mention was that Music is one of the apps we (community team) are super focussed on.

 11:13 <popey> and with only a few weeks until "beta freeze" for phone we need to get things finished off so we can do final testing

 11:14 <popey> thanks ahayzen

 11:14 <ahayzen> super focused...in terms of testing? or missing features? or?

 11:14 <popey> In terms of less of our time is spent on other apps.

 11:14 <popey> for example some of the apps are considered 'done' (bugs aside)

 11:14 <vthompson> So I assume beta freeze would be an image drop to the manufacturers?

 11:15 <popey> but music (and calendar) are two of the apps which have features yet to land

 11:15 <popey> most of the other apps don't have that

 11:15 <popey> hence the focus ☻

 11:15 <ahayzen> hah ok :) i've noticed the bug velocity has increased a bit recently

 11:15 <popey> it's focus in a good way

 11:15 <ahayzen> awesome

 11:15 <popey> beta freeze is when we can't really land new features, it's bug fixes all the way

 11:15 <popey> image will go to manufacturers at end of august

 11:15 <vthompson> So other than specifically content-hub, what else in terms of features are sought for the beta-freeze

 11:16 <popey> we already have devices, and are sending more of them out to people inside the company for more wider testing

 11:16 <ahayzen> when is beta-freeze?

 11:16 <popey> start of august

 11:16 <ahayzen> ok

 11:17 <ahayzen> vthompson, i assume we want searching... and possibly listitem-actions before beta freeze as well?

 11:17 <popey> Of course we can fix things inside the music app which need it

 11:17 <popey> yes ahayzen

 11:17 <vthompson> That'd be my assumption

 11:17 <popey> but anything which requires additional features or fixes in the platform components (like content hub) needs to land asap

 11:17 <ahayzen> yeah because we are a click.... so we need everything that we need to land upstream before that date

 11:18 <ahayzen> ok so these are the ones i would push tim to do...

 11:18 <ahayzen> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1341814

 11:18 <vthompson> IMO that means the content hub integration, media-hub fix for seeking, ms2 update for any content-hub needs, and possibly an SDK fix for both searching and for a panel issue we have

 11:18 <ahayzen> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1336563

 11:19 <vthompson> Yep, those are the 2 SDK bugs

 11:19 <ahayzen> vthompson, IIRC jim said he would be working on media-hub things hopefully next week (to get the backgroundplaylists done as well)

 11:19 <ahayzen> we badly need ^^ to land

 11:20 <vthompson> ahayzen, I hope we have time to let Jim patch up any issues we might find after it lands

 11:20 <ahayzen> ms2 we need the streaming mp to land https://code.launchpad.net/~jamesh/mediascanner2/streaming-model/+merge/226249 ... and we need that helper they propose to write to be QML

 11:20 <vthompson> because the background playlists, while seemingly seamless, might have issues

 11:21 <ahayzen> popey, beta-freeze is like FF so 'fixes' can land but not new features after...or am i missunderstanding?

 11:21 <popey> yes

 11:21 <popey> beta should be bug free of course ㋛

 11:21 <ahayzen> <jhodapp> I'm trying to finish up audio recording this week since feature freeze is Friday

 11:21 <ahayzen> <jhodapp> and then I can start on that next week is what I'm thinking as a bug fix

 11:21 <vthompson> and that includes packages like media-hub, ms2, etc?

 11:21 <popey> yes

 11:21 <ahayzen> 'that' being background playlists

 11:23 <vthompson> of the remaining MPs in review, maybe we should put the now playing/queue split on the back burner?

 11:23 <ahayzen> ok so what we have left that we 'want' to land in terms of features...

 11:23 <ahayzen> - searching, - listitem actions, - background playlists

 11:23 <ahayzen> vthompson, +1 yeah probably best to leave that

 11:23 <ahayzen> oh and i've been playing about with bottom edge

 11:23 <ahayzen> then any addition general fixes

 11:24 <ahayzen> then for searching we need that SDK fix

 11:24 <ahayzen> listitem actions is still WIP and we need to confirm design

 11:24 <vthompson> if we could get bottom edge in that would be nice. Also Jamie filed a bug for fast scroll in the Songs tab, IMO we should try to integrate that as well

 11:24 <ahayzen> background playlists we need to write once we know what it will look like

 11:24 <ahayzen> and content-hub!

 11:25 <ahayzen> vthompson, oh yeah there was a discussion on irc about that nik wanted to add it to the clock as well

 11:25 <popey> the fast scroll that you see in contacts app?

 11:25 <vthompson> ah for the list of cities

 11:25 <ahayzen> vthompson, it should hopefully be quite simple to do

 11:25 <vthompson> yep

 11:25 <popey> ok

 11:25 <vthompson> popey, yep

 11:25 <ahayzen> yeah cities and popey yes

 11:25 <vthompson> it looks very simple to integrate, I had a look last night

 11:25 <ahayzen> :)

 11:26 <ahayzen> even if we just had it on the Tracks

 11:26 <vthompson> I'd like it on Artists as well

 11:26 <ahayzen> yeah ideally in the same places u can search

 11:26 <ahayzen> artists/albums/songs

 11:27 <vthompson> Albums would be more difficult probably. But that might just be an orientation thing

 11:27 <ahayzen> oh yeah

 11:27 <ahayzen> artists/songs then

 11:27 <ahayzen> popey, ^^ where do u think for fast scroll?

 11:27 <popey> depends how big your music collection is

 11:27 <popey> ☻

 11:27 <ahayzen> hah

 11:28 <popey> so not playlists, but album & artist certainly

 11:28 <vthompson> I'd like albums as well, but we kind of have a space limitation at the bottom of the device on that tab

 11:28 <popey> s/artist/songs/

 11:28 <ahayzen> popey, album goes horizontally

 11:28 <popey> oh of course.

 11:28 <ahayzen> so artists/songs

 11:28 <popey> yes

 11:29 <ahayzen> if we land searching u'll be able to search ur albums anyway

 11:29 <popey> However, these I think are much lower priority than content-hub and ms2 related work.?

 11:29 <vthompson> we could add and underlay on the fastscroll to do it ontop of the bottom of the albums tab, but we should get the other 2 tabs working first

 11:29 <ahayzen> yep content-hub needs badly doing

 11:29 <ahayzen> popey, and even bottom edge maybe?

 11:29 <vthompson> yea, but we might be waiting for the ms2 stuff to be finalized and that impacts content-hub

 11:30 <ahayzen> yeah we are blocked wth content-hub

 11:30 <ahayzen> popey, is Jouni likely to reply quickest for confirmation of the listitem actons?

 11:30 <popey> yes

 11:30 <ahayzen> vthompson, is the only issue left with that the background disappearing too fast?

 11:31 <ahayzen> (the labels i fixed last night)

 11:31 <vthompson> ahayzen, I believe so, aside from any design/SDK assumptions we might be making

 11:31 <ahayzen> popey, ok i'll try and mail him for confirmation tonight

 11:31 <popey> whats the question?

 11:31 <popey> we can ask him now ☻

 11:31 <ahayzen> popey, the sliding

 11:32 <ahayzen> popey, so should the listitem's actions be 'revealed' or 'bound' to the item

 11:32 <vthompson> Can we just get that sorted in person during the hangout for the new design?

 11:32 <vthompson> probably easier to describe that way

 11:32 <popey> either jouni or ben should be able to answer that

 11:32 <popey> its a simple fix once you know the answer, right?

 11:33 <ahayzen> popey, erm 'simple' ish...bit of logic changes but it should be ok...i'm gonna do a final refactor tonight which should make it easier to swap

 11:33 <popey> ok

 11:34 <ahayzen> i've gone the other way...so it should just be reverting my changes lol

 11:34 <vthompson> Could we get this little MP reviewed? https://code.launchpad.net/~vthompson/music-app/consistent-icons/+merge/226597

 11:34 <ahayzen> vthompson, yep

 11:34 <ahayzen> vthompson, and what was our decision on https://code.launchpad.net/~vthompson/music-app/fix-playlist-keyboard/+merge/226402

 11:34 <vthompson> The main thing I'd like input on is which icon makes sense for "queue" and which makes sense for "playlist"

 11:35 <popey> ahayzen: which one did you go for?

 11:35 <ahayzen> vthompson, ok i'll check that out tonight

 11:35 <popey> bound or uncovered?

 11:35 <ahayzen> popey, uncovered at the moment as that is what the design spec implies

 11:35 <vthompson> ahayzen, if some of those keyboard fixes won't land by RTM I'd like to land that workaround. but otherwise we can ignore the keyboard issue

 11:35 <popey> yes, i think thats right

 11:35 <popey> ← not a designer

 11:35 <ahayzen> vthompson, surely they will land before rtm... i had that bug when sending a text the other day really annoying

 11:36 <vthompson> I'll mark the keyboard MP as WIP. If it gets close to RTM and it isn't resolved we can merge it

 11:36 <ahayzen> yep agreed

 11:37 <ahayzen> popey, basically a mash up of these two bugs upstream https://bugs.launchpad.net/ubuntu-keyboard/+bug/1324955 https://bugs.launchpad.net/ubuntu-keyboard/+bug/1305999

 11:37 <ahayzen> popey, so if you are typing with autocomplete the text isn't committed until u press space or enter...so if the text is still purple when you hit a 'save' or 'send' button that word isn't actually in the box

 11:38 <popey> should music even use autocomplete?

 11:38 <popey> i would switch it off

 11:38 <ahayzen> popey, for creating playlist names...we are unsure

 11:38 <popey> yes, off all the time in music app imo

 11:38 <vthompson> that was my idea as well, popey, but if the word gets committed to the box autocomplete isn't too bad

 11:38 <ahayzen> agreed to both! lol

 11:38 <vthompson> if my playlist is called "running" it might be nice to have it suggested to me

 11:39 <vthompson> as I type

 11:39 <ahayzen> yep

 11:39 <popey> hm

 11:39 <popey> how often do you create playlists?

 11:39 <vthompson> me? never

 11:39 <ahayzen> i don't much but i know others use it alot

 11:39 <popey> I mean, I can understand it for creating content in sms and email

 11:39 <popey> but for this, it seems unnecessary

 11:40 <ahayzen> hmmm maybe disable predictive for now until it is fixed upstream then reeval?

 11:40 <vthompson> ahayzen, I could agree to that.

 11:40 <popey> i would use the hints to turn it all off for now, yes.

 11:40 <ahayzen> ok

 11:40 <vthompson> I also think that predictive is kinda garbage right now... so I'd like to have that be sufficient prior to using it

 11:40 <vthompson> marking as ready for review then

 11:41 <popey> +1

 11:41 <ahayzen> cool i'll approve thatwhen i get back

 11:42 <ahayzen> ok so i'll fix listitem actions tonight, continue working on bottom edge

 11:42 <ahayzen> searching and content-hub are blocked upstream

 11:42 <vthompson> the fix for listitems is just refactor right?

 11:42 <ahayzen> what was our decision on asking design about listitem actions

 11:42 <vthompson> I just say we ask during the new design hangout.

 11:42 <ahayzen> vthompson, yeah now we are using the default property i think it could be simpler

 11:43 <vthompson> k

 11:43 <ahayzen> or 'less hacky' :)

 11:44 <vthompson> I had added Zsombor as a reviewer for the listitem-action MP. I think he should also concur with our direction being similar to the direction the SDK team is taking

 11:44 <popey> he's still afk on vacation right?

 11:44 <vthompson> If design decides to change the behavior, maybe we'll still leave it as-is if that's not what the SDK will be delivering

 11:44 <vthompson> oh I had no idea

 11:45 <ahayzen> hah

 11:45 <ahayzen> yeah i suppose we could leave as is then just migrate to sdk when that lands

 11:46 <ahayzen> (most likely post rtm)

 11:46 <popey> yeah

 11:46 <ahayzen> so is there anything else we need todo?

 11:47 <popey> I think that's sufficient!

 11:47 <vthompson> I wanted to poke the hornets nest back when we had more time to change the design, but we really don't have that luxury now

 11:47 <ahayzen> vthompson, i think we need to investigate statesaver || sql for playlists & recent

 11:47 <popey> Now, I'm on holiday next week, so dpm, mhall119 and balloons can of course help should you need it when I'm not around.

 11:47 <ahayzen> as we have some bugs in playlists atm :/

 11:47 <vthompson> ahayzen, actually statesaver is currently only used for when the app crashes

 11:48 <ahayzen> popey, k noted have a good holiday :)

 11:48 <vthompson> I think they changed it because saving the state/serializing is too expensive

 11:48 <ahayzen> ok

 11:48 <ahayzen> so i'll checkout patching the sql as well then :)

 11:48 <vthompson> nik90 had said that they might reintroduce statesaver for normal use and lifecycle, but I'm not sure when they'll do that

 11:50 <nik90> vthompson: yeah I wouldn't wait for that before the rtm as they are prioritizing the work they do

 11:50 <nik90> oh hi btw :)

 11:50 <ahayzen> o/

 11:50 <vthompson> nik90, o/ didn't mean to summon you ;)

 11:50 <nik90> lol

 11:51 <vthompson> popey, ahayzen, I had one more thought earlier with regard to search

 11:51 <ahayzen> vthompson, ok so we need to checkout the sql then...so what do we do with the 'deleted' tracks as when we 'fix' the db they will be resurrected

 11:51 <popey> go on..

 11:51 <vthompson> Should we think about introducing a Genre tab? This would allow search for Genre

 11:51 <ahayzen> post rtm with the new design?

 11:52 <vthompson> One of the bacon bugs was about genres being hard to navigate. I don't browse my music by genre, but if it's common having a tab and the ability to search on it would be nice

 11:52 <popey> i never use genre

 11:52 <vthompson> I'm suggesting pre-rtm

 11:52 <ahayzen> think we already have enough things todo before rtm ...and genres most people don't use genre

 11:53 <ahayzen> and we have genre in the start page which is probably enough for now

 11:53 <vthompson> ok, since it's 3 against Bacon and he isn't here to defend his position, we'll call him a unique user in this regard

 11:53 <vthompson> :)

 11:53 <ahayzen> +1

 11:53 <ahayzen> hehe

 11:53 <popey> +1

 11:54 <popey> he's dead to us.

 11:54 <ahayzen> :(

 11:54 <popey> j/k

 11:54 <ahayzen> anyway anything else?

 11:54 <vthompson> nothing from me

 11:54 <popey> I think not.

 11:54 <ahayzen> do we need to poke the ms2 guys?

 11:54 <popey> Thanks so much guys for the hard work as we lead up to RTM

 11:54 <ahayzen> with that extra qml thing we need

 11:55 <vthompson> Jussi just replied to the email thread

 11:55 <ahayzen> np we'll get there

 11:55 <ahayzen> ah lol

 11:55 <ahayzen> ok nothing else from me then

 11:55 <vthompson> he's suggesting we don't add the QML piece... which we'll have to find a way to build something to access the backend

 11:55 <ahayzen> oh god

 11:56 <vthompson> (I'm still against getting the metadata at all though)

 11:56 <ahayzen> ok well jim said he could relink the metadata in MediaPlayer if needed

 11:56 <ahayzen> as all it is missing is the onchanged signal being raised

 11:56 <popey> We don't have long to sort this, so we need to come up with a plan either way.

 11:56 <ahayzen> so would that resolve the issues?

 11:56 <ahayzen> if we then had streaming model as well

 11:56 <vthompson> jim's plate is rather full

 11:56 <ahayzen> hah :/

 11:57 <vthompson> I want the basics working in ms2 with the streaming so we can even import the file in the ~/Music

 11:57 <ahayzen> yeah but still need to know what to call the file

 11:57 <vthompson> There's still a chance that the metadata pulled from media-hub would mismatch the ms2 data and then the destinatino of the file is not as accurate

 11:58 <vthompson> call it what it was called when d/l'ed

 11:58 <ahayzen> jhodapp> ahayzen: media-hub can supply it, but it's not hooked up yet in qtubuntu-media

 11:58 <ahayzen> <jhodapp> ahayzen: no unchanged

 11:58 <popey> I still vote for ./Downloaded/YYYYMMDDHHMMSS-foo

 11:58 <popey> or similar

 11:59 <vthompson> popey, +1

 11:59 <ahayzen> ok well we could prompt the user (as with current designs)

 11:59 <vthompson> my idea was ~/Music/imported/...

 11:59 <popey> +1

 11:59 <ahayzen> with it prefilled with ~/Music/Imported/YYYYMMDDHHMMSS-foo.ext

 11:59 <ahayzen> ok we'll do that then

 12:00 <popey> Ok. we done?

 12:00 <ahayzen> right thats all from me i gtg now o/

 12:00 <vthompson> yep!

 12:00 <popey> Thanks ahayzen vthompson !

 12:00 <popey> Have a great day.

 12:00 <ahayzen> popey, thanks have a great holiday :)

 12:00 <vthompson> bye popey, ahayzen, (nik90)!

 12:00 <popey> \o/

 12:01 <ahayzen> vthompson, cyas later :)

 12:01 <popey> #endmeeting



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