== Meeting information == * #ubuntu-touch-meeting: Music meeting, 15 Jan at 17:00 — 17:33 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2016/ubuntu-touch-meeting.2016-01-15-17.00.log.html]] == Meeting summary == ''LINK:'' http://pad.lv/1534172 ''LINK:'' https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1533779 == Vote results == == Done items == * (none) == People present (lines said) == * karni (78) * popey (62) * ahayzen (60) * Elleo (41) * meetingology (3) == Full Log == 17:00 #startmeeting Music meeting 17:00 Meeting started Fri Jan 15 17:00:39 2016 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 17:00 17:00 Available commands: action commands idea info link nick 17:00 o/ 17:00 hah 17:00 karni, yup :-) 17:00 indeed it is 17:01 for the sake of brevity, if we do talk about it, please let's reference it as "music streaming" :) 17:01 sure 17:01 So typically we use this as a catch up 17:01 coolio :) 17:01 popey, was there any result from the RTM meeting? 17:01 popey, Jim is still investigating things 17:02 Only that the app is currently with QA 17:02 I suggested that they talk to Jim 17:02 They are also testing some other silos 17:02 popey, the case of camera Jim thinks they are using the multimedia not the alert role :-/ 17:02 and they _may_ be building an rc image later today 17:02 but that still doesn't explain why the queue gets cleared lol 17:02 But I wouldn't be surprised if that actually happens next week 17:02 yeah a monday build :-) 17:02 well there is a camera app in the pipeline to land 17:03 so if thats the case then potentially that could be fixed and slipped in with that update 17:03 probably doesn't include a change, unless it was reported 17:03 popey, yeah i say after this we discuss with Jim and decide what actions todo 17:03 heya 17:04 hi Elleo 17:04 ello Elleo 17:04 popey, note that it happens for telegram notifications and screenshoting as well .. so they may need changes we'll see 17:04 Elleo, o/ 17:04 ahayzen: the playlist clearing bug? 17:04 yes 17:05 karni, bug 1534172 17:05 ahayzen: I suppose for any time of notificaiton then :( ? sms, etc 17:05 ugh no bot! https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1534172 17:05 http://pad.lv/1534172 17:05 yeah, saw the bug tho 17:05 nasty 17:05 no, only some 17:05 oh 17:05 karni, some are fine some aren't 17:05 :O 17:05 Jim is chasing 17:05 Ok, so that's on Jim's plate. 17:05 Let's move on :) 17:05 yup 17:06 What do you need from Elleo / karni for music streaming ahayzen ? 17:06 since out last meeting, we had the ListItemLayout and GridView changes land :-) == super fast scrolling 17:06 ok 17:06 for the playback side, as karni was saying we should be able to pass the spotify url straight to the MediaPlayer 17:06 so that seems pretty simple 17:06 for full disclosure I'll say I know as much about cutespotify as ahayzen after the meeting :D 17:06 that is correct, ahayzen 17:07 it's the listing side that is going to be fun, sounds like we can either use libqtspotify? or their web api ? 17:07 then once we can get that into a ListModel like thing...it'll be simple for us to show it as a view 17:07 yeah, web api has the advantage that it's a) not depricated and b) allows for oauth 17:07 so could potentially integrate with online accounts 17:07 so really the questions are how do we get the models 17:07 I wonder what's the best way to expose credentials to the app so that they're not up somewhere in a branch. I think env variables would work. 17:07 but it'd likely be much quicker to just grab stuff from libqtspotify 17:08 karni, weather just stores them in the built click :') 17:08 Elleo: do we *need* online account at this point though? does it make anything easier? 17:08 put creds in ~/.config/com.ubuntu.music/ 17:08 because this is only temporary for now 17:08 popey: +1 17:08 karni: at this point no, but if deciding for the technology to base all the future stuff on it matters 17:08 I'd hard wire them into a file in there, share with developers and people giving demos at MWC 17:08 popey, remember the other day i suggesting a APIKey storing component thing 17:08 :-) 17:08 :) 17:08 ahayzen: that means they'll be somewhere up in JEnkins. as long as this is not public (and I guess it is?) that'd be okay 17:08 karni: I think long term the web api makes more sense, but short term libqtspotify is likely to be much quicker 17:09 +1 17:09 Elleo, agreed 17:09 Elleo: sure, we will definitely make use of online accounts 17:09 Elleo: completely agree 17:09 so it depends on if people mind redoing a bit of stuff between libqtspotify and the web api 17:09 well, for the demo we are only going to show like a basic list IIRC ? 17:09 I just think we should be laser focused and if we don't *have* to do it now, we shouldn't do it. we can easily add it later tho. 17:10 ahayzen: not too much fancy, yes. song list. if we pull it off early enough, perhaps playlist list, but I wouldn't go that far today. 17:10 yeah, so that means minimal tasks to perform with libqtspotify, hopefully 17:10 I agree playlist support is "nice to have" 17:10 tab/page -> song list, touch song -> song plays. 17:10 and just showing the "Starred" list is sufficient for demo. 17:10 yeah, I could take a quick look on sunday and see if I can get libqtspotify exposed to the music app 17:10 popey: +1 17:10 Joe didn't pooh-pooh that idea 17:10 which'd provide you with a list model to play with 17:11 popey: what's pooh-pooh? like boo-boo? :D 17:11 dismiss 17:11 yeah, so it should be a simple as adding the .so into the click ? 17:11 and then it's just music app UI and handing off to media-hub that'd be left to do, if that helps? 17:11 Elleo: well tat would be perfect, though you don't have to give up your weekend for it 17:11 Elleo: very much so :) 17:11 Elleo, yeah from there we can just copy what we do in the Songs tab already ? 17:11 (that just takes a SongsModel from mediascanner2) 17:11 ahayzen: yes (re: .so file) 17:12 ahayzen: I expect so, the exact properties on the model might differ a bit, but otherwise pretty similar 17:12 TBH it's amazing to know music app is pure QML :D 17:12 yeah cool :-) 17:12 I might need to rework the build for libqtspotify a bit, as at the moment I think it gets statically compiled into cutespotify 17:12 Elleo: yeah, this is easily changable in QML though (field names, etc) right :) 17:12 karni, hehe :-D and its still relatively quick :-) 17:12 but that shouldn't be too much work 17:12 Elleo: oh I see 17:13 I'll try work towards documenting how to set up the gst-spotify plugin 17:13 but, long term when we use the webapi. Is that XML/JSON ? as then we should be able to use the XMLListModel right ? 17:13 you can have a quick look here (no notes on installing it though) https://git.launchpad.net/gstspotify/tree/README 17:13 ahayzen: yeah, from a quick glance it seems to provide json at the very least 17:13 ahayzen: didn't see if there was also xml output 17:14 yeah, what Elleo said. JSON, haven't seen XML myself. 17:14 it's a pity there's no JSONListModel haha 17:14 cool, that should be possible todo then 17:15 Elleo: do you think you could expose 3 env vars via QML in libqtspotify? ideally we'd store the credentials nowhere else other than demo devices I'd say. 17:15 otherwise we have to protect the click like hell, so that nobody else "oh shiny!" gives it at try, while others are demoing at the same time.. 17:15 karni: yeah, should be possible 17:16 or what popey said (qt.labs.settings?) in ~/.config/com.ubuntu.music 17:16 We can share the click privately, that's fine. 17:16 karni: I'll just make a quick hacked up version that sticks those env vars in if you try calling the login stuff without credentials 17:16 I'd prefer a file on disk 17:16 that way we don't have to worry too much 17:16 yeah then we can access via Settings {} 17:16 yeah, actually popey's way is nicer 17:16 and if someone does want to try it, they can just put the file in the right place and play using their own api key 17:16 perhaps file on a disk, that we don't have to ship with the click then? 17:16 then I don't need to change libqtspotify at all 17:17 popey: oh yeah, that should work 17:17 ahayzen: +1 17:17 we can just read the settings and pass it via the normal login stuff 17:17 yes, agreed 17:17 \o/ 17:17 \o/ 17:17 hrm. theres one thing though. currently the gst-plugin gets the credentials from env vars (I just literally laughed out loud) 17:17 I guess I'll have to figure this part out 17:18 karni: the docs show it as having parameters for user and pass at least 17:18 karni: maybe just add another for the api key? 17:18 Elleo: they're not part of the track URI though, if that's what you mean 17:18 karni: or better still might be allowing it to just take an auth token, then the user and pass don't have to be passed around so much in a way that's potentially easily introspectable 17:18 karni, could we give something to qtubuntu-media somehow ? 17:19 karni, or is it lower than music ? 17:19 Elleo: actually, they do. I think it's a technical limitation, that you need to pass those for each stream. TBH I'm not sure if we can use different authentication 17:19 karni: ah yeah, sorry I was just thinking from a gstreamer perspective not a media-hub via 17:19 view* 17:19 but I mostly did porting to GST 1.0, I don't know as much about their auth 17:20 this runs with media-hub privileges.. would it have read access to ~/.config/com.ubuntu.music then? 17:20 if so, this would cut it for the demo 17:21 presumably media-hub must have read access everywhere 17:21 karni, hmm is it only the qtubuntu-media side that runs with the same permission as the app ? 17:21 to be able to play music in any app location 17:21 Elleo, you can't play from any location IIRC 17:21 there was something Jim was working on today related to that 17:22 let's shelve this detail, I'll ask around to see how we can get those creds to the gst plugin 17:22 ok 17:22 https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1533779 17:23 Elleo: if you could rework for the libqtspotify not to link statically, that would be great, so we could ship it with the music app 17:23 ahayzen: that's a bit different iirc, that's due to media-hub not being able to cope with the non-click style name for messaging-app 17:23 I have no further questions/comments on the subject right now 17:23 Elleo, yeah just reading it now, it looks like that...i just have a vague memory of something 17:23 karni: sure thing 17:23 We'll need to tweak the build of Music app if we're going to put binaries (libs) in it as it's qml now. 17:24 Or am I misunderstanding the libqtspotify install location? 17:24 popey: for a demo click we can potentially just bundle a precompiled .so and a qmldir file 17:24 popey: we just put it in a subdirectory, so it should be simple 17:24 ok 17:24 \o/ 17:24 I wont worry about that then 17:24 yes, please don't :) 17:24 popey, are Elleo and karni part of the ~music-app-dev team ? 17:25 no but they can be :) 17:25 popey, as then we can have a team branch going 17:25 most probably not 17:25 yeah, pretty sure I'm not at the moment 17:25 but happy to be added :) 17:25 :-) 17:25 :) 17:25 you both are now 17:25 thanks 17:25 great, thanks 17:25 \o/ 17:25 Ok, anything else needing discussion? 17:25 5 mins left 17:26 may I just suggest we don't name it too specifically. say, mwc-demo or streaming or such 17:26 I'm good 17:26 super-secret-branch-that-has-nothing-to-do-with-spotify-honest 17:26 :') 17:26 Elleo: lol 17:26 :) 17:27 streamify lol 17:27 music-streaming seems sane to me 17:27 +1 17:27 sure 17:27 yup 17:27 coolio! 17:27 Ok, we done then? 17:27 Everyone happy? 17:27 :) 17:28 yup \o/ so i guess we need to wait until we get the .so bundled in before we can start properly working on it from the music-app side 17:28 obv we need to poke design but I expect this will be a basic list view for the demo 17:29 yeah. TBH I expect a "fancy" header (not app header, just something above the list) and a list. should be no more than that. 17:29 JMulholland, ^ 17:29 yeah :-) 17:29 iirc there's a bit of text we have to display in the app as well 17:30 ahayzen: yeah, for now (if you really want to haha) you can get as "far" as adding that new dedicated page, a list view with delegate same as regular songs in the music app, and no model :') 17:30 about registered trademarks and being powered by spotify streaming core or similar 17:30 For license compliance? 17:30 yeah 17:30 only if we distribute it, surely? 17:30 good point 17:30 we should check.. 17:30 could put it in the splash screen 17:30 (I admit I facepalmed though) 17:30 guess we all need to acquire spotify accounts... 17:30 got to make sure we don't forget it when fully releasing stuff though 17:31 ahayzen: they're free for 3 or 6 months if you sign up (check it though!). you have to provide a credit card though.. (that I plan to remove myself later) 17:31 i have one, if you don't and you're signing up expressly for this then I think we should pay 17:31 at least for the first year :) 17:31 with the first half free :) 17:31 we could put that through the community donations fund I think. I will speak to dpm about it after the meeting. 17:31 Elleo: yeah. it'll be a while before we release this though, no worry. 17:31 popey: sounds nice 17:32 Ok, we done? 17:32 \o/ 17:32 think we are 17:32 yeah 17:32 thanks guys 17:32 Ok, we all hang out in #ubuntu-app-devel or #ubuntu-media or telegram or whatever 17:32 so we're all easy to find. 17:32 thanks karni Elleo :-) 17:32 Thanks all 17:32 #ubuntu-media is good 17:32 Have a great weekend. 17:32 as not many folks there 17:32 yeah 17:32 yeah, ahayzen +1 17:32 true 17:33 you too, popey :) 17:33 secret :D 17:33 lol 17:33 the more we use that word, the less it is xD 17:33 heh 17:33 heh 17:33 hahaha 17:33 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)