--- Log opened Sat Jun 10 00:00:39 2017 00:25 -!- pmckinley [~Peter_McK@88-110-192-224.dynamic.dsl.as9105.com] has joined #navit 00:25 #navit: < pmckinley> hey kazer :) 00:25 #navit: < pmckinley> hi roomies 00:31 #navit: < pmckinley> =-O 01:00 -!- pmckinley [~Peter_McK@88-110-192-224.dynamic.dsl.as9105.com] has left #navit [] 01:43 -!- Horwitz [~mich1@p200300800E180C00022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 01:43 -!- mode/#navit [+o Horwitz] by ChanServ 01:47 -!- noradtux [~noradtux@2a02:2028:85b:c001:c0e6:9162:be20:46f5] has quit [Ping timeout: 255 seconds] 01:51 -!- noradtux [~noradtux@port-4327.pppoe.wtnet.de] has joined #navit 04:11 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 06:42 #navit: < jkoan> If we get them over mail we could write a script that pases the body out an generate automatic tickets on our ticket system. BTW you said you want to upgrade the Navit infrastructure. Maybe a crazy Idea, but what if we publish our website navit-project.org over github pages? And even we should have more modern/up to date software. Ie wiki and ticket system and also please add mobile responsive to those both. It is a mess working on by handy 09:23 -!- jjelen [~jjelen@83.240.61.30] has joined #navit 09:50 -!- jjelen [~jjelen@83.240.61.30] has quit [Ping timeout: 246 seconds] 17:12 #navit: < kazer> hi there 17:14 #navit: < kazer> jkoan: my concern with automatically converting emails to tickets would be that we'll end up with a gazillion tickets that just clutters our ticketing system. Technically we could probably create ticket directly as part of the bug reporting 17:15 #navit: < kazer> jkoan: publishing navit-project.org using github pages : http://navit-gps.github.io/website/ :) (we would just need to point the domain there) 17:19 #navit: < kazer> also, updating our software : try http://52.26.214.83 - i am working on an automated upgrade path for mediawiki and the forums 17:19 #navit: < kazer> any help on any of these topics is welcome, so if you're interested just let me know :) 17:19 #navit: < jkoan> i know that we need to point the domain there. even we need the cname file in the repo ;) 17:21 #navit: < jkoan> the link looks nice :D even if some images are missing 17:23 #navit: < kazer> you mean the tentative new website? 17:25 #navit: < jkoan> yes 17:29 #navit: < kazer> mmm. which images? 17:32 #navit: < jkoan> all notes 17:35 #navit: < kazer> notes? 17:36 #navit: < kazer> you're talking about the wiki no? 17:40 #navit: < kazer> test forums are at http://52.26.214.83:81/ btw 17:41 #navit: < kazer> but i still need to install ldap for that 17:43 #navit: < jkoan> Yes in the wiki, the note template 17:44 #navit: < kazer> ah yeah 17:45 #navit: < kazer> do you see a difference in the response tim between our current wiki and this one? 17:53 #navit: < jkoan> Yes of course, it is now blazing fast instead of loading over taking ages :D 17:54 #navit: < kazer> ah sweet. i was wondering if it was related to the transatlantic distance :) current wiki is in germany, that server is in oregon 18:03 #navit: < jkoan> I'm located in Germany, so no it's not :D 18:04 #navit: < kazer> cool :) 18:06 #navit: < jkoan> I head I new idea for our release process related to Fdroid :X 18:10 #navit: < kazer> ah? 18:14 #navit: < jkoan> What if we create a new file named "VERSION" with the only content "0.5.2" so we have a the file for Fdroid and we could read the file also from cmake so we only need to change that one file to release a new version. Also our ci could react to the change and push the apk to Google stable and beta branch, so we don't need to have any tags 18:17 #navit: < kazer> it's a good idea per se, but tags are actually meant to replace the need for this kind of files 18:19 #navit: < jkoan> And why we don't use tags on the main branch? ^^ not those creepy R0000 tags 18:21 #navit: < kazer> the creepy Rxxxx tags are required to keep track of the build ids for google play :) i want to move them to a seperate repo though 18:22 #navit: < jkoan> Why we not use 201706102022? 18:26 #navit: < kazer> actually we could because they would be bigger than the latest release 18:26 #navit: < kazer> but we would still need to move them to another repo, currently it clutters our release page 18:28 #navit: < jkoan> Yes, I know that it is bigger and even that this is needed 18:28 #navit: < jkoan> Why we generally need tags?! 18:29 #navit: < kazer> for playstore, we need a way to tag the release that we push to the store. Unfortunately, it has to be a number, we can't use git hashes 18:29 #navit: < kazer> currently the Rxxxx tags are only used for that 18:36 #navit: < jkoan> Yes, if we use the datecode as id and another thing to let the ci know it should push the new apk to stable branch 18:38 #navit: < kazer> that's where tags are handy :) circleci can trigger a build when we issue a tag. It will have a specific env var that we can use to know that it's a release, and not a regular commit. We could use that to push updates to many places at once, automatically 18:38 #navit: < kazer> have to go afk, back in a few 18:39 #navit: < kazer> any feedback on the wiki/forum test server is useful. For the forum i still need to fix something related to ldap 18:40 #navit: < jkoan> Yes, but then (if we use real tags like v0.5.2-beta2) we don't need those annoying R0000 tags 18:45 #navit: < kazer> they do are annoying : but we can create a stub repo and push the tags for playstore (Rxxxx or using a date stamp) against that specific repo, as a trickle from the regular builds 18:45 #navit: < kazer> bbiaw 18:54 #navit: < jkoan> But the tag text is not important if we use datecode because the datecode is the id. And the trigger for the build and also the upload to Google play stable branch is the release of a new tag 20:12 #navit: < kazer> tags also allow us to link to a specific code version to investigate bugs, which a text file would not allow 22:12 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] 23:35 -!- Horwitz [~mich1@p200300800E180C00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds] 23:48 -!- Horwitz [~mich1@p200300800E0C6200022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 23:48 -!- mode/#navit [+o Horwitz] by ChanServ --- Log closed Sun Jun 11 00:00:40 2017