09:00:00 #startmeeting Sailfish OS, open source, collaboration – 30th November 2017 09:00:00 Meeting started Thu Nov 30 09:00:00 2017 UTC. The chair is sledges. Information about MeetBot at http://wiki.merproject.org/wiki/Meetings. 09:00:00 Useful Commands: #action #agreed #help #info #idea #link #topic. 09:00:16 #info Meeting information and agenda can be found here: https://lists.sailfishos.org/pipermail/devel/2017-November/008125.html 09:00:30 I am the meeting’s chairperson today and will be doing my best to keep time and order. Please behave, respect the timings and be kind 09:00:36 #topic Brief introduction (5 min). Please prefix your name/handle with # info 09:01:00 #info tortoisedoc developer 09:01:40 #info Kimmo Lindholm, connoisseur 09:01:47 #info Leif-Jöran Olsson, community 09:02:13 #info Bhushan Shah, KDE Plasma Mobile maintainer 09:02:16 #info eekkelund 09:02:25 #info Joona Petrell, sailor @ Jolla 09:02:31 #info objectifnul, community 09:02:52 #info Mister_Magister, community and mad porter 09:02:58 #info Raine M�kel�inen, sailor @ Jolla 09:03:21 so sledges today is chairman 09:03:29 #info Damien Caliste, community 09:03:31 #info Simonas Leleiva, sailor @ Jolla 09:04:23 #info Andrzej Lochowski, community 09:04:31 #info Miklos Marton, community 09:05:48 #info Rodolphe Sequeira, community 09:06:29 skipping first topic until tortoisedoc is around (might be only in two weeks:) 09:06:33 hei 09:06:36 #info Carmen Fdez., community 09:06:36 im actually here :) 09:06:42 so I can throw the argument in the wiold 09:06:46 *wild 09:06:48 k 09:06:53 (seems my meeting got postponed) 09:07:09 so 09:07:22 in order to clarify about the applications stats 09:07:22 #topic Apps install/usage stats per device in Harbour (NOT Jolla store) (Asked by tortoisedoc - 20 min) 09:07:37 the original idea refers to the developer's applications stats 09:07:41 NOT to public harbour 09:08:00 and the idea is to have per-device install stats on the (developer) harbour 09:08:09 tortoisedoc: let me paste your desc first 09:08:24 #info Nokius, community 09:08:27 #info As a developer, I'd benefit from an improved view of my userbase, splitted by device type and Application, visible from the developer Harbour summary page. For example, this helps in identifying where to focus testing efforts to, and eventual issues with application on specific devices. 09:08:36 tortoisedoc faster than rabbit ? 09:09:58 tortoisedoc: this is the same topic from last time's general discussion 09:11:18 sorry I'm late 09:11:36 nobody commenting? 09:12:19 pketo or xfade I think would be the right people to answer this, not sure 09:13:34 Well, I completely agree with that. Though, I don't really need the device type (still have all available form factors at home), but more a distribution over countries and some statistics over time (downloads in the last week/month/year). Anyway, more statistics would be nice. 09:15:11 last meeting the message from Jolla was that there are no short-term plans to implement that; would we have an update on mid-to-long term plans? 09:15:29 Countries are of interest for translation efforts and for my plans to start selling SFOS software. Tax laws actually make it quite hard to sell software outside of EU for a single person - of course only if you want to comply to the laws... ;) 09:15:31 ljo_: please fix your client 09:15:35 ljo_: ^ 09:15:41 ljo: ^ 09:16:43 sledges: sorry, the trainride is not good for connectivity 09:16:56 ah :) 09:17:29 10 more mins on the topic; pketo ? 09:17:46 At the moment there is no update on long-term plans on this, but we will put all the Harbour improvements on the priority list when we have time and resources to consentrate on that 09:18:06 #info At the moment there is no update on long-term plans on this, but we will put all the Harbour improvements on the priority list when we have time and resources to consentrate on that 09:18:31 tortoisedoc: have you received your answer? (i can't ask if you are happy with it :} ) 09:18:46 If Jolla has no resources to build it, we need to do it on our own. I actually included a registration/statistics feature in the most recent version of Piepmatz. About one week live now, works smoothly and gives me a nice impression about the distribution of my user base. 09:19:23 number of things that jolla don't have resources for is too damn high :D 09:20:02 or maybe number of people in the community is too damn high (which is awesome!) :D 09:20:40 As a plus side, we have currently some internal requirements for improving the store statistics, so this will be taken into account when working on those 09:21:04 #info in the meantime Ygriega has implemented own solution, community can contact? 09:21:14 #info As a plus side, we have currently some internal requirements for improving the store statistics, so this will be taken into account when working on those 09:21:14 still waiting for harbour to be ready for my app 09:22:04 Some info about my solution is on http://wagnis.ygriega.de/ - Devs/community can contact me at any time if you are interested 09:22:53 #info Ygriega: Some info about my solution [that's been rolled out on the Piepmatz app] is on http://wagnis.ygriega.de/ - Devs/community can contact me at any time if you are interested 09:23:02 maybe it time to opensource everything. 09:23:10 #link http://wagnis.ygriega.de/ 09:23:22 corvinux: no resources for this :D 09:24:03 corvinux: not in the hands of people who would like this to happen, I'm afraid… 09:24:53 ok, moving on before time, probably tortoisedoc gotten in their meeting in the end :) 09:25:05 #topic Sailfish Browser content DPI calculating is broken in 2.1.3.7 (Asked by Mister_Magister - 20 min) 09:25:28 #info Since 2.1.3.7 and changes for better support for FullHD screens, webpages DPI is calculated clearly wrong. On Motorola Moto G2 everything is too small and on Motorola Moto X Play everything is too big. Moto G2 has 5" HD display and X Play has 5.5" FullHD display. https://bugs.merproject.org/show_bug.cgi?id=1855 09:25:28 Mer bug 1855 in .Other "Sailfish Browser content DPI calculating is broken in 2.1.3.7" [Major,New] 09:25:34 #link https://bugs.merproject.org/show_bug.cgi?id=1855 09:25:41 rainemak: ^^ 09:25:54 Yeah its broken since 2.1.3 before that everything was okay 09:26:05 confirmed on 3 devices 09:26:21 ok, there are basically 2-3 things to check from your ports 09:26:38 Mister_Magister: strange, it looks fine on OnePlus One (1080 x 1920) 09:26:45 rainemak: i'm ready and happy to help 09:27:11 1) dconf dump /desktop/sailfish/silica/ 09:27:15 (pixel_ratio 2.0) 09:27:16 sledges: on g2 is totally too small (as you can see in link) and on n7 2013 and x play its a bit too big 09:27:37 2) in browser about:config and search layout.css.devPixelsPerPx 09:28:18 3) this not related per se but does all of those devices get correct dpi 09:28:44 rainemak: 2) is 1 09:29:19 rainemak: btw layout.css.dpi is -1 09:29:28 Mister_Magister: make that 4, I think I've seen that on Xc 09:29:33 (sorry I'm late) 09:29:48 ^ e.i. is physical screen size reported correctly up to Qt level (can be checked from the first QScreen of QGuiApplication) 09:29:50 layout.css.dpi is -1 also one oneplus one 09:29:51 stephg: 4 is too big but yeah its changing 09:30:12 stephg, no... that will be reset on the fly 09:30:29 stephg, no... that will be reset after browser restart as it should not be tampered 09:30:53 rainemak: 1) http://paste.opensuse.org/58299896 09:31:03 Mister_Magister, for fullhd I'd think that both of them could go with 1.75 silica pixel ratio 09:31:13 rainemak: g2 is HD 5" 09:31:26 those area wrong 09:31:32 s/area/are/ 09:31:37 rainemak: silica pixel ratio is all ok 09:32:08 1.0 is not correct for either of the device 09:32:24 for silica it is 09:32:59 1.75 seems a lot better but too big 09:33:02 Mister_Magister, I cannot know what kind other quirks you have done but it should not be 1.0 09:33:11 why? 09:33:45 pixel ratio formula: https://github.com/mer-hybris/droid-hal-configs/blob/master/droid-config-%40DEVICE%40.spec.template#L16 09:33:51 hi! any chanche to update qtwebkit on 2.1.4? right now on together app it is very slow when charging photos or web version of threats :( 09:33:52 rainemak: 1.5 seems okay 09:33:52 labels need to be readable, touch items finger-tappable 09:34:03 it is meant for keeping everything pixel perfect and correctly sizes 09:34:08 jpetrell: and they are 09:34:14 gabriel_: please wait until general discussion 09:34:44 Mister_Magister, have tampered qwindow's pixelratio instead? 09:34:47 have you 09:35:05 rainemak: what do you mean? 09:35:26 Mister_Magister, http://doc.qt.io/qt-5/qwindow.html#devicePixelRatio 09:35:37 10 more mins 09:35:51 don't recall by heart the conf value for that 09:36:04 nevertheless that should be zero as well 09:36:17 rainemak: i'm a bit lost 09:36:56 Mister_Magister, based on the info that I have so far seen those devices are not properly scaled to full hd 09:37:24 Mister_Magister, I'd recommend that we'd check those after the meeting 09:37:30 rainemak: nexus 7 2013 is fullhd though 09:37:36 rainemak: okay 09:37:44 Mister_Magister: did you use the formula? ^^ 09:37:52 sledges: ofcourse not 09:37:56 well then 09:38:34 i'll talk with rainemak after meeting so we can move on i think 09:38:45 sledges: ^ 09:38:47 sledges, and even that formula can produce suboptimal values 09:39:07 sledges, but that formula is a good starting point 09:39:10 rainemak: it is, but it's a starting point 09:39:24 :) 09:39:28 (: 09:39:29 but making everything bigger is no sense 09:41:18 if you buy bigger screen you want more place not everything bigger 09:41:18 first get 4-rows of icons in app grid and 2x2 / 3x3 app covers grid 09:41:18 sledges: covers grid is fixed in 2.1.3 09:41:18 sledges: no thanks 09:41:18 it's workaround its not fix 09:41:18 everything was good until 2.1.3 09:41:18 i'm still talking as a starting point: if you follow the formula, the browser should be ok (so in this way we know nothing else is wrong) 09:41:22 labels and touch items should be roughly of same physical size to remain readable and finger-tappable, with physically larger screen you do get more content 09:42:00 sledges: but if i set "proper" pixel ratio there i can rescale silica later? 09:42:16 jpetrell: yeap thats why i didnt use formula 09:42:56 Mister_Magister: we don't have official sfos devices with big screens + resolutions, that's why there be dragons if you try to deviate away from the formula 09:43:07 sledges: its HD 5" 09:43:14 Mister_Magister: that is what the formula does, increases size if pixels grow, reduces if display dimensions grow 09:43:24 Mister_Magister: HD not full HD? 09:43:24 2 mins 09:43:26 sledges: there would not everything was okay untill 2.1.3 09:43:35 jpetrell: HD 09:43:35 Mister_Magister: because we are adapting for xperia x 09:44:00 sledges: so what i'm saying that your way is workaround not fix 09:44:25 jpetrell: this formula makes everything bigger 09:44:25 Mister_Magister: ok so close to Jolla C's 1.25 pixel ratio 09:44:36 it just rescales 4.5 jolla 1 display to 5" 09:44:46 sounds like we are using different formula 09:44:57 or interpreting it differently 09:45:06 jpetrell: if so correct formula would give me 1.0 09:45:11 2.1.3 works on all official devices, "we don't have resources to maintain all community devices too" :) 09:45:26 sledges: thats just lazy 09:45:31 the UX scaling issue was popping up in community many many times in the past 09:45:36 yyeah sledges you have me for testing 09:45:51 sledges: but now everything is okay except browser 09:45:56 browser broke in 2.1.3 09:45:57 Mister_Magister: i want more than anyone to have community devices to scale, but it's not up to me ;) 09:46:01 Mister_Magister, will check that calculation results after the meeting 09:46:02 and it's a tough job! 09:46:41 Mister_Magister, regarding browser that is 09:46:49 thanks rainemak & jpetrell, we know that making other form factors scale would benefit Jolla too when an official device comes along :) 09:46:57 moving on 09:46:59 yeah we will just talk later and i'll explain my point :) 09:47:11 #topic MEGA.nz integration into Sailfish OS (Asked by Mister_Magister - 10 min) 09:47:20 I did tune app grid and active cover layouts quite a bit in 2.1.3 to better suit higher-resolution displays. the margins were off and not pretty 09:47:30 #info Mega.nz is another cloud storage service. They have github with sourcecode for every of their tools. (url: https://github.com/meganz) There is one commandline tool so that can be used for adding mega.nz integration into sfos. Can it be added to "we dont have resources for this for now" list? Can it be done? Eventually i'll do it myself ¯_(ツ)_/¯ 09:47:40 #link https://github.com/meganz 09:47:59 irc broke my meme ¯\_(ツ)_/¯ 09:48:07 if you can DIY then DIY :) 09:48:21 r0kk3rz: but i dunno how to integrate it into sfos 09:48:23 Mister_Magister: no it didn't ;) pure copypaste ;) 09:48:24 So it can be added to OS but resources are limited 09:48:35 we have no plans to work on MEGA.nz cloud integration, but community is free to develop an app in Store that connects to MEGA.nz 09:48:39 is the SFOS cloud integration plugin API public/documented? 09:49:01 the synchronisation parts are, yes. the account parts are not, no. 09:49:07 jpetrell: i want to make it like dropbox or somethhing 09:49:14 to be available as account 09:49:20 Mister_Magister: with like accounts and sharing dialog? pretty sure we've done community things with those parts 09:49:22 but dunno if there is documentation for it 09:49:35 r0kk3rz: but no documentation 09:49:40 any plans on opening the accounts API? 09:49:53 Mister_Magister: since when do you read documentation? 09:50:02 r0kk3rz: since always? 09:50:26 libpurple have no legit documentation tell me more about that 09:50:40 we want to enable 3rd party accounts, unfortunately there is quite much technical debt and security issues we need to sort out before we can provide 3rd party API 09:50:47 martonmiklos: my intention is to replace the current accounts middleware with one that I wrote. I don't really want to expose the current one, for a variety of reasons, and have to keep BC/SC etc. But let's see how it pans out, changing our entire stack to the new accounts framework might be quite a bit of effort, that needs to be resourced internally. 09:51:16 i can make app for it but thats not what i wanted :/ 09:51:34 and im out of resources too 09:52:00 chriadam_: make the guideline / plan public, we may help in implementation. 09:52:05 #info we want to enable 3rd party accounts, unfortunately there is quite much technical debt and security issues we need to sort out before we can provide 3rd party API 09:52:06 chariadam_ : that sounds great 09:52:08 stick it on TJC, maybe someone will pick it up 09:52:56 i gather it's more tight-knit to sfos internals 09:53:04 chriadam_: what does the BC/SC means? sorry this is the first time when I see this 09:53:21 Binary/Source Compatibility 09:53:26 ah 09:53:32 okay 09:53:33 dcaliste: indeed. first step is to opensource the new accounts framework. then I can document the steps to port parts of our stack. but a big chunk of work is currently closed source settings/accounts stuff (and no plan to opensource that stuff in the near future, from what I know) 09:53:46 I think we all would love to see better cloud integration (syncing all content types, cloud folders, automatic camera roll sync, more supported services, etc.), but really we need 1.) more time or 2.) paying customer project to speed things up 09:53:51 but need to discuss with jpetrell and internal stakeholders more ;-) 09:54:46 3 more mins 09:55:06 Mister_Magister: fwiw, you can check the buteo-sync-plugins-social for .. 90% of the dropbox/onedrive code 09:55:24 the other 10% is in closed source repo, unfortunately, related to listing files for backup/restore cases 09:55:30 chriadam_: can i have link to that? 09:55:36 oh, plust he accounts plugins but they're just QML and can be found on teh device 09:56:08 https://git.merproject.org/mer-core/buteo-sync-plugins-social 09:56:10 #info fwiw, you can check the buteo-sync-plugins-social for .. 90% of the dropbox/onedrive code; the other 10% is in closed source repo, unfortunately, related to listing files for backup/restore cases 09:56:12 Mister_Magister: https://git.merproject.org/mer-core/buteo-sync-plugins-social 09:56:25 #info plus the accounts plugins but they're just QML and can be found on teh device 09:56:31 #link https://git.merproject.org/mer-core/buteo-sync-plugins-social 09:56:42 chriadam_: and if i make it ready is it possible to make it into sfos? 09:57:04 dcaliste: thanks 09:57:07 moving on? 09:57:28 Mister_Magister: try to embark more pirates on your ship:) 09:57:31 Mister_Magister: contributions to open sourced repos can follow normal contribution process. the problem is the accounts side stuff - it's closed and we cannot accept contributions to that currently, as we have no defined process 09:57:35 sledges: just wondering if it will be integrated into sfos if i make it 09:57:38 There will be also the issue of using the single sign on framework, don't you think? 09:57:46 sledges: i have one :P 09:57:55 Mister_Magister: you could raise a community support group around this one; cc jpetrell 09:58:06 (like chriadam_ does around c*dav) 09:58:16 chriadam_: so i have to make into jolla and then make it internally 09:58:19 seems like good plan! 09:58:27 grin 09:58:42 I just mean, the sync plugin is a good start, then we can discuss further 09:58:47 chriadam_: sledges: just wait for me :P 09:58:57 chriadam_: okay! 09:59:00 #topic Covers are sometimes displayed wrongly 09:59:01 thanks 09:59:15 #info asked by Mister_Magister, 10mins 09:59:17 Mister_Magister: I'm trying to do the same with WebDAV synchronisation. 09:59:20 #info Sometimes covers are rendered too big for a window (link to screenshot: https://imgur.com/v4F6E99). This bug started from 2.1.3 09:59:48 #link https://imgur.com/v4F6E99 09:59:54 'sup everyone 09:59:58 * tbr checks in 10:00:00 When i enter app and leave it it fixes, its weird bug 10:00:03 dcaliste: Mister_Magister: could you join forces outside meeting pls? :) 10:00:21 sledges: doubt we have 2 different plugins :P 10:00:29 I haven't met this bug yet on 2.1.3 10:00:35 Mister_Magister: it's about accounts integration - what we've mainly discussed ^^ 10:00:36 sledges: sorry being out of topic time. Will discuss it later. 10:00:36 sledges: i have friend that will amke it with me 10:01:21 dcaliste: all good, more helping hands the better to overcome accounts integration (which is the biggest show stopper atm) 10:01:28 this bug has been reported by me before it happens after phone calls I have to check tjc how the reproducing works 10:01:51 This bug can be reproduce after a phone call. 10:01:51 #info this bug has been reported by Nokius before it happens after phone calls, have to check tjc how the reproducing works 10:01:55 Nokius: not even after calls for me it just happen sometimes 10:02:02 Oups, sorry Nokius ! 10:02:11 tjc linky pls :) 10:03:22 like said I did tune active cover layouts, though it should not directly affect such scaling 10:03:33 there has been similar layout issues in active covers before, maybe my active cover layout changes made those issues more common on some community devices 10:03:52 yeah about covers even with my "broken" dpi they are proper 2 columns now since 2.1.3 10:04:09 so thats a good thing 10:04:36 the cover width is calculated from display width and margins around and between covers 10:04:45 Mister_Magister: and 3x3 when >4 apps open? 10:05:00 sledges: yeap 10:05:15 Nokius: dcaliste: have you seen this on community ports only? 10:05:20 sledges: they are all good no matter the pixel ratio 10:05:33 great job jpetrell! :) 10:05:40 sledges: my brother with jolla phone didnt had it 10:05:44 so i can adjust the formula description :) 10:05:46 For me it happens almost all the time on JollaC after phone calls. 10:06:27 I don't have this bug on Jolla 1 :) 10:06:31 dcaliste: after phone call the phone cover contents are incorrectly scaled? 10:06:44 jpetrell, exactly. 10:06:52 sledges: on non ports ;) 10:06:55 dcaliste: cool I'll try to reproduce 10:07:09 I can fix if I can find a way to repro 10:07:25 Nokius: you mean official device(s)? 10:07:41 sledges: yes, it happened on the Xx too 10:08:00 I cannot reproduce it on demand though, but it happens very often for me. I guess first something with screen blanking when put the phone near ears, but it's not reproducible just playing with the captor when the phone rest on the table. 10:08:01 * sledges can't find TJC 10:08:04 on that 10:08:06 I experienced it with Jolla 1 and Xperia X 10:08:16 (randomly) 10:08:34 dcaliste: helps to reproduce if you swipe the top (jolla phone) app to background during phonecall maybe? 10:09:10 jpetrell: as an aside, is there any way to tune the whitespace between app covers on the homescreen? 10:09:49 probably it wasn't an eye-watering bug, because it goes away after enter/exit any app 10:10:03 r0kk3rz: the margin there is Theme.paddingLarge, you can tune paddings but then all apps are affected 10:10:12 nice netsplit 10:10:27 jpetrell: hmm ok, i'll have to check the latest version with your new tweaks anyway 10:10:29 the issue should be fixed, though severity depends on how many see it 10:10:56 time to move on, Nokius could you find its tjc please, and if not, could you file one with Mister_Magister? 10:11:08 sure why not 10:11:14 thanks! 10:11:29 also with hints how to reproduce quicker than later :) 10:11:33 #topic Email app improvements and long standing bugs in email and connection switching (Asked by ApBBB - 15 min) 10:11:47 #info https://together.jolla.com/question/97109/email-imap-idle-doesnt-work-with-both-connections-active/ & https://together.jolla.com/question/91937/bug-imap-idlepush-of-some-email-service-providers-some-users-does-not-work-with-generic-imap-account/?sort=votes&page=1 are two bugs that affect email. Also we have the case that emails arrive late etc etc. 10:11:56 #info One of the things that a smartphone must do well is communication and email is one of the main ways people communicate outside proprietary apps. And the situation is no good for some at least. So what are the plans for improving this. 10:12:03 #link https://together.jolla.com/question/97109/email-imap-idle-doesnt-work-with-both-connections-active/ 10:12:09 sledges: I can't find it atm, but it should be there let me search on 10:12:12 #link https://together.jolla.com/question/91937/bug-imap-idlepush-of-some-email-service-providers-some-users-does-not-work-with-generic-imap-account/?sort=votes&page=1 10:12:15 sledges: it is happening also without sending the app to background. Typically: phone on the table, ringing. Pull down to answer, pick the phone put it to ear 45°, speak. Later hang off, let the phone app disappear and show the home screen, then covers are wrongly scaled. 10:13:04 #info sticking to previous topic, how to repro scaled covers: phone on the table, ringing. Pull down to answer, pick the phone put it to ear 45°, speak. Later hang off, let the phone app disappear and show the home screen, then covers are wrongly scaled. 10:13:08 sorry ApBBB :) 10:13:12 the stage is all yours now 10:13:23 oops, sorry again, too slow to type :( 10:13:37 As the title suggests. Not much to add to it other than its quite annoying to have emails arriving late or having to activate/deactivate flight mode to have the email app working 10:13:58 and both those stuff are loooooong standing bugs 10:14:46 sounds serious, we should have a look 10:15:01 ApBBB: how often do you need to do that? 10:15:12 we are actively working on improving email and calendar 10:15:23 For the issue with both connections active, see my TJC answer : https://together.jolla.com/question/97109/email-imap-idle-doesnt-work-with-both-connections-active/?answer=175138#post-id-175138 10:15:23 \o/ 10:15:26 every time i go out and have to reconnect to my appartment wifi 10:16:32 In a nutshell, any change in the NetworkSession (disconnecting, roaming…) will stop the idle IMAP connection. 10:16:42 meaning two-three times a day 10:16:56 I cannot see from the code where this connection is reestablished. 10:17:25 in 2.1.3 we fixed a lot of long-time connectivity issues, were connections didn't always recover when device switched between connection methods (WLAN hotspots, mobile data), both Qt and Android apps were improved 10:18:02 jpetrell: i am on 2.1.3.7 10:18:09 and still get those issues 10:18:19 ApBBB: well different issue probably 10:18:41 I'll try to investigate this reconnection issue in imapservice.cpp in the coming weeks and report in TJC if I find something. 10:18:50 jpetrell: BTW have you taken into accont the community suggestions with the email design and stuff? 10:18:59 dcaliste: thanks 10:19:06 dcaliste: if you get stuck let me know and I'll forward questions to mvogt 10:19:46 Thanks chriadam_, my main concern here is that I cannot see where the connection is reestablished after network hickups which is strange. 10:20:13 by "connection" do you mean connection to the imap server, or the lower level qtbearer connection config? 10:20:21 I woudl 10:20:38 ApBBB: yes. community suggestions and votes in together jolla are active used for ideas to suggest for the paying customers 10:20:46 The latter, see imapservice.cpp#1962 10:21:21 ops I would say that something has to be fixed with connecting to secured wifi hotspot. Still can't log in with default browser on university :( have to use another web browser 10:21:31 jpetrell: good. i hope the whole inverted UI to get into the folders is fixed 10:21:38 chriadam_: I didn't try yet to reproduce, just tried to read the code and find inconsistencies. 10:22:06 dcaliste: rainemak might be able to help with the qtbearer level stuff, he investigated / fixed some things there recently 10:22:23 gabriele: when i was in itally that was workign ok for me 10:22:28 buggy but ok 10:22:38 gabriele: please adress during general discussion in 3 mins ;) 10:23:11 ApBBB: we would also like to do comprehensive UX redesign of Email, it is not easy for new users, HTML viewer could be much better, folder ux is broken, etc. 10:23:15 chriadam_: currently I don't think it is in the qtbearer things, more in the way imapservice is reacting to its signals. 10:23:27 ah, right 10:23:36 unfortunately it is hard to get funding for non-functional UX improvements 10:24:18 sorry non-functional UX improvements = non-functional requirements like UX. non-functional as in quality improvement and not new features 10:24:19 jpetrell: open source it then and let the community do the design stuff. 10:24:31 #info dcaliste has kindly stepped forward to look into the matter, and will keep us updated, with help from Jolla 10:24:35 #link https://together.jolla.com/question/97109/email-imap-idle-doesnt-work-with-both-connections-active/?answer=175138#post-id-175138 10:24:50 jpetrell: UX is painfull in some areas 10:25:06 not only in the email app. we ahve discussed that in the past i think 10:25:17 and i made some suggestions 10:25:57 at the end of the day you will be able to offer a better more usable product to your paying customers 10:25:58 seamlessly moving on to... 10:26:00 sledges: :) yes, the issue is lying in the open source parts, so it should be possible to fix it from the community. 10:26:01 #topic General discussion - 15mins 10:26:04 this meeting is kinda long :P 10:26:07 uh 10:26:16 sledges: my topic was missed? :P 10:26:22 sledges: where is my officially supported xz1 compact 10:26:24 :D 10:26:24 ApBBB: open sourcing is decision only the investors/owners can ultimately make. if you have money buy controlling stake at Jolla and open source the asset :P :) 10:26:31 bshah: no topic of yours here: https://lists.sailfishos.org/pipermail/devel/2017-November/008125.html 10:26:47 sledges: well yes, it was missed in email as well :P 10:26:51 Any work in progress regarding partitioning scheme in SailfishX/XperiaX ? 10:26:53 bshah: maybe added to late 10:27:06 james didnt edited that 10:27:07 jpetrell: i get that. but opening an app or two will help enormusly. 10:27:14 agree 10:27:21 bshah: when adding a topic, don't add it as an answer it is often missed. 10:27:31 i was not talking about opensourcing the whole thing 10:27:41 it doesn't matter 10:27:45 but apps 10:27:50 is another storry 10:27:55 dcaliste: I don't have enough karma to do otherway 10:28:03 Well lets everybody clap their hands on my first sfos contribution! 10:28:12 * ApBBB claps 10:28:19 aka hwcomposer pullreqest for inverted screens 10:28:19 anyway here was my topic, and Mister_Magister added it to wiki today : https://together.jolla.com/question/54157/sailfishos-open-source-collaboration-meeting-planning/?answer=174543#post-id-174543 10:28:27 objectifnul: not prioritised on that at the moment 10:28:30 bshah: sorry, will vote for your answer! 10:28:30 thank you for your contribution, Mister_Magister. 10:28:39 bshah: today is probably too late :P 10:29:01 chriadam_: thanks :3 10:29:06 sledges: any news on nes xperia hw? 10:29:16 .... but but I added topic week ago.. anyway.. it's fine if is not discussed today I guess... uh 10:29:18 :p 10:29:20 :( 10:29:30 ApBBB: nintendo entertainment system? :) 10:29:36 MisterMagister how do you know I am in Italy? Anyway, connecting to wifi hotspot in university is diffucult still :( Have to use or webpirate 10:29:41 bshah: who was the author? 10:29:42 sledges: highfive thought about the same 10:29:48 jpetrell: so whats this sailfish-secrets thing all about? - https://github.com/sailfishos/sailfish-secrets 10:29:55 bshah: sorry, we've had lots of topics, let's let people eat some lunch today :) will pick up next week! 10:30:00 gabriele: i had login page at my hotel 10:30:04 sledges: okay, fine with it 10:30:36 chriadam_: author for? 10:30:38 sledges: yeah getting hungry but dont wanna miss anything :P 10:30:39 r0kk3rz: that would be telling :P 10:30:39 bshah: if you can send me an email with the sha1s of the changes which are missing from upstream, I will try to follow up. chris dot adams at jolla dot com as per usual 10:30:56 sledges: yes i guess it wouldnt be very secret! 10:31:03 chriadam_: actually, this is useful : https://github.com/bhush9/qtmultimedia-patches 10:31:12 (I guess) 10:31:32 bshah: ok, I will check tomorrow 10:31:35 r0kk3rz: it's what the README is reporting, a framework to store and perform crypto operations. 10:31:43 bshah: for next times: we need some time to prepare an answer, so the earlier it appears in tjc wiki body the better 10:31:51 What about bringing back swype gestures for active covers actions? They were so cool in older Sailfish! :) 10:31:59 r0kk3rz: similar to android's KeyChain 10:32:13