15:00:22 #startmeeting SailfishOS, open source, collaboration: 10-March 2015 15:00:22 Meeting started Tue Mar 10 15:00:22 2015 UTC. The chair is iekku. Information about MeetBot at http://wiki.merproject.org/wiki/Meetings. 15:00:22 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:30 welcome :) 15:00:36 # topic Intro (5 min) 15:00:37 #info intoduce yourself, use #info in the beginning 15:00:43 \o 15:00:45 #info Kimmo Lindholm, TOHs et.al. 15:00:47 #info Aleksi Suomalainen, Nemo Mobile community 15:00:58 #info Martin Brook , community member, HADK eater 15:01:05 iekku: space between # and topic 15:01:14 #info Nokius, community 15:01:14 graah 15:01:15 #info Lucien Xu, community 15:01:17 #info Ville Määttä, random dev, Ruriat 15:01:20 #info Richard Rondu, app developer (RPNCalc, Parrot Zik 2.0 Manager) 15:01:24 #topic Intro (5 min) 15:01:42 noo 15:01:55 #info Osmo Salomaa, app developer 15:02:01 not worky? 15:02:03 #topic Intro (5 min) 15:02:07 no, not worky 15:02:10 hold on 15:02:23 #info Martin Kolman, community member & modRana navigation system developer 15:02:41 #topic Intro (5 min) 15:02:43 now 15:02:46 #info Kimmo Lindholm, TOHs et.al. 15:02:51 #info intoduce yourself, use #info in the beginning 15:02:54 #info Martin Brook , community member, HADK eater 15:02:57 #info Richard Rondu, app developer (RPNCalc, Parrot Zik 2.0 Manager) 15:02:58 please, again 15:03:07 #info Simonas Leleiva, Jolla sailor, #sailfishos-porters, community pootle 15:03:08 #info Lucien Xu, community, dev 15:03:15 #info Carol Chen, community chef @ Jolla, tired but happy sailor from mwc 15:03:15 community pootle 15:03:18 #info Nokius , community 15:03:29 #info Ville Määttä, random dev, Ruriat 15:03:37 #info Simo Piiroinen, Jolla sailor, mostly nemo mw 15:03:47 #info Iekku Pylkk�, Developer community sailor, hatles chair today 15:04:17 #info Thomas Perl, sailor 15:04:22 #info Osmo Salomaa, app developer 15:04:54 #info Timo Munnukka, developer 15:05:08 locusf, vmaatta: could you please repeat your info? 15:05:13 #info Ville Määttä, random dev, Ruriat 15:05:22 nh1402_:info yourself 15:05:26 #info Aleksi Suomalainen, Nemo Mobile community 15:05:50 iekku: maybe 3rd time was the charm :) 15:05:58 :) 15:05:59 #info community member, currently attempting to get android compatibility working via cyanogenmod 15:07:05 moving on 15:07:13 #topic SailfishOS and SailfishOS Secure - Nokius (10-20 min) 15:07:22 #info Nokius can't join, "Please tell more about the plans will be the consumer SFOS Version be an other branche or will it have the same Core." 15:08:06 Last Monday Jolla announced the partnership with SSH Communication Security and SailfishOS Secure. After that announcement there ware a discussion in social-media about it and the question if it's a new branch or does the consumer Version will get the security features as well. So can we get today some more information about this. Thanks 15:08:26 #link https://cdn.jolla.com/wp-content/uploads/bsk-pdf-manager/49_PRESS_RELEASE_MWC_SAILFISHSECURE_FINAL.PDF 15:08:48 * Nokius|jolla_ back to work thanks for the answer 15:09:11 Nokius|jolla_, thank you 15:11:32 I remember Marc Dillon stating that the Sailfish Secure is coming to consumers as well in the JollaUsers question session in youtube 15:11:38 we made the announcement for Sailfish Secure at MWC, however the project has just started and things are still being defined 15:11:54 there is plan to make it available for consumers 15:12:25 #info we made the announcement for Sailfish Secure at MWC, however the project has just started and things are still being defined 15:12:36 will it be open source ? 15:12:37 #info there is plan to make it available for consumers 15:13:22 for other customers (governments, enterprises etc.) there will be discussions on case-by-case basis to determine their specific needs and work with them on that 15:14:02 so Sailfish secure is more for gouvernments and companies 15:14:11 not really for average user 15:14:17 #info will it be open source, and if so, what type of licence? i.e. permissive or not etc. 15:14:54 I believe features that will be required for the enterprises will make their way to consumers (ie VPN stuff) 15:15:30 SfietKontantinW: some security features will be made available to everyone, others require customized solutions 15:16:07 also is it actually software or more of a certification/audit thing ? 15:16:09 vmaatta: those are still being discussed and planned 15:16:16 #info "others require customized solutions" i.e. proprietary? 15:16:55 cybette: :) yeah I'm sure they are… voicing the concerns / interest 15:16:56 vmaatta: please do not #info your questions 15:17:26 thank you cybette. 15:17:29 cybette: I'll be conservative 15:17:43 M4rtinK_jolla_: I would say more software, as the solution is based on a security-hardened version of Sailfish OS and SSH's communication encryption and key management platform 15:18:01 please use #info to information, not to questions. 15:18:05 cybette: note though: " People should liberally use this for important things they say, so that they can be logged in the minutes." 15:19:23 what about gpg support? (if I may ask here) 15:19:38 vmaatta, point taken. this conversation however doesn't belong to this topic, but to general 15:20:01 iekku: very much true so I didn't and won't comment about it further 15:20:11 inte: I don't have info on that at the moment 15:20:21 thx 15:20:33 inte: gpg 2.0.4 is on the device, but do you mean support in the e-mail client? 15:20:42 exactely 15:20:56 #action iekku will collect unaswered questions 15:20:57 inte: refer to together.jolla.com if there's a thread for this already, if not, create one. 15:21:00 im using mutt with the built in jolla-gpg which works but.... 15:21:14 i put mutt on openrepos already :-) 15:21:23 yeah integration of gpg at system level would be quite beneficial and fit the Secure OS theme 15:21:40 but I support this deal is only about SSH corp products 15:21:43 #info integration of gpg at system level would be quite beneficial and fit the Secure OS theme 15:22:05 again, gpg integration into system/apps best discussed/brainstormed at a together.jolla.com topic 15:22:09 also maybe OTR in IM a user data encryption ? 15:22:15 s/I support/I suppose/ 15:22:27 https://together.jolla.com/question/887/gpg-for-email-and-other-stuff/ 15:22:35 #info gpg integration into system/apps best discussed/brainstormed at a together.jolla.com topic 15:22:54 #link https://together.jolla.com/question/887/gpg-for-email-and-other-stuff/ 15:23:42 anything else on this topic, or should we move on? 15:24:20 basically we do not have too much to share on this topic at this point, the project is just starting and we'll share more info with you as we progress 15:24:58 #info more info will be shared as project progress 15:24:59 good development and idea.. and something to return to when things develop 15:25:11 vmaatta: certainly, thanks :) 15:25:26 #topic Clarification about GPS & QtPositioning usage in Jolla store applications - M4rtinK (20 min) 15:25:35 M4rtinK_jolla_, could you please? 15:25:45 sure 15:27:29 I see it as a simple question - why cant application developers use QtPositioning for Harbour apps and are more or less forced to use a low lewel DBUS api instead? 15:28:02 The APIs are functionally equivalent so it feels very weird. 15:28:46 technically, starting with qt 5.2, we can now allow qtpositioning. just waiting on legal team to approve some details. 15:29:00 also the geoclue DBUS api is pretty hard to use for Python or pure QML apps in a Harbour compatible way 15:29:07 M4rtinK_jolla_: how easy would it be to wrap QtPositioning API just around geoclue DBus API ? 15:29:45 it would be doable, sure 15:29:46 thp: do you know if the legal issue is about the QtPositioning API or geoclue API too ? 15:29:54 agree that using geoclue D-Bus API is not ideal. also agree that QtPositioning can do the same thing as GeoClue (and the same thing as android apps, for that matter) 15:29:57 as it might be because of the HERE positioning API 15:30:31 #info technically, starting with qt 5.2, we can now allow qtpositioning. just waiting on legal team to approve some details. 15:31:14 SfietKontantinW: harbour faq at the moment recommends geoclue as stopgap solution. 15:31:20 so how come Geoclue is fine and QtPositioning is not ? 15:32:22 M4rtinK_jolla_: "historic reasons". qtpositioning wasn't ABI- (API?-) stable in qt 5.1 and before. with D-Bus APIs, API stability is a bit different (your calls would fail, but your apps don't crash.. usually) 15:32:54 or what if I submitted an Android app that uses QtPositioning to Harbour, woukd it be accepted ? 15:33:07 thp: what if community provides a geoclue wrapper that provides QtPoisitionning API ? 15:33:16 would it be accepted and packaged etc ? as a workaround ? 15:33:32 thp: sure, but that should be no longer the case with Qt 5.2 15:33:43 SfietKontantinW: idea is to get the legal checks done and then allow QtPositioning as-is. 15:34:09 thp: :) 15:34:17 but maybe the legal stuff would take a long time 15:34:23 i'd say we hopefully can get this done within a week. allowing qtpositioning then should just be a matter of updating rpmvalidator. 15:34:23 and 'undisclosed legal stuff' is getting rather tiring after all the waiting... 15:34:55 thp: a week from now ? ;-) 15:35:04 M4rtinK_jolla_: +1 15:35:13 but now we have a deadline :) 15:35:20 i'll try to push this forward internally. won't happen today, though. and no promises, but i'll see what i can do. 15:35:27 a week after they start which can be months away :P 15:35:48 but you guys have to submit apps to harbour then using qtpositioning :p 15:35:54 anyway, i think we can wrap up this topic and continue? 15:36:02 +1 15:36:12 thp: thanks - it is nice to finally see feedback like this! :-) 15:36:20 yeah 15:36:28 info it ? 15:36:33 good news 15:36:38 thanks thp, we do have apps waiting 15:36:47 #info thp tries to push it internally 15:36:56 #info you guys have to submit apps to harbour then using qtpositioning :p 15:36:58 ;) 15:37:00 #action thp to push forward qtpositioning internally. eta 1 week, no promises. 15:37:13 thp, thanks 15:37:19 moving on 15:37:20 thp: can you keep us posted ? like via twitter or on irc ? 15:37:20 modRana has been reaady for half a year at least :) 15:37:21 this last info "thp tries to push it internally" sounds weird :P 15:37:31 M4rtinK_jolla_: /me using modrana for half a year :) 15:37:39 NSA-Rep, ;) 15:37:57 SfietKontantinW: yup, feel free to poll status from me via irc daily ;) 15:38:04 #topic General discussions - everyone (10 min) 15:38:35 two questions: 1) status of offline HERE maps (stefano said that it would start this year) 15:39:04 #action iekku to find out status of offline HERE maps (stefano said that it would start this year) 15:39:05 NSA-Rep: really ? :) 15:39:26 FYI I'm close to offline routin on Sailfish Os 15:39:33 *routing 15:39:43 2) Ways to accelerate DIT. Ie. a guy solved the voisemail problem but jolla hasn't said much (or i didn't notice it) how to make the process of taking in things faster 15:39:44 NSA-Rep, so nothing to share, but i will try to get info for next meeting 15:39:44 M4rtinK_jolla_: cool, but do you have offline map rendering ? 15:39:50 this will help a lot 15:40:05 NSA-Rep: +1 for the topic of DIT 15:40:19 2) sound more like own topic 15:40:21 + there are plenty of community patching going around 15:40:32 SfietKonstantinW: just offline routing for now 15:40:33 DIT also inscludes translations and kb layouts and stuff which are needed yesterdays and don't get much traction. 15:41:07 NSA-Rep, we are working on getting translations part open for community. 15:41:25 oops, i forgot that i don't have hat 15:41:28 NSA-Rep: source of stefano's comment? 15:41:32 i know the translation tool is comming but thats just half the problem. Kbrds are missing 15:41:47 but I basically forked Monav (check for monav-light on GitHub) so it might be possible to reuse the ofkine map rendering code too 15:42:00 NSA-Rep: problem about this is the same as with privileged API: security issues 15:42:02 any upates on the topic of in-app payment / paid apps etc topics? 15:42:19 M4rtinK_jolla_: did you ever thought about using osmand ? they have Qt code ! 15:42:21 https://together.jolla.com/question/339/downloadable-map-data-and-offline-turn-by-turn-navigation-in-maps/?answer=54921#post-id-54921 next january 15:42:26 s/upates/updates/ 15:42:43 and the comment was made on sep 14 15:42:51 vmaatta, unfortunately no 15:43:23 ok 15:43:34 cybette: except if he meant jan 2016 :P 15:43:44 NSA-Rep: re: 2.) -- which voicemail problem and how was it solved? is there a patch / fix somewhere that we should see to get merged? 15:44:16 thp: basically the jolla do not display any voicemail notification 15:44:21 even if the middleware seems to handle it 15:44:29 thp: wait i have to find the tjc comments 15:44:36 thp: basically it is a ui issue 15:44:47 https://together.jolla.com/question/8779/no-notification-when-new-voicemail/?answer=76513#post-id-76513 15:45:04 patch is included 15:45:39 SfietKontantinW: you are faster :D 15:45:40 NSA-Rep: ok thanks. as iekku noted, we'll look into it 15:45:49 iekku: comment re: payment, it might be obvious but I hope the Qt Purchasing API is being taken into consideration and usable where possible 15:45:55 NSA-Rep: firefox's awesomebar is awesome 15:46:02 damn - reminder was off by an hour :( 15:46:38 lbt: welcome to DST :) 15:46:54 NSA-Rep, SfietKontantinW: i'll try to link this patch up internally to the right people and forward it. maybe it's done in a different way, but proof of concept code always helps. 15:46:59 #info vmaatta hopes the Qt Purchasing API is being taken into consideration and usable where possible 15:47:04 :) 15:47:07 1 minute left 15:47:16 thp: yep, you will need to ask design etc. 15:47:29 for those in/near Florence: http://www.qtday.it/ 15:47:39 this fri/sat 15:47:52 #info http://www.qtday.it/ 15:47:58 ETA on the translation tool? 15:48:22 NSA-Rep, as soon as possible 15:48:36 #info get 30% discount on qtday: https://ti.to/develer/qtday2015?discount_code=GNR30 15:48:50 iekku: push them internally :P 15:49:04 NSA-Rep, we are doing it already :) 15:49:29 and time out for this topic 15:49:33 #topic Wrap up and next meeting (5 min) 15:49:34 use force if nessesary. 15:49:34 NSA-Rep: constantly 15:49:52 thats the way 15:50:10 * iekku proposes 2 weeks from now: March 24, same time 15:50:24 I'll chair, it's my turn :) 15:50:32 should have recovered from MWC by then 15:50:45 :) 15:52:33 i think the proposed time is ok 15:52:36 no +1 ? no -1 ? 15:52:39 +1 15:52:41 :D 15:52:42 +1 15:52:52 +1 15:53:01 lbt: do you need a separate alarm? :) 15:53:05 yes please 15:53:09 * lbt runs 15:53:10 :D 15:53:15 #info next meeting 24-March 2015, 15:00 UTC 15:53:31 thank you all and everyone 15:53:38 thanks iekku 15:53:45 #endmeeting