--- Log opened Fri Jan 18 00:00:48 2019
05:10 -!- xenos1984 [~xenos1984@9efa-2ce1-dee4-e84a-8780-87e7-07d0-2001.dyn.estpak.ee] has joined #navit
05:10 -!- mode/#navit [+v xenos1984] by ChanServ
07:28 -!- naggety [~naggety@198.red-95-127-75.dynamicip.rima-tde.net] has joined #navit
07:43 -!- xenos1984 [~xenos1984@9efa-2ce1-dee4-e84a-8780-87e7-07d0-2001.dyn.estpak.ee] has quit [Quit: Leaving.]
08:34 -!- twoelk [~twoelk@pD95595DE.dip0.t-ipconnect.de] has joined #navit
11:19 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
11:19 -!- mode/#navit [+v xenos1984] by ChanServ
14:05 -!- naggety [~naggety@198.red-95-127-75.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!]
15:59 -!- mvglasow [~mvglasow@dslb-092-074-099-105.092.074.pools.vodafone-ip.de] has joined #navit
16:02 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
18:53 -!- ilovekiruna [~ilovekiru@ip1f12af77.dynamic.kabel-deutschland.de] has joined #navit
18:53 -!- mode/#navit [+v ilovekiruna] by ChanServ
20:28 #navit: <+ilovekiruna> hi @all
20:48 #navit: <+ilovekiruna> KaZeR, jkoan, mvglasow: I still have time to make changes to my presentation. Do you have any comments or additions?
20:53 #navit: <+ilovekiruna> KaZeR: could you also at some point merge my PR against the navit-layout repo?
20:55 #navit: <+ilovekiruna> or maybe I could do it myself, if you give me merge permissions for this repo
21:21 #navit: < mvglasow> ilovekiruna presentation? I guess I missed that part, but let me know where to find it
21:22 #navit: < mvglasow> in the meantime, I got news on the F-Droid end
21:23 #navit: < mvglasow> after numerous attempts, with jkoan's input and tryagain's CI script I finally managed to piece together a working build recipe for Navit
21:24 #navit: < mvglasow> it largely relies on the Linux build script, with just a few adaptations
21:24 #navit: < mvglasow> and I finally got it to build master successfully on a CI image
21:25 #navit: < mvglasow> however, the build relies on changes introduced after the last released version (namely the build script)
21:25 #navit: < mvglasow> so to get a current Navit version on F-Droid we have two options:
21:25 #navit: < mvglasow> either just wait for the next official release
21:25 #navit: < mvglasow> or do an interim release
21:29 #navit: < genesis> btw i left this project, better would be asking an official release
21:30 #navit: < genesis> since it's dead and no one is really competant to be a benevolent dictator for this project.
21:31 #navit: <+ilovekiruna> mvglasow: I present our build infrastructure on the fosdem conference in the beginning of feb in brussels
21:32 #navit: <+ilovekiruna> link: https://fosdem.org/2019/schedule/event/geo_navit/
21:34 #navit: < mvglasow> ah... just looking at it
21:35 #navit: < mvglasow> cosmetically, the Navit icon is a bit squashed
21:36 #navit: < mvglasow> then on page 4: 64 MB RAM may be enough for Navit to boot, but long routes (Lisbon-Warsaw or the like) won't work
21:36 #navit: < mvglasow> not sure how to best express that, though
21:37 #navit: < mvglasow> maybe: 64 MB are enough for basic functionality, but longer routes will require more memory
21:39 #navit: < mvglasow> page 7: platform specific tests - with a multiplatform project like Navit, this is particularly important, as testing every platform gets close to impossible for a single dev
21:40 #navit: <+ilovekiruna> mvglasow: if you want you will be also able to watch me live :-D
21:40 #navit: <+ilovekiruna> in stream
21:41 #navit: < mvglasow> all right, I'll try to save the date :-)
21:42 #navit: <+ilovekiruna> i will see to include that maybe in the weekend
21:42 #navit: <+ilovekiruna> what i for sure want to add is the note from jkoan about openstf
21:42 #navit: <+ilovekiruna> that could be a great future development
21:42 #navit: < mvglasow> page 9: how does CI help avoid long living branches? The immediate benefit of CI is that it tells you when your latest commit has broken something...
21:42 #navit: < mvglasow> but how that keeps branches limited to one topic is not immediately obvious to me
21:42 #navit: <+ilovekiruna> maybe that a combination or a combination of a CI with automation tools like apium, selenium, ...
21:44 #navit: <+ilovekiruna> i think the long living branches was more about circleci
21:45 #navit: <+ilovekiruna> but we need to ask KaZeR, i think that part came from him
21:47 #navit: < mvglasow> You have reached your destination in one slide. :-) How about accompanying that with a speech announcement :->
21:48 #navit: <+ilovekiruna> u mean by a tts?
21:48 #navit: <+ilovekiruna> I would say it also myself, I guess
21:48 #navit: < mvglasow> :-)
21:48 #navit: < mvglasow> apart from that, maybe the presentation can be spiced up with some visuals:
21:49 #navit: < mvglasow> a screenshot on the What is Navit slide
21:50 #navit: < mvglasow> maybe also include a screenshot from CircleCI, for those who have little experience in the field
21:50 #navit: < mvglasow> for me Navit was the first time I got in touch with that
21:51 #navit: <+ilovekiruna> for the visuals, could you provide me the exact screenshots you have in mind?
21:52 #navit: < mvglasow> for Navit itself, I would suggest a descriptive one from the website
21:52 #navit: < mvglasow> for my own project I have used this one: https://traffxml.gitlab.io/app-navit.html
21:53 #navit: < mvglasow> but it displays an experimental feature and a custom OSD and map layout, so it may not be representative
21:54 #navit: <+ilovekiruna> btw: how far is the traffic branch functionality?
21:54 #navit: < mvglasow> basics work, I recently added some improvements to segment matching
21:55 #navit: < mvglasow> and it will route you around congestions if there is a shorter way
21:55 #navit: < mvglasow> there are just some things around it to be worked out:
21:56 #navit: < mvglasow> for example, announce when the route changes because of the traffic situation
21:56 #navit: < mvglasow> right now Navit will just silently reroute you, and at the most you will notice that the next maneuver suddenly changes
21:57 #navit: <+ilovekiruna> hmm, i agree this is not so good
21:57 #navit: < mvglasow> also displaying traffic distortions on the map is not great, some limitations of the graphics engine really bite us here
21:57 #navit: <+ilovekiruna> is the graphics engine gui dependent?
21:58 #navit: < mvglasow> for example, there is no way to indicate the direction of the road to which the distortion applies
21:58 #navit: < mvglasow> the graphics engine is mostly platform dependent
21:59 #navit: <+ilovekiruna> so gui independent, right?
21:59 #navit: < mvglasow> we cold really use things like shield symbolizers as in Mapnik, support for dashed lines (of any width), arrow patterns
21:59 #navit: < mvglasow> it should be GUI independent
22:00 #navit: <+ilovekiruna> u know I was also thinking about changing osd a little
22:01 #navit: <+ilovekiruna> in particularly auxmap
22:01 #navit: <+ilovekiruna> but right now too busy with work :-(
22:01 #navit: < mvglasow> also, an OSD item for upcoming traffic messages (on the route or on the current road) would be nice
22:01 #navit: <+ilovekiruna> couldnt you just write that in an ordinary text osd element?
22:01 #navit: < mvglasow> that way, we could not only warn of traffic jams but also e.g. of objects on the road
22:02 #navit: < mvglasow> the challenge is to identify that something is up, and then enable/disable the OSD
22:02 #navit: < mvglasow> maybe some of the speedcam OSD ode can be borrowed for that
22:02 #navit: <+ilovekiruna> so you mean, you lack the "signal", sth is going on?
22:02 #navit: < mvglasow> yep
22:03 #navit: <+ilovekiruna> i want to also ask you one more thing
22:03 #navit: <+ilovekiruna> do you have merge access to the layout repo?
22:03 #navit: <+ilovekiruna> I wonder what we still do about my PR
22:05 #navit: < mvglasow> let me see
22:06 #navit: < mvglasow> apparently not for that repo, sorry
22:06 #navit: <+ilovekiruna> ok, no problem, maybe I am still missing sth there
22:07 #navit: <+ilovekiruna> just saw now to my surprise, if so, can see when i make the required changes
22:08 #navit: < mvglasow> but that reminds me that someday I might want to commit the layout I use
22:08 #navit: <+ilovekiruna> great, we could then add that as well
22:08 #navit: < mvglasow> originally taken from the 0606.at layout I found on the wiki, with some adaptations
22:11 #navit: < mvglasow> as for traffic, I have added that as a github project: https://github.com/navit-gps/navit/projects/8
22:12 #navit: < mvglasow> about visuals for the presentation, for CircleCI maybe you can do a little visual tour:
22:12 #navit: < mvglasow> the list of workflows
22:13 #navit: < mvglasow> one workflow expanded to show its jobs
22:13 #navit: <+ilovekiruna> i have 30 mins
22:13 #navit: <+ilovekiruna> so maybe 2 or 3 more slides could work
22:13 #navit: < mvglasow> and maybe one job
22:14 #navit: < mvglasow> possibly with one step expanded, showing console output
22:14 #navit: < mvglasow> so people who don't know CircleCI will get a feeling for it
23:06 #navit: < mvglasow> all, I just filed a merge request for F-Droid:
23:06 #navit: < mvglasow> https://gitlab.com/fdroid/fdroiddata/merge_requests/4313
23:07 #navit: <+ilovekiruna> good luck and thx for the efforts
23:07 #navit: < mvglasow> the next official Navit build will go on F-Droid (if everything works as expected)
23:07 #navit: <+ilovekiruna> in addition to google play?
23:09 #navit: < mvglasow> presumably yes, unless someone decides otherwise
23:10 #navit: <+ilovekiruna> :-D
23:10 #navit: < mvglasow> we've been on F-Droid all along, just the last build was hopelessly outdated
23:10 -!- mvglasow [~mvglasow@dslb-092-074-099-105.092.074.pools.vodafone-ip.de] has quit [Quit: Leaving]
23:35 -!- twoelk [~twoelk@pD95595DE.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds]
--- Log closed Sat Jan 19 00:00:50 2019