15:09:52 #startmeeting kde-sig 15:09:52 Meeting started Tue May 17 15:09:52 2016 UTC. The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:09:52 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:09:52 The meeting name has been set to 'kde-sig' 15:09:59 #topic roll call 15:10:00 .hello lupinix 15:10:03 lupinix: lupinix 'Christian Dersch' 15:10:10 * jgrulich is present 15:10:14 hi all, friendly kde-sig meeting, who's present today? 15:10:20 * RaphGro listens 15:10:23 present 15:12:18 #info rdieter lupinix jgrulich RaphGro than present 15:12:29 #chair lupinix jgrulich than RaphGro 15:12:29 Current chairs: RaphGro jgrulich lupinix rdieter than 15:12:31 #topic agenda 15:12:39 ok, what to discuss today? 15:12:53 * rdieter can give updates on kde-apps, kf5, plasma 15:13:24 nothing special here 15:15:38 alright, let's get started 15:15:45 #topic kde-apps, kf5, plasma updates 15:15:56 I've been working on those mostly over the past week (or 2?) 15:16:05 kde-apps-16.04.1 is all in f24 now 15:16:13 plasma-5.6.4 updates submitted for f24/f23 15:16:40 and I'm working my way through importing kf5-5.22.0 into rawhide (started yesterday) 15:16:55 * lupinix already received plasma 5.6.4 today 15:17:22 working fine right now, will test 1-2 more days before adding comment @bodhi 15:17:38 notable change in kfk5-5.22, is that kwayland is an official framework now 15:18:06 so soon folks will see kf5-kwayland-5.6.4 => kf5-kwayland-5.22.0 update coming soonish 15:18:32 but there should be no real changes, the code is essentially the same (or should be) 15:19:17 that's all, any questions, comments? 15:20:43 ups, I forgot the meeting 15:20:50 #info tosky present 15:20:51 hi :) 15:21:25 repost for tosky: kde-apps-16.04.1 is all in f24 now, plasma-5.6.4 updates submitted for f24/f23, and I'm working my way through importing kf5-5.22.0 into rawhide (started yesterday) 15:21:40 that's my own status report 15:21:42 thanks 15:22:08 We are now approximately at the point of the release cycle at which the default browser in Fedora 23 KDE was changed. So it is now time to change the default browser for Fedora 24 KDE to QupZilla. QupZilla 2.0.0 is stable now and has been tested successfully for several weeks. 15:22:38 I will not accept the "it's too late in the release cycle" argument because it WASN'T too late to switch to Firefox last time. 15:23:01 seriously? 15:23:17 we already decided this, that we would wait for f24 (at least) 15:23:32 Déjà vu 15:23:52 I am mainly pointing out the blatantly obvious double standard. 15:24:04 whatever 15:24:07 This is ridiculous. 15:24:10 closing this topic I guess 15:24:13 #topic open discussion 15:24:21 anything else for today? 15:24:37 Why was it not too late to switch to Firefox, but is it now too late to switch to QupZilla? 15:24:46 (feel free to discuss qupzilla even, though I probably won't participate much) 15:24:54 The argument to defer to F24 was that QupZilla 2.0.0 wasn't out at the time. It is now (and has been for several weeks). 15:25:10 @qupzilla: i'd propose it for f25 to give it some more time 15:25:19 true, qupzilla is finally testable now, that is much appreciated 15:25:30 It had been testable for months. 15:25:41 2.0.0 das some small but sometimes annoying bugs like the font settings bug 15:25:47 It's not like 1.9.99 didn't work. 15:25:59 (yes, already fixed in upstream git) 15:26:21 If that's the blocker, I can apply the fix, or even take a git snapshot altogether. 15:26:29 do you have any compelling reason that we change our minds, since the last time we discussed this? 15:26:51 it's just an example, not a blocker. in genereal i'd like to give it some more time before making it default 15:27:01 f25 shopuld be perfectly fine 15:27:04 *should 15:27:38 That you are shipping a KDE spin where the probably most used application is a mixed XUL and GTK+ application, is that not compelling enough? 15:27:44 no 15:27:56 I should have put "KDE spin" within quotes. It's not a KDE spin. 15:28:27 Kevin_Kofler: nothing has changed in that regard, since the last discussion 15:28:37 it's the same now, as it was last time 15:28:57 What has changed is that we have reached the point in the cycle at which the decision to switch TO Firefox was made. 15:29:00 That's what has changed. 15:29:49 But Firefox got a free pass out of any testing requirements and best practices, QupZilla does not get such preferential treatment. That's unfair. 15:30:10 Firefox was already available for many years, it's not the same situation 15:30:14 yes, and i also disliked this decision. but i don't want to couple these two decisions directly 15:31:03 .moar popcorn lupinix 15:31:05 here lupinix, have some more popcorn 15:31:07 tosky: +1, though I'd hoped that would've been obvious :( 15:31:14 :D 15:31:38 Nobody had tested it shipped on the KDE spin, nobody had tested the changes that were rushed in late to make it the default browser (even on upgrades), etc. 15:32:08 still on upgrades most people tested with firefox 15:32:21 and it is less than comparing also with the changes of feature from the browser itself 15:32:30 Kevin_Kofler: I'd encourage you to start a new ml thread if you insist, but it's not a decision to be taken lightly or quickly here and now 15:32:35 And also it was KNOWN to have showstopper issues that will likely NEVER get fixed (such as no support for KDE file dialogs). That was ignored entirely. 15:32:42 personal impression: qupzilla js engine (f23/webkit) isn't that faster compared to firefox, tested with f*ceb**k. 15:33:25 RaphGro: you should compare the qtwebengine version 15:33:32 true 15:33:43 The QtWebKit version is not the same thing at all. 15:33:55 You can get a QtWebEngine QupZilla for F23 from the QtWebEngine Copr. 15:34:02 RaphGro: , webengine is noticably better and faster (than webkit), there's no disputing that. 15:34:07 * RaphGro tries 15:34:39 And really, the point of switching to QupZilla is not that it's faster (though it probably is!), but that it is a Qt app. 15:35:19 howdy folks, finally have a stable connection at OSCON 15:35:41 It doesn't have the amount of integration Konqueror had (kioslaves etc.), but it's the best thing available out there and much nicer than Firefox. 15:36:12 for *me*, the primary importance of a browser is it's functionality/realiability. what toolkit/engine is used is of secondary important 15:36:15 importance 15:37:39 And the Chromium engine isn't reliable? 15:37:59 I voted for firefox because it's browser which most people would use/install anyway, qupzilla might be better integrated into KDE, but lacks functionality and people are not used to it 15:38:28 * pino|work still late :/ 15:38:51 Kevin_Kofler: qtwebengine/qupzilla has far less real-world exposure and testing comparatively 15:38:52 jgrulich, what func do you miss in qupzilla? 15:39:13 RaphGro: for me, extensions/addons 15:39:22 +1 15:39:23 RaphGro: plugins I use 15:39:31 #info pino|work present, hi 15:39:33 jgrulich: Sigh… This is going to be the same disaster as with NM-gnome back then: people getting used to the temporary stopgap and putting unrealistic expectations on the native app that we've all been waiting for. 15:39:51 s/we/you/ 15:40:09 * lupinix does not miss anything @qupzilla 15:40:13 It's taken us 3 releases (!) to finally switch to KNM/plasma-nm. 15:40:24 patience grasshopper 15:40:55 confirmed. qtwebengine feels faster 15:41:15 F23 KDE should have shipped with Konqueror, it would have been one single release, and switching to QupZilla 2 now (with Konqueror as the fallback) would have been a no-brainer. Sigh… 15:41:27 (or with no fallback if you hate Konqueror so much ;-) ) 15:42:11 nobody is hating konqueror, unlike somebody else who is actively hating firefox 15:42:27 At this time we should be done with the browser issue and already looking into replacing Anaconda with Calamares. 15:42:44 * danofsatx hates Firefox, but for reasons other than functionality. 15:42:54 Kevin_Kofler: beside that, would really be nice if you could *stop* this "us against them" thing you keep bringing forward again and again 15:43:02 It's more accurate to say I greatly dislike Mozilla, but that's not the argument here. 15:43:16 danofsatx: The freedom- and privacy-related issues? Those are also part of why I don't like Firefox. 15:43:29 The fact that it looks&feels like from another planet is another one though. 15:43:31 yes, those are two of the reasons 15:43:33 jgrulich, firefox slows down mostly cause of laggy plugins+addons. 15:43:41 But I've explained that often enough already. :-) 15:46:37 pino|work: Is wanting a consistent desktop experience for Fedora KDE users and a KDE spin that actually showcases KDE technologies "us against them"? 15:46:51 Kevin_Kofler: the way you keep bringing the situation is 15:47:06 pino|work: +1 15:47:36 it's fine to advocate for integrated solutions, but then leave out the negative campaigning 15:53:01 so, looks like we've hit a lul, anything else to discuss today? 15:53:11 nothing else here 15:55:27 nope. I haven't even finished the backlog yet. 15:56:12 Oh, one more thing: Is there nobody wanting to comaintain Calamares? 15:56:46 Am I the only one who cares about having a modern, Qt-based installer with a real upstream project behind it? 15:58:19 no, but I can't devote any time to the argument at this point 15:58:20 Kevin_Kofler: in general yes, but I'll have a look at it before 15:58:54 we can discuss in #fedora-kde later 16:00:04 Mainly now it'd need an update to 2.x, but I didn't get around to dealing with the impact on kpmcore and KPM. 16:02:27 k, let's wrap up the meeting, we're out of time 16:02:31 thanks everyone 16:02:37 #endmeeting