15:01:02 <rdieter> #startmeeting kde-sig
15:01:02 <zodbot> Meeting started Tue Oct  3 15:01:02 2017 UTC.  The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:02 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:02 <zodbot> The meeting name has been set to 'kde-sig'
15:01:05 <rdieter> #meetingname kde-sig
15:01:05 <zodbot> The meeting name has been set to 'kde-sig'
15:01:08 <rdieter> #topic roll call
15:01:14 <lupinix> .hello lupinix
15:01:15 <zodbot> lupinix: lupinix 'Christian Dersch' <lupinix@mailbox.org>
15:01:15 <rdieter> hi all, friendly kde-sig meeting, who's present today?
15:01:20 <pino|work> o/
15:01:21 <tosky> o/
15:02:16 <rdieter> #info rdieter lupinix pino|work tosky present
15:02:21 <rdieter> #chair lupinix pino|work tosky
15:02:21 <zodbot> Current chairs: lupinix pino|work rdieter tosky
15:04:20 <rdieter> #topic agenda
15:04:24 <rdieter> ok, what to discuss today?
15:04:25 <mbriza> hello
15:04:34 <rdieter> #info mbriza present
15:04:35 <rdieter> hi
15:04:37 <rdieter> #chair mbriza
15:04:37 <zodbot> Current chairs: lupinix mbriza pino|work rdieter tosky
15:05:02 <tosky> genera status?
15:05:03 <rdieter> I've got recent stuff: kde-apps-17.08.1 status, kf5-5.38.0 status
15:05:40 <tosky> I was even more swamped in upstream work and I barely followed the deadines for F27
15:06:19 <rdieter> ok, can throw f27 in too (I didn't have much time either, should have more moving forward)
15:07:08 <rdieter> anything else ?
15:07:25 <lupinix> maybe qt 5.9 status?
15:07:42 <lupinix> read in #fedora-kde that you're working on something
15:07:43 <rdieter> there's nothing new there, is there?
15:07:59 <rdieter> lupinix: oh, *plans* to start working, not much to show for it yet :)
15:08:04 <lupinix> ok
15:08:15 <rdieter> I'll share plans in open discussion at end though, sure
15:09:00 <rdieter> ok, let's get started
15:09:07 <rdieter> #topic kde-apps-17.08.1 status
15:09:50 <rdieter> over the past week, I'd been working to import kde-apps-17.08.1 into rawhide, and then past few days doing f27 builds, now submitted to updates-testing
15:10:17 <rdieter> there's a few stragglers and ftbfs, I need to file a couple of bugs to track those
15:11:27 <rdieter> f26 builds should be doable, though there are a good handful of kde4 -> kf5 ports included... these are mostly non-critical leaf packages
15:11:37 <rdieter> (games mostly)
15:12:19 <rdieter> that's all I've got, any comments or questions?
15:12:42 <lupinix> nothing here
15:13:18 <rdieter> k, moving on to kf5
15:13:23 <rdieter> #topic kf5-5.38 status
15:13:42 <rdieter> rawhide only so far, planning on doing f27/f26 builds after meeting
15:13:59 <rdieter> some users anxious for this one, includes fix for https://bugs.kde.org/show_bug.cgi?id=381130
15:14:20 <rdieter> (notifications in multiscreen setups)
15:14:55 <rdieter> I started work on python bindings, so far only did one module: kf5-kconfig as a proof of concept
15:15:07 <rdieter> .bug 1490997
15:15:07 <zodbot> rdieter: Bug 1490997 – RFE: Install python bindings - https://bugzilla.redhat.com/1490997
15:15:09 <rdieter> blocking (kinda) on ^^
15:15:19 <tosky> python bindings are still complicated, if I remember the last discussions
15:15:35 <lupinix> so the stuff is already in source packages and we have to add it to our packages?
15:15:41 <rdieter> yeah, I won't do much more of them until we can streamline the process
15:15:55 <rdieter> lupinix: yes, in short
15:16:30 <pino|work> would it be possible to backport https://bugs.kde.org/show_bug.cgi?id=311456 to kdepim-runtime f26?
15:16:30 <rdieter> my current proof-of-concept hack bundles the clang python bindings in extra-cmake-modules
15:17:35 <rdieter> pino|work: yes, kde-apps-17.08.1 pim stuff will be a priority for me to do
15:18:16 <pino|work> ack
15:19:12 <rdieter> while on the topic, anyone have much experience with cmake+ninja vs cmake+make ?
15:19:31 <rdieter> turns out the python bindings (for whatever reason) fails with make but works with ninja
15:19:39 * pino|work not
15:19:45 <mbriza> nope
15:19:48 <lupinix> nope
15:20:49 <rdieter> ok, *so* the idea was if we wanted to move forward more with python bindings, probably would consider moving more kf5-related builds to using ninja... and long term, moving most/all of it
15:21:12 <rdieter> (but only if we're confident in it)
15:21:13 <lupinix> what is the advantage?
15:21:34 <rdieter> current advantage is that python bindings actually build properly
15:22:09 <rdieter> and apparently a small speed improvement in builds (~2-5%)
15:23:51 <rdieter> another todo for me: file bugs upstream about python bindings ftbfs when not using ninja :-/
15:24:40 <rdieter> alright moving on ...
15:24:46 <rdieter> #topic f27 status
15:24:58 <rdieter> f27-beta should be out soon (today?)
15:25:10 <lupinix> just got the announcement mail some minutes ago
15:25:38 <rdieter> I might actually install it, heh, just got used to my f26 install here :)
15:26:21 <rdieter> one thing brought up onlist recently is slimming the spin some
15:26:42 <lupinix> i remember
15:26:57 <rdieter> please respond there if you have opinions: my short version was that we could consider dropping kde telepathy from default install
15:27:14 <lupinix> but that user request was not some slimmung but essentially remove anything?
15:27:17 <rdieter> and one of the 2 non-default browsers: konqueror or qupzilla
15:27:26 <tosky> I would agree for Telepathy
15:27:30 <lupinix> yes, telepathy is a good candidate
15:27:40 <lupinix> konqueror too, and maybe k3b
15:27:44 <rdieter> lupinix: the extreme proposal was a bit too far, to make a bare-bones plasma-only spoin
15:27:50 <lupinix> yes
15:28:00 <tosky> iirc we have 3 games in the live image, would it make sense to remove one or two to simplify the life of the QA?
15:28:32 <rdieter> maybe, games definitely are not critical functionality
15:28:45 <lupinix> ack
15:29:22 <rdieter> so we've got 2 weeks until final freeze to implement any removals
15:30:07 <lupinix> 2 weeks? :o
15:30:09 <rdieter> until the 17th
15:30:17 <rdieter> Oct 17 is f27 final freeze
15:30:20 * lupinix just realized again the short f27 schedule
15:30:37 <tosky> oki
15:30:40 <rdieter> or maybe we could  just focus on f28 changes at this point too, avoids last minute rush
15:30:56 <mbriza> yeah, btw, there are some sddm bugs (some of them introduced by me)
15:31:01 <mbriza> going to look at them today and tomorrow
15:31:03 <tosky> well, removing telepathy at least shouldn't impact too much the functionality
15:31:09 <rdieter> mbriza: yay!  thanks
15:31:11 <lupinix> tosky: +1
15:31:40 <tosky> on the other side, iirc telepathy does not impact on the menus
15:31:40 <lupinix> same for konqueror (which is quite unusable as a browser in current state)
15:31:55 <rdieter> tosky: true, those are mostly only applets
15:32:02 <tosky> so not much win there
15:32:32 <rdieter> I figured it would be a baby step to satisfy those wanting a slim/clean'er spin
15:32:40 <tosky> I need to recheck the full list of the menus (I took screenshots for F26, need to redo it, but I guess they should be the same)
15:32:54 <tosky> how is the gain by removing KDE Telepathy?
15:33:19 <rdieter> tosky: we can say we responded to requests for a smaller spin, but that's about all
15:33:35 <tosky> ack
15:34:29 <rdieter> anyone able/willing to champion/own the 'slimming the spin' issue?  I can, but would mean time taken away from other stuff I wanted to work on (kde-apps/kf5 backports for f26)
15:34:59 <tosky> I can review the possible changes but I need guidance or technical support in implementing them
15:35:34 <rdieter> tosky: great, thanks.  actual changes will likely involve pagure pull requests to comps and/or spins-kickstarts
15:35:43 <tosky> ook
15:35:59 <tosky> how easy is to test them offline? (but we can discuss it later)
15:36:07 <lupinix> https://pagure.io/fedora-kickstarts/blob/master/f/fedora-kde-common.ks removing the line "@kde-telepathy" should do it?
15:36:27 <tosky> most likely
15:36:29 <rdieter> if it's just removals, nothing really worth testing, it's just removing a line or 2, like lupinix's example
15:37:10 <tosky> do we need all the additional fonts now that noto is available?
15:37:23 <tosky> this is a question for Sho_ probablt
15:37:24 <rdieter> good question
15:37:48 <rdieter> that sounds more of a long-term thing to consider changes for f28
15:38:18 <rdieter> (still worth doing)
15:39:06 <rdieter> moving on...
15:39:14 <rdieter> #topic open discussion
15:39:57 <rdieter> another thing I was hoping to help work on was testing qt-5.9 for f26 and/or epel7/rhel7, probably in copr first
15:40:21 <lupinix> why epel7? isn't it part of rhel now?
15:40:38 <rdieter> <nod>, epel7 here is not relevant
15:40:52 <rdieter> guess I meant centos7
15:41:35 <rdieter> if we can get it work well and smooth, raises chances of rhel adopting it later
15:42:16 <tosky> qt 5.9 for f26 would help
15:42:29 <tosky> many packages requires it; it's true that f27 is close, but still
15:42:35 <rdieter> <nod>, my priority would be f26 first
15:44:02 <rdieter> anything else before we close the meeting?
15:44:30 <lupinix> yes
15:44:39 <lupinix> kstars package
15:45:04 <lupinix> we have a new optional dependency now available in fedora (astrometry)
15:45:21 <lupinix> which pulls in an additional star catalogue (~200mb)
15:45:30 <rdieter> ouchie, that's big
15:45:37 <lupinix> i'm wondering whether recommends or suggests is better
15:45:47 <lupinix> in kstars
15:46:21 <rdieter> my gut says making it soft/optional, yeah, depends on how important the new functionality is, how many users will want/need it?
15:46:43 <lupinix> it is useful for those who make astrophotography with kstars
15:46:52 <lupinix> not for people who use it as planetarium
15:46:59 <tosky> if it starts without, for sure soft
15:47:19 * pino|work votes for suggest
15:47:35 <rdieter> offhand, if you think a majority of kstars users would find it useful: Recommends, otherwise Suggests
15:48:12 <pino|work> the astrometry spin can always add it among the default installation
15:48:14 <lupinix> for fedora astronomy lab astrometry will be shipped anyway
15:48:15 <rdieter> downside of Suggests means most people won't know about it at all either
15:48:50 <lupinix> rdieter: we documented it @kstars/indi homepages
15:49:03 <lupinix> so suggests should be fine for them
15:49:14 <rdieter> lulz, as if users read docs :-P
15:49:43 <rdieter> use your best judgement, I trust either decision you make
15:49:58 <rdieter> (as long as the shed is blue)
15:50:19 <lupinix> ok, i think i'll add a suggests
15:54:31 <rdieter> alright, thanks everyone
15:54:43 <rdieter> anything else before closing the meeting?
15:54:51 <lupinix> nothing else here
15:54:56 <rdieter> k, thanks
15:54:57 <rdieter> #endmeeting