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