kde-sig
LOGS
15:15:36 <rdieter> #startmeeting kde-sig
15:15:36 <zodbot> Meeting started Tue Aug  2 15:15:36 2016 UTC.  The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:15:36 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:15:36 <zodbot> The meeting name has been set to 'kde-sig'
15:15:41 <rdieter> #topic roll call
15:15:44 <tosky> hi
15:15:48 <lupinix> hi
15:15:49 <rdieter> hi, friendly kde-sig meeting, who's present today?
15:16:02 <rdieter> #info rdieter tosky lupinix present
15:16:08 <rdieter> #chair lupinix tosky
15:16:08 <zodbot> Current chairs: lupinix rdieter tosky
15:18:01 <rdieter> may be a fast meeting
15:18:03 <rdieter> #topic agenda
15:18:11 <rdieter> anything to discuss today?
15:18:27 <lupinix> any new results of default browser discussion?
15:18:36 <pino|work> o/
15:18:37 * lupinix checks mailing list
15:19:02 <lupinix> no new comments @ml
15:19:04 <rdieter> I'd mentioned it in #fedora-kde recently only, but now that chromium is in fedora, we can consider that as well
15:19:35 * pino|work is here late, sorry
15:19:39 <tosky> maybe not too relevant, but today dfaure merged the frameworks branch of kde-baseapps into master
15:19:40 <rdieter> it at least, has some integration (not native like qupzilla of course), support for kwallet, and file dialogs
15:19:45 <lupinix> pino|work: we are late too, just stating
15:19:58 <lupinix> *starting
15:20:04 <rdieter> #info pino|work present
15:20:05 <tosky> which is targeted (at least) for Applications 16.12 at this point
15:20:07 <rdieter> #chair pino|work
15:20:07 <zodbot> Current chairs: lupinix pino|work rdieter tosky
15:20:18 <rdieter> tosky: excellent news
15:20:52 <rdieter> I can give a brief status on recent package updates
15:20:58 <pino|work> well, still konq would need a proper maintainer though
15:21:23 <rdieter> let's get started I guess
15:21:25 <pino|work> it isn't like being frameworks will make it magically on-par with features of the rest
15:21:29 <rdieter> #topic default browser discussion(s)
15:21:58 <rdieter> onlist discussions tapered out a bit, I didn't see any new revelations recently
15:22:10 <tosky> no, it won't make it have magical features
15:22:14 <rdieter> I'll stir the pot and bring up chromium (as threatened)
15:22:18 <tosky> also, it would need an updated qtwebkit
15:22:23 <tosky> so it's not automagic at all
15:22:25 <tosky> just reporting
15:22:50 <rdieter> <nod>, using modern toolkit/frameworks is a step in the right direction
15:23:05 * lupinix prefers QupZilla as default due to best integration
15:23:30 <rdieter> lupinix: better integration, what specifically?  besides kwaller, file dialogs ?
15:23:36 <rdieter> kwallet... I mean
15:23:56 <lupinix> chromium uses gtk theming and at least looked weird when using breeze-gtk some time ago
15:24:19 <rdieter> that's a separate issue, that's not integration (imo)
15:24:31 <lupinix> imho it is :D
15:24:38 <rdieter> and we're not using breeze-gtk (yet), so that's irrelevant too
15:25:06 <rdieter> so you're in the "I insist on a native Qt5 app" camp?
15:25:11 <lupinix> yes
15:25:16 <rdieter> k, fair enough
15:25:41 <rdieter> I'm (still) more pragmatic, willing to consider alternatives if that means better functionality and features
15:25:59 <rdieter> which chromium definitely has (again, imho)
15:26:11 <pino|work> (as long as they are still free, of course)
15:26:26 <rdieter> if it's in fedora, it must be free, so that's a given
15:26:47 * Markus_KMi hopes it'll just stop two browsers by default. doesn't care much about more ;)
15:27:02 <lupinix> only pro chromium i find: addons
15:27:11 <rdieter> Markus_KMi: can you rephrase that?  I'm not surw what you mean?
15:27:33 <lupinix> but i'm not using it that much, maybe there are other pros
15:27:35 <Markus_KMi> firefox AND konqueror installed by default. unless it changed already
15:27:44 <rdieter> lupinix: you have to admit upstream support is superior... I mean, how many developers are actively working on qupzilla (esp compared to chromium)?
15:28:44 <lupinix> don't know if this really comparable. @qupzilla there are less devs (3-4 really active i think), but it is "only" the gui, the core is the same in both cases
15:29:04 <lupinix> konqueror should be dropped due to the outdated webkit
15:29:12 <pino|work> Markus_KMi: not installing konqueror doesn't give any advantage, since most of its components are provided elsewhere
15:30:02 <lupinix> rdieter: the more risky part is qtwebengine, not qupzilla (imho)
15:30:20 <rdieter> <nod>, it is still relatively new
15:30:32 <pino|work> or anything webkit-related in general, i'd say
15:31:30 <lupinix> so what is the best way to find a decision @browser discussion
15:31:33 <rdieter> ok, we'll need a decision soonish, I'll try to move onlist discussion forward this week
15:31:34 <lupinix> some voting?
15:32:01 <rdieter> lupinix: yes, I don't think we'll find an easy consensus
15:32:12 <lupinix> yep
15:32:33 <pino|work> i honestly don't like the way webkit and forks are developed: single branch, no stable series, new features and (security) fixes go together only, huge blob of code
15:32:59 <rdieter> pino|work: and by "and forks" you mean webengine too ?
15:33:01 <lupinix> well Qt tries that
15:33:06 <pino|work> rdieter: yes
15:33:10 <lupinix> cherry-picking security fixes
15:33:16 <rdieter> k, just checking :)
15:33:18 <lupinix> from chromium
15:33:59 <pino|work> sure, and webkitgtk folks do that as well, for a lot of wasted work in fixing stuff
15:33:59 <Markus_KMi> webkit has a stable branch. it's maintained by apple for safari. nokia/digia just refused to use that as base for qtwebkit
15:34:13 <lupinix> QtWebEngine 5.6.1 for example is chromium 45 with backported security fixes of chromium 51
15:34:19 <pino|work> Markus_KMi: sure, and given that it's apple-only it doesn't matter
15:34:47 <Markus_KMi> no, its public ;)
15:35:13 <pino|work> and qtwebkit is no more maintained by qtcompany anyway
15:36:20 <rdieter> pino|work: +1
15:36:26 <pino|work> Markus_KMi: link?
15:37:56 <deadrat> once there were few Qt ports of firefox. ( wish someone does that. might make things a little easier. )
15:38:00 <Markus_KMi> pino|work: https://trac.webkit.org/browser/branches
15:38:47 <pino|work> deadrat: they were hacked patches for firefox, and sadly some of the changes were not refactored in a cleaner way as asked by upstream
15:40:32 <rdieter> move on ?  (I'd greatly encourage more browser discussion onlist too)
15:40:46 <pino|work> ok
15:40:51 <rdieter> #topic recent updates
15:41:20 <rdieter> So... lemme see, rawhide now has kde-apps-16.07.80 (mostly), minus -pim stack due to 3 new packages pending review
15:41:43 <rdieter> https://bugzilla.redhat.com/show_bug.cgi?id=kde-reviews  tracked here
15:41:50 <rdieter> the kf5-aknoadi-* ones
15:42:14 <rdieter> I'm importing plasma-5.7.3 into rawhide now, will do f23-f25 builds soonish
15:42:51 <rdieter> kde-apps-16.04.3 recently when to f24 (stable) updates too over the past week or so
15:42:52 <Markus_KMi> 👍
15:43:24 <rdieter> that's all I can think of, anyone else?
15:44:39 <tosky> uhm, I guess the big hit will be Application 16.08
15:46:25 <rdieter> some good stuff there, yeah, in case there's any doubt, I intend to push that to f24 updates
15:46:45 <rdieter> may do some selective f23 updates where features, bugfixes warrant it
15:48:30 <rdieter> ok, sounds like that's all, moving on
15:48:35 <rdieter> #topic open discussion
15:48:44 <rdieter> anything else to discuss today?
15:48:51 <lupinix> nothing here
15:49:00 <tosky> nothing here
15:49:57 <pino|work> nope
15:50:47 <rdieter> ok, thanks everyone!
15:50:50 <rdieter> #endmeeting