15:04:42 #startmeeting kde-sig 15:04:42 Meeting started Tue Mar 1 15:04:42 2016 UTC. The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:04:42 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:04:42 The meeting name has been set to 'kde-sig' 15:04:44 #meetingname kde-sig 15:04:44 The meeting name has been set to 'kde-sig' 15:04:47 here 15:04:49 hi 15:04:51 present 15:04:56 #topic roll call 15:05:01 hola 15:05:15 #info rdieter heliocastro tosky than dvratil present 15:05:19 #chair heliocastro tosky than dvratil 15:05:19 Current chairs: dvratil heliocastro rdieter than tosky 15:07:00 #topic agenda 15:07:01 hi all, what to discuss today? 15:07:40 qt-5.6 status (and related blocker bug(s)) 15:07:59 Plasma 5 for Centos - need a volunteer to look into it 15:08:25 QupZilla by default, now that it is all packaged and working? 15:08:30 well, baby steps, need to work on kf5 first (for epel I assume) 15:08:40 (i.e., instead of Firefox on the KDE Spin) 15:09:10 that makes 3 topics, anything else? 15:09:55 #info Kevin_Kofler present 15:10:00 I would also like to formally complain (mainly for the meeting log) about the toxic behavior of heliocastro, accusing me of toxic behavior in a meeting I wasn't even attending. 15:10:19 ok, if you insist, that makes 4 15:10:23 (so no chance to defend myself from the accusation) 15:10:27 #topic qt-5.6 status 15:10:50 So, qt-5.6.0-rc landed, but we hit a new, fairly big bug wrt plasma 15:11:06 .bug 1311635 15:11:07 rdieter: Bug 1311635 Unable to create io slave: klauncher said: Error loading /usr/lib64/qt5/plugins/kf5/kio/desktop.so - https://bugzilla.redhat.com/1311635 15:11:13 heliocastro: ^^ that's the one I mentioned 15:11:36 rdieter: The strange part is that is not in all achines 15:11:40 *machines 15:11:56 And i have one with nvidia, prop, and other with intel chipsets 15:12:00 heliocastro: oh? it's on all mine (though I have only 2) 15:12:01 all f23\ 15:12:24 heliocastro: it's fine on at least one of yours? 15:12:41 Both is running 15:12:51 And the nvidia one, even with three screens 15:12:58 interesting, both using plasma ? 15:13:11 I experienced a single crash on composite konsole when unplugged one screen 15:13:14 But all plasma 15:13:25 I just don't have any plasmoids beyonf the taskbar 15:13:44 mine's a default/vanilla plasma config, fwiw 15:14:04 desktop containment fails to load due to the desktop.so plugin not loading 15:14:26 anyway, I'll make a call onlist for more testing/feedback 15:14:39 anyone else successfully using qt-5.6.0-rc/plasma5 ? 15:14:46 rdieter: Humm, all my machines are using folder view 15:14:48 not desktop 15:14:59 like I said, mine's whatever is the default 15:15:14 heliocastro: and, I reproduce the error with dolphin, trying to use pretty much any kio slave 15:16:28 Have you tried whether a rebuild of the offending kioslave fixes it? 15:16:35 no 15:16:41 wait, yes I did 15:17:05 I rebuilt plasma-workspace (which owns desktop.so) 15:17:17 like I said, other kio's failed too, the same way 15:17:57 I think I even tried rebuilding kf5-kio 15:18:03 * jgrulich is here 15:18:08 #info jgrulich present 15:18:09 hi 15:18:32 hi 15:18:58 anyway, any debugging assistance would be appreciated 15:19:56 I'd tried settings QT_DEBUG_PLUGINS env, but it didn't give anything too useful, I may have to enable more debugging 15:21:36 anyway, any help would be appreciated, please comment in the bug 15:21:49 moving on... 15:21:54 #topic kf5/plasma5 for centos 15:22:07 anyone able/willing to work on this? 15:22:20 I want to, but no, no time 15:22:28 same here :) 15:22:28 I'm focusing in make the ci works 15:22:39 first step would probably be to kf5 (copr initially, eventually in epel-7) 15:22:47 we have a fairly new KF5 there 15:22:49 5.19 I think 15:22:57 so it's just about getting Plasma 5 built 15:23:06 there's a copr already? where? 15:23:26 http://copr.fedoraproject.org/coprs/dvratil/epel-playground 15:23:46 it should be fairly simple to get the stuff work with the new distgit feature in Copr 15:24:39 dvratil: wow, it 'just worked' without any changes ? 15:24:51 it was fairly simple, yes 15:24:55 I expected at least a few, nice 15:25:07 mostly I just needed minor fixes in spec files 15:25:23 but since we build for F22, getting it work for EPEL was rather easy 15:25:39 Plasma might be more tricky, I don't know yet 15:25:48 rdieter: https://heliocastro.fedorapeople.org/Screenshot_20160301_162148.png 15:26:00 Current packages, dolphin with fish 15:26:03 but as I said, we can use specfiles diurectly from Fedora distgit, we just need someone to do the initial setup and write the tooling probably 15:26:35 and eventually to do the mass-import of KF5 into EPEL 15:26:36 dvratil: neat, I didn't know that was possible 15:26:43 dvratil: We can read/get from distgit 15:26:50 But not write directly 15:26:56 we don't need to write 15:27:01 Yep 15:27:08 we can build from f22 branch of Fedora distgit 15:27:28 * heliocastro is basing the same idea on use distgit 15:27:36 there are even some hooks for automatic build triggers, but I haven't investigated 15:28:24 ok, looks like build triggers only work with github 15:28:46 heck, if kf5 works without changes, any objection to requesting epel-7 kf5 branches asap ? 15:29:09 it *builds*. I haven't tested if they actually work 15:29:14 heh 15:29:23 SHIPIT 15:29:33 and someone needs to review build logs if we have all the optional deps 15:29:40 15:30:15 dvratil, heliocastro: either of you willing to post onlist about progress so far, maybe asking for help too? 15:30:44 Yes, for both cases, epel + ci ? 15:31:02 regarding the EPEL, I can write something after work 15:31:07 sounds like testing in copr may be a reasonable prereq before pushing anything to epel 15:31:28 but I'm ok with doing so asap too, esp if that means more testing/feedback 15:32:06 side-issue: *may* be worth waiting until qt-5.6.0 lands in epel before pushing kf5/plasma5 there too 15:32:16 sounds reasonable 15:33:03 I mispoke , only kf5 for epel, plasma5 can't go there 15:33:16 plasma5 must be copr only 15:33:32 yep, that we discussed previously - setting up a kde-sig/plasma-5 copr for EPEL 15:33:48 ok, sounds like we have a plan, anything else? 15:33:55 nfm 15:34:12 Done 15:34:22 moving on... 15:34:32 #topic Qupzilla for f24 15:34:37 Kevin_Kofler: go ahead 15:35:28 Yeah, so… 15:35:48 QtWebEngine 5.6 RC is now in Rawhide and F24 Branched. 15:36:32 (GStreamer support is not there and I'm not sure it'll land for F24, it also depends on gstreamer1-plugins-bad-free packaging, among other things. But unencumbered codecs work with the current packaging.) 15:37:01 \o/ 15:37:11 (with the bundled remnants of FFmpeg, with all encumbered codecs removed) 15:37:48 There is also a matching QupZilla 1.9.99 snapshot that should also just work. Last I tested the stuff, it all worked, at least. :-) 15:38:07 Other people have also confirmed it working well, being fast, etc. 15:38:23 , worked fairly well in my own limited testing. good work 15:38:32 So I am now proposing again that the F24 KDE Spin should drop Firefox and include QupZilla as its default browser instead. 15:38:56 (When I last proposed it, it was shot down due to not being packaged yet. Now it is.) 15:38:57 I thought we'd already decided to wait a release? 15:39:05 See above. 15:39:11 no, it was not the reason why I voted no 15:39:32 What would waiting a release buy us? 15:39:35 the reason still stand: too early, first release not yet released, happy to re-evaluate in F25 15:39:35 though, I would agree to shipping it on the spin by default 15:39:52 fine with having it on the spin 15:39:53 You didn't wait a release to switch to Firefox during Final Freeze (!!!). 15:39:57 as a tech-preview, backup browser (possibly replacing konqueror) 15:40:03 Firefox was not a new software 15:40:20 as mentioned, ff was not new and was already well-tested, well-understood 15:40:24 "First release not yet released" is not true, QupZilla has been around for years. :-) 15:40:37 it's a rewrite with a new engine 15:40:39 webengine-based qupzilla, *is* quite new 15:40:43 It's a port, not a rewrite. 15:40:56 same complexity 15:41:54 If you insist on shipping both, the Qt browser with Plasma integration should be the default and Firefox the emergency fallback, not the other way round. 15:41:59 Any objections to including qupzilla on kde-sig spin (as a seconary/tertiary browser)? 15:42:03 hi all 15:42:25 no objections to including qupzilla on the spin 15:42:32 But shipping both means yet another HTML engine on the spin. 15:42:35 There are already too many. 15:42:40 Gecko needs to go away. 15:43:02 +1 for including QupZilla as a secondary browser (and re-evaluating in subsequent releases) 15:43:03 Kevin_Kofler: other kde/plasma apps will eventually start depending on qtwebengine, its only a matter of time 15:43:21 That's exactly why QtWebEngine is not the one that should go away. :-) 15:43:30 Kevin_Kofler: baby steps 15:43:38 The KDE Spin is a KDE Spin, not a Mozilla Spin. 15:43:52 And Firefox will soon no longer comply to the Free Software Definition. 15:43:58 Kevin_Kofler: you're repeating yourself again, we've been over that many many times 15:44:06 See the signed extension fiasco. 15:44:21 and hint: each time you do it, the weight of the argument lessens (to me) 15:45:12 ok, so followup proposal: consider removing konqueror from the spin (since qupzilla is essentially filling the role of backup browser) 15:45:38 Konqueror should be the backup for QupZilla (instead of Firefox). 15:46:11 Kevin_Kofler: if you insist, we can take a vote, and then will you promise to stop bringing it up? 15:46:12 Then if we're confident enough that QupZilla works for everyone, drop Konqueror too. 15:46:40 Your problem is that QupZilla is too new? Well, Konqueror sure isn't. ^^ 15:47:12 Konqueror lacks seriously a Frameworks version 15:47:20 sadly 15:47:40 Yes, so Konqueror should be dropped in F25. F24 should have it as a fallback for QupZilla. 15:48:19 ok, let's get this over with 15:48:20 And Firefox was a one-time mistake in F23 that should never have happened. (F23 should have shipped with Konqueror, it would just have been one more release to bridge.) 15:48:36 The arguments for Firefox are still as irrational as ever. 15:48:50 * rdieter giggles at the irony of that statement 15:49:02 (sorry) 15:50:01 Kevin_Kofler: can you make a formal proposal that we can vote on please? 15:50:22 Irony? Are you trying to imply desktop integration, look&feel consistency, freedom (e.g., no signed extension nonsense) are irrational? Do you really think that??? 15:50:42 i think it's irrational to repeat yourself , and expect a different outcome 15:51:11 now, do you want a vote or not? 15:51:18 I want to get it over with, so we can move on 15:51:24 Proposal: QupZilla 2/1.9.99 shall replace Firefox as the default browser on the Fedora 24 KDE Spin. Konqueror shall remain the fallback for now, dropping it will be considered for Fedora 25. 15:51:32 Rationale: as above. 15:51:50 two combined votes? Uhm 15:51:58 ok, -1 then 15:52:12 well, the primary issue is the first sentence 15:52:22 -1 15:52:26 +1 15:52:28 If your issue is the second sentence, then let me offer the alternative: 15:52:32 -1 15:52:42 Proposal B: QupZilla 2/1.9.99 shall replace Firefox as the default browser on the Fedora 24 KDE Spin. Konqueror shall be dropped immediately. 15:52:51 (the first one is A) 15:53:03 Kevin_Kofler: pick one 15:53:04 -1 15:53:10 A: -1, B: -1 15:53:11 A implies to me that firefox is being removed 15:53:26 That's the plan for B too. 15:53:26 A; -1 B: Abstain 15:53:27 B implies to me that firefix is kept as secondary browser 15:53:43 A: -1, B: -1 15:53:46 Kevin_Kofler: oh, so no secondary browser at all? 15:53:54 Proposal B (clarified): QupZilla 2/1.9.99 shall replace Firefox (which shall be dropped) as the default browser on the Fedora 24 KDE Spin. Konqueror shall be dropped immediately. 15:54:29 Yes, Firefox needs to go away, it's a waste of space, and a landmine for privacy and freedom. 15:54:45 And we had 22 releases without a fallback browser. 15:54:51 ok, neither proposal passes as-is, I'll assume you're +1'ing it 15:55:01 from my point anothe reason for dropping ff: quite bad integration in plasma 5 15:55:02 I'm not in the voting members anymore. 15:55:09 Kevin_Kofler: feel free to take issue onlist and ask kde-sig'ers to vote 15:55:46 I see only lupinix for it, so… 15:56:09 Thanks for reminding me again why I left the SIG! 15:56:17 ok, quickly, my proposal was just: remove konqueror from f24 spin 15:56:27 It also really shows how much my work on packaging QtWebEngine is appreciated. 15:56:32 (mostly because we now already have 2 browsers) 15:56:58 Kevin_Kofler: I'm sorry if it's a surprise, but we're following the plan we agreed on in prior meetings 15:57:04 So you want Firefox/QupZilla? 15:57:18 Whereas I proposed QupZilla/Konqueror or just QupZilla. 15:57:25 yes, implies keeping firefox default, qupzilla as backup/tech-preview 15:57:51 rdieter: I'm annoyed by the ever-changing excuses for sticking to Firefox. 15:57:54 shipping 3 browsers seems a bit much 15:58:10 It's true that tosky had already brought up the "wait one release" idea, but you jumped on that bandwagon now. 15:58:15 Kevin_Kofler: again, I'm sorry if you feel that way, *my* reasoning has always been consistent 15:58:23 You said it needs to be packaged before being considered. Now it is packaged. 15:58:37 the packaging of QtWebEngine *is* appreciated; the delay of QupZilla has nothing to do with the level of packaging 15:58:46 it's not just "it's packaged, it's ready" 15:59:32 any votes/comments on removing konqueror? (we're running short on time) 15:59:43 I'm torn, but tentative +1 16:00:00 And this is also one of the reasons I was so strongly against Firefox in F23, I knew it'd be a fight to get the Spin off that drug. And this proves my point back then. 16:00:04 +1 for removing konqueror in favor of qupzilla 16:00:13 I share the same for removing konqueror, I abstain on that 16:00:41 +1, same as jgrulich 16:01:08 than ? 16:01:51 pretty sure we don't have quorum, I'll take it onlist after 16:02:38 moving on... 16:02:45 #topic toxic behavior 16:03:06 Kevin_Kofler: your topic, go ahead 16:03:29 Basically, I already said what I had to say in the introduction: I consider it toxic behavior to accuse me of toxic behavior in absentia, when I am not there to defend myself. 16:03:40 (which is exactly what heliocastro did last week). 16:04:03 heliocastro: That's what I had to say. 16:04:07 Sorry, i really commented, and that's why i requested to we implement rules for everyone 16:04:11 As rdieter took 16:04:17 duly noted 16:04:28 Not only you, neither me, everyone 16:04:34 Is going too far. 16:04:50 I made a mistake few days ago, you direct call me for expulsion 16:04:51 last week we decided to take a harder stance on code of conduct expecatations 16:05:22 As for the actual alleged "toxic behavior" at stake, I think we've been through this on the chan enough for the whole week not to rehash it again. 16:05:45 ok, so matter is (essentially) closed ? 16:05:45 So now we have proper policies, reinforced 16:05:48 That's ok for me 16:06:27 worksforme too 16:06:29 #topic open discussion 16:06:41 anything else to mention today before we close the meeting? 16:06:52 just got an email about Plasma 5.5.5 tarballs being available for packagers, will get to building tonight 16:06:59 woot 16:07:09 dvratil++ 16:07:15 go go go 16:07:23 Plasma 5.6 beta tarballs will be available tomorrow, I'd like to get that to Copr too, but can't promise when 16:07:41 Quick question, which git tag should be more appropriate for the packages 16:08:04 upstream tag? 16:08:10 Meaning 0.. 16:08:36 So, the next qt packages will be 5.6.1-0.1.adasda 16:08:46 Or there is a better approach ? 16:08:53 heliocastro: oh, if they are snapshots, then yes, that's the way to go 16:09:02 I like the explicit "beta", "alpha", "rcX" more 16:09:13 git tag revision does not tell you much 16:09:24 dvratil: This is for nightly builds 16:09:28 not the official released 16:09:32 ah! 16:09:36 heliocastro: depends, if there are real 5.6.1-beta git tags to use, then use the tag 16:09:38 Will be same for kf5 packages 16:09:44 There is a clear policy to follow for Release tags for prereleases, which you are expected to know. One minute, let me dig up the link. 16:09:44 sorry, in that case +1 16:09:56 rdieter: The released ones will keep the beta/rc tags 16:10:08 in the absense of tags, then use snapshot scheme 16:10:09 The ci ones will be the reference 16:10:21 https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Non-Numeric_Version_in_Release 16:10:34 * rdieter has to run to appointment soon, we're over time 16:10:40 kk 16:10:47 There's a git tag recomendation already 16:10:51 So, see you guys 16:10:59 thanks everyone! 16:11:01 #endmeeting