--- Log opened Sat Nov 11 00:00:20 2017
00:22 -!- Horwitz [~mich1@p200300800E57D800022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
00:35 -!- Horwitz [~mich1@p200300800E564400022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
00:35 -!- mode/#navit [+o Horwitz] by ChanServ
00:39 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/osm-exp/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/n
00:39 #navit: < Navit> oad.navit-project.org/logs/navit/android_armv4t/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-.failed
00:39 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
01:30 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 240 seconds]
01:39 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
03:45 -!- noradtux [~noradtux@2a02:2028:70e:3a01:ec4:7aff:fe33:3dc1] has quit [Ping timeout: 240 seconds]
03:52 -!- noradtux [~noradtux@2a02:2028:622:e501:ec4:7aff:fe33:3dc1] has joined #navit
04:55 -!- charles__ [48241adf@gateway/web/freenode/ip.72.36.26.223] has quit [Ping timeout: 260 seconds]
05:07 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
06:32 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Ping timeout: 248 seconds]
09:16 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
10:43 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 240 seconds]
13:37 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
14:59 -!- Charles__ [48241adf@gateway/web/freenode/ip.72.36.26.223] has joined #navit
15:11 #navit: < Charles__> https://github.com/navit-gps/navit/pull/367
20:01 #navit: <@KaZeR> thanks Charles__ 
20:09 #navit: <@KaZeR> jkoan: check out mvglasow's updates on the wiki. you're going to like it
20:17 #navit: < ilovekiruna> KaZeR: which updates do you talk about?
20:25 #navit: < ilovekiruna> KaZeR: found now, pretty nice. I also like it :)
20:27 #navit: <@KaZeR> :)
20:40 #navit: < ilovekiruna> i just checked, we still have to wait to c what happened to fosdem, no news yet
20:44 #navit: <@KaZeR> was about to ask actually. thanks for the update!
20:44 #navit: < ilovekiruna> status is still undecided
20:44 #navit: < ilovekiruna> I guess it will take a while
20:45 #navit: < ilovekiruna> 1 November onwards
20:45 #navit: < ilovekiruna>     main track talks announced (in batches)
20:45 #navit: < ilovekiruna> this is what the website says
20:46 #navit: < ilovekiruna> KaZeR: do you know if youte has any promo material in the works I should take with me?
20:55 #navit: <@KaZeR> don't think there's something yet, but we could get several members involved to do it
20:56 #navit: < ilovekiruna> ofc, that's why i brought it up
20:56 #navit: < ilovekiruna> u know some cards or stickers could be still cool
20:56 #navit: < ilovekiruna> just that people can take away sth from us and remember us ;-)
20:56 #navit: <@KaZeR> yep totally
20:57 #navit: < ilovekiruna> and we still have enough time to plan
20:57 #navit: <@KaZeR> maybe you guys want to chip in at opencollective? :) we can use that money to order goodies for the conference
20:57 #navit: <@KaZeR> that's actually a really good idea
20:57 #navit: < ilovekiruna> good that u remind me, wanted to do that earlier already
20:57 #navit: <@KaZeR> https://opencollective.com/navit <- :)
20:58 #navit: < ilovekiruna> KaZeR: are you the only funder so far??
21:03 #navit: < ilovekiruna> honestly, I would have also spent on some on the goodies by my own
21:03 #navit: < ilovekiruna> but probably better to make it visible via opencollective
21:06 #navit: < ilovekiruna> seems like we got another backer :-p
21:11 #navit: <@KaZeR> ilovekiruna: yeah i am :) but we haven't really advertized it yet
21:11 #navit: <@KaZeR> yay!
21:12 #navit: <@KaZeR> yeah i think that it worth trying to fund that collectively, even if it costs us a small fee. hopefully this will entice other folks to contribute
21:14 #navit: < ilovekiruna> i think one thing is especially very important
21:14 #navit: < ilovekiruna> transparency about what is paid
21:14 #navit: < ilovekiruna> was once also donating to sabayon linux 
21:14 #navit: < ilovekiruna> but saw then that apparently what was written in the budget for planned expenses was just carried on in the next years
21:15 #navit: < ilovekiruna> and no real justification from the project leader
21:15 #navit: <@KaZeR> yeah that sucks :(
21:15 #navit: <@KaZeR> that's why i was interested in opencollective
21:16 #navit: < ilovekiruna> i think it was for two years or three years, that there is a need to upgrade the build-servers
21:16 #navit: < ilovekiruna> come on, one should then at least mention, why it is repeating
21:17 #navit: <@KaZeR> yeah it's a bit shady
21:17 #navit: <@KaZeR> ilovekiruna: how about applying for a dev session too at fosdem? i'd be happy to participate remotely
21:20 #navit: <@KaZeR> https://twitter.com/NavitProject/status/929458845306384384 
21:21 #navit: < ilovekiruna> great
21:21 #navit: < ilovekiruna> i personally dont have a twitter account
21:22 #navit: < ilovekiruna> can a dev session be done remotely?
21:22 #navit: <@KaZeR> feel free to relay the information otherwise :)
21:22 #navit: <@KaZeR> well i think that if you man the dev room i can easily provide help and support via irc
21:22 #navit: < ilovekiruna> i think we can put what you put on our other platforms to
21:22 #navit: <@KaZeR> i doubt that you can do it fully remote
21:22 #navit: < ilovekiruna> fb, linkedin
21:22 #navit: <@KaZeR> yep
21:23 #navit: < ilovekiruna> etc
21:23 #navit: < ilovekiruna> if you tell me what to do, sure i can do that
21:23 #navit: < ilovekiruna> but i need ur input what you have in mind
21:23 #navit: <@KaZeR> for the dev session? or for the tweet?
21:23 #navit: < ilovekiruna> dev session
21:23 #navit: < ilovekiruna> i would suggest, once we have anything accepted, we have a skype conversation
21:24 #navit: < ilovekiruna> or a voice conversation to talk things through
21:25 #navit: < ilovekiruna> others are ofc also invited to voice their ideas
21:28 #navit: < ilovekiruna> could be also useful for practising the talk beforehand then
21:28 #navit: <@KaZeR> sounds good yeah
21:28 #navit: < ilovekiruna> any platform preference by u?
21:29 #navit: <@KaZeR> i found something not long ago that makes it easy for people to make their first contributions. looking for it. we could prepare some easy issues to fix with that
21:29 #navit: <@KaZeR> well linux is usually the easier i think
21:29 #navit: <@KaZeR> or did you mean video conferencing platform?
21:29 #navit: < ilovekiruna> i meant video conferencing platform
21:30 #navit: < ilovekiruna> ofc I would still like that we also present a summary of our discussion here in the channel
21:30 #navit: < ilovekiruna> to keep the others in the loop
21:35 #navit: <@KaZeR> yep. skype would work for me
21:40 #navit: < ilovekiruna> despite i actually consider skype on linux a catastrophe 
21:40 #navit: < ilovekiruna> dont know how it works for u
21:42 #navit: <@KaZeR> i use it on the phone or the xbox yeah, not on linux
21:42 #navit: <@KaZeR> ha, found it back : http://www.firsttimersonly.com/ 
21:42 #navit: <@KaZeR> we could create a few issues that would fit these criterias
21:48 #navit: < ilovekiruna> actually I think about making it easy for people to first contribute you are already pretty good
21:48 #navit: < ilovekiruna> i think
21:51 #navit: < ilovekiruna> i consider it especially important also to value small contributions in the start
21:51 #navit: < ilovekiruna> if people feel appreciated they tend to continue to contribute
21:54 #navit: <@KaZeR> yeah exactly. but currently we can only reach people who come here on IRC
21:54 #navit: <@KaZeR> this website might help us find new contributors
21:54 #navit: < ilovekiruna> that also did the trick for me myself ;-)
21:54 #navit: <@KaZeR> i have a couple of easy fixes that would be a good fit, like some compiler warning fixes
21:54 #navit: <@KaZeR> exactly :D
21:56 #navit: < ilovekiruna> for the dev room?
21:57 #navit: <@KaZeR> my idea was to put that on github, and use them during the dev room too
21:59 #navit: < ilovekiruna> which devroom did you consider for us?
22:02 #navit: < ilovekiruna> can this audo framework be considered platform indepedent?
22:23 #navit: < ilovekiruna> KaZeR: Is there a particular reason for spotify?
22:59 #navit: <@KaZeR> "Embedded, mobile and automotive" could be a good one
23:00 #navit: <@KaZeR> the current implementation of the audio framework isn't platform independent. Well, the plugin part is, but the example implementation isn't
23:01 #navit: <@KaZeR> this implementation revolves around players and outputs. Currently we only have one output, which is alsa. But if we add more outputs, we can support more platforms
23:01 #navit: <@KaZeR> the reason for spotify is that it's what i use in my car :
23:01 #navit: <@KaZeR> :)
23:04 #navit: < ilovekiruna> do you know the deadline for embedded, mobile and automotive?
23:09 #navit: <@KaZeR> 2017-12-11
23:10 #navit: <@KaZeR> https://lists.fosdem.org/pipermail/fosdem/2017-October/002647.html
23:10 #navit: < ilovekiruna> cool
23:11 #navit: < ilovekiruna> i was wondering what about other platforms other than spotify
23:14 #navit: <@KaZeR> so the idea is that a player plugin implements a set of feature. for example, a list of playlists, a list of tracks attached to a playlist, and some capabilities (play, next, etc)
23:14 #navit: <@KaZeR> the UI is backend-agnostic. you just see your playlists and songs
23:14 #navit: <@KaZeR> we have the spotify backend, but we also have a mpd backend
23:25 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
23:32 #navit: < ilovekiruna> qt is not just about gui, in general, 
23:32 #navit: < ilovekiruna> KaZeR: I guess you know, right?
23:41 #navit: <@KaZeR> yeah totally
23:42 #navit: <@KaZeR> we just need to think about what components we want to use. using qtnetwork functions would be great for map downloading for example
23:42 #navit: <@KaZeR> but we've always tried to keep navit agnostic of this kind of things, to avoid being locked in with one specific tech
--- Log closed Sun Nov 12 00:00:22 2017