18:00:36 #startmeeting 18:00:36 Meeting started Wed Apr 1 18:00:36 2015 UTC. The chair is tittiatcoke. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:36 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:00:44 *cough* 18:00:49 #meetingtopic Welcome to the openSUSE KDE community IRC meeting! Please wait with other discussion until the meeting is over. This meeting is logged 18:01:55 have to leave, bbi 20 18:01:57 ok. On tonights show we have a special star Plasma5 :) 18:02:58 Agenda for tonight is: 18:02:58 yay 18:04:01 Transition plan to switch TW to Plasma5 as default. When, how, etc. Issues that were reported regarding Plasma5 from the community. Changes to the default setup: Application Menu, Desktop Theme, etc SDDM startup issue with Breeze theme. Solution, workaround, .. ? Status KDE Applications 15.04. OBS repositories that will be used for Frameworks, Plasma and Applications. Other topics. 18:04:19 Hmm. was expecting that to be better. Let me try again 18:04:31 Transition plan to switch TW to Plasma5 as default. When, how, etc. 18:04:41 Issues that were reported regarding Plasma5 from the community 18:04:51 Changes to the default setup: Application Menu, Desktop Theme, etc 18:05:01 SDDM startup issue with Breeze theme. Solution, workaround, .. ? 18:05:08 Status KDE Applications 15.04. 18:05:16 OBS repositories that will be used for Frameworks, Plasma and Applications. 18:05:26 Other topics. 18:05:33 Ok. lets move to the first point 18:05:54 #topic Transition plan to switch TW to Plasma5 as default. When, how, etc. 18:06:33 As that the target is to move with 5.3 to default, I assume the timing is still end of April ? 18:06:38 shumski: correct ? 18:06:46 tittiatcoke: yep, afaik 18:07:17 Ok. I guess that actuall all Framework and Plasma packages are already in Factory/Tumbleweed ? 18:07:23 14.04 beta, 28.04 final 18:07:23 *actually 18:07:31 Ok. 18:07:46 tittiatcoke: except muon. yesterday i packaged muon release, but it just segfaults 18:07:56 shumski: Do we want muon ? 18:08:09 and i guess we need some sort of update applet? 18:08:59 Good question :) I know that somebody started with porting Apper, but based on the history do we really want an update applet or do we want to fall back on just YaST and zypper ? 18:09:00 that was at least blocker in the past. i don't mind if we miss it, but want to say we don't have anything in P5 18:09:42 shumski: But I don't think Muon would really help us here, I don't think the packagekit backend is really working 18:10:01 true 18:10:32 Ok. Lets park the update applet for now :) 18:10:40 oki 18:10:58 #action What to do with an update applet. Go for Apper on P5, Muon or just nothing (yast/zypper) 18:12:06 I guess that we need to adjust openQA if we make the switch ? At least openQA should be evaluating Plasma5 and no longer KDE4 18:12:15 yeah 18:12:35 so half of tests need to be rewritten from scratch 18:12:56 Ok. Do we have anybody who can do that or is this a job for the QA team ? 18:13:23 i think they accept volunteers always 18:13:25 I can remember that ilmehtar/sysrich offered help before with the rewrite 18:13:43 it is more question do *we* *need* to do it, or someone else 18:13:57 :) Ok. Let validate this then :) 18:14:16 * shumski poked around some needles before, but nothing big like this 18:14:30 #action tittiatcoke to check with Richard, Bernhard, DimStar who should normally write new tests for openQA 18:15:23 Once we have the tests, I guess that we then need to change the patterns to make Plasma5 default ? 18:15:51 yep. that shouldn't be too hard 18:16:28 we only need to check will this fit 1.0GB for liveCD 18:16:51 Is that the max limit ? 18:16:52 for the KUF iso, i needed to axe LO to go below 1.0 18:17:05 tittiatcoke: i am not sure is it official limit 18:17:47 bit i think DVD is anyway more important 18:18:09 Ok. Guess we have to check that. :) And then we should define a minimum pattern :) 18:18:27 #action tittiatcoke to check with coolo and DimStar what the limit is for the liveCD 18:18:57 Ok. Once we have the patterns, we are then ended up with what to obsolete from KDE4 :) 18:19:20 At least I guess we are not planning in keeping KDE4 complete as a desktop solution in Factory ? 18:19:30 krop: shumski einar77_work ^^ 18:19:43 (and listen to people complaining) 18:19:50 well, hear, not listen :) 18:20:00 i don't think we should have both 18:20:22 in that case there wouldn't be an upgrade path 18:20:32 which is something we want i'd say 18:20:37 krop: if we would have listened in the past, then we would now be maintaining three desktops :) 18:20:37 but no, we don't want yet another unmaintained version 18:21:09 Good. So whatever is not needed from KDE4 should be obsoleted from Plasma5/Frameworks5. 18:21:39 wstephenson had a KDE 2 live CD, we could have 4 version in factory :) 18:22:15 krop: The famous one that was made when KDE 4 just was out ? The one from beineri ? 18:24:04 shumski: Do we have a list or idea what is no longer needed from KDE4 ? e.g. kdebase-runtime ? 18:24:12 if people will want kde4, they have <= 13.2 =) 18:24:25 Yup 18:24:29 tittiatcoke: kdebase4-workspace, addons and some applets 18:24:47 i mean plasma-addons 18:25:15 shumski: Oki :) And kdebase-runtime is part of KDE Applications, so I guess that one will slowly disappear 18:25:32 i think that one will be there until the end 18:25:37 yup :) 18:26:15 shumski: I guess we want to continue with the "5" prefix for certain Frameworks/Plasma stuff ? We agreed in the past already that we will not do this for KDE Applications 18:26:55 tittiatcoke: for libs makes sense (and was my biggest mistake all of KF5 doesn't have a prefix or suffix) 18:27:12 Ok.I guess too late to change it :) 18:27:17 for plasma, not 100% necessary. where we have kde4 equivalents 18:27:31 e.g. bluedevil, etc 18:28:07 Ok. But those packages we already have in Factory, so do we really want to submit now bluedevil instead of bluedevil5 ? 18:28:09 https://build.opensuse.org/package/rdiff/KDE:Unstable:Frameworks/plasma5-unstable-pkglist?linkrev=base&rev=3 can be removed e.g. 18:28:30 tittiatcoke: ah, i don't think we need to rename existing packages 18:28:41 Ok. :) 18:28:47 i was speaking more about potential new packages 18:29:34 for apps, yes, no need to append 5, unless we need some kpart from kde4 one 18:29:46 e.g. with konsole, kate & okteta 18:29:47 Ok. I guess it might be good to draft a new guideline there. How do we want to distinguish Framework Packages, Plasma packages, etc 18:30:03 shumski: indeed, but then I would suggest to rename the old KDE4 ones :) 18:30:18 tittiatcoke: that also worksforme 18:30:56 shumski: At least that would make things a little clearer :) I did the same with libkdegames and libkmahjongg (where we need both KDE4 and KF5 versions) 18:31:13 tittiatcoke: oki 18:31:22 no objection to that 18:32:54 Ok. Lets concluded on this point. Transition plan would exist out of: 1). Create the openQA test and then 2) adjust the default patterns so that Plasma5 is pulled in. Open Items are the update applet and a minimum plasma5 pattern for the liveCD (if space is limited). 18:33:30 The timing would depend on when the openQA tests are done and available. 18:34:19 yep. even beta can be submitted to act as default, i figure it'll take at least 2 weeks to adjust everything 18:34:26 (then the final is out) 18:34:47 Ok. Anything else for the transition plan ? 18:35:06 can't think of anything else now 18:35:16 ok. 18:35:53 Lets postpone the second topic (Issues that were reported regarding Plasma5 from the community) as that einar77_work isn't there yet. And I hope that he has this particular information 18:36:08 so. Third topic 18:36:13 #topic Changes to the default setup: Application Menu, Desktop Theme, etc 18:36:14 h, you mean the poll? 18:36:17 yup 18:36:24 oki. 18:36:58 ok. we have most of stuff wrt branding adjusted, there are a few points i like to bring up. 18:37:09 ok. My intention here was to see how much we want to go back to the default setup of KDE itself. 18:37:13 shumski: Ok. shoot 18:37:36 1) we default to kicker due to famous kickoff crash, but that one seems fixed. do we want to continue with it 18:37:43 2) how branding is applied 18:38:05 due to https://bugs.kde.org/show_bug.cgi?id=340691 18:38:06 KDE bug 340691 in frameworks-kconfig (general) "system-wide kdeglobals "overwrite" local ones" [Critical,Reopened: ] 18:38:39 i am pondering to change how we apply kdeglobals 18:40:17 Well. If we go back to the defaults then we might not need to change kdeglobals :) 18:42:33 we usually deliver them in sysconfdir, but this bug makes it pretty bad. alternative idea is to ship separate startkde 18:42:41 both in our and upstream branding 18:42:57 yeah 18:43:05 Ok. And what would be the difference between the two ? 18:44:56 we would apply oS settings directly into ~/.config/ (upstream does that with some font settings e.g.). that would workaround that bug 18:45:41 tittiatcoke: the bug comes in form that if there is something in systemwide kdeglobals, e.g. BrowserApplication=firefox, users settings constantly revert to that, instead of his own 18:46:16 shumski: Ok. But how do we want to insert something in ~/.config ? 18:46:36 only 2 really important settings i guess are LookAndFeelPackage and BrowserApplication 18:46:49 tittiatcoke: that is an open question =) 18:47:07 would that work for users migrating from 4 to 5 ? 18:47:28 it would work for clean/non-existing kdeglobals in 5 18:48:05 so there's nothing that moves kdeglobals from ~/.kde4/share/config to ~/.config ? 18:48:14 what i want to say is i think this bug is bad enough to choose between no branding, and separate startkde's 18:48:20 krop: no afaik 18:49:00 shumski: What would a separate startkde do ? copy things to the user dir or viceversa ? 18:49:02 i know there was an upgrade script on oS for 3->4, if wanted i guess we can do that one also 18:49:37 tittiatcoke: upstream one would be upstream =) with openSUSE one we would inject few wanted settings into kdeglobals 18:49:39 question there would be how compatible is kglobal from kde4 with KF5 ? 18:49:52 shumski: Ok 18:49:56 at worse settings would be ignored 18:50:05 *some settings 18:50:19 true. Seems so far nobody really complained about that :) 18:50:58 yeah. about systemwide kdeglobals issue there where complaints though 18:51:13 Ah. Ok. 18:51:25 Well, lets go through the points one by one :) 18:51:40 First item is kicker vs kickoff. Which to take as default. 18:51:50 I guess that we should have kickoff there 18:51:59 and 3) question of artwork 18:52:35 tittiatcoke: i am not 100% sure. seems these days kicker is getting more love. will have ktp/contacts integration, et 18:52:35 and 4) menu categories 18:53:02 shumski: Ok. Wasn't aware of that 18:53:07 i am not against going back to kickoff, just saying 18:53:29 krop: any opinion ? 18:54:00 kickoff = traditional or kicker ? 18:54:09 well, no. I'm still using KDE4 apps/workspace on the desktop 18:54:16 krop: Ok :) 18:54:23 im kde4 i like classic menu, but that is just me 18:54:37 plinnell: kicker would be the homerun menu (but then not fullscreen) 18:54:44 shumski: correct ? 18:54:48 ok 18:54:57 yep 18:56:12 Ok. lets say that kicker is the favorite, but we are still missing einar in the voting :) 18:56:30 http://cdn.arstechnica.net/wp-content/uploads/2014/08/screenshot12.png 18:56:34 plinnell: ^ 18:56:37 And if it is already the current Plasma5 default, then people might be used to it :) 18:56:53 works for me :) 18:57:07 vs. http://i1-news.softpedia-static.com/images/news-700/Plasma-Next-Is-Preparing-to-Replace-KDE-First-Beta-Now-Available-for-Download.jpg (kickoff) 18:57:31 no please 18:57:50 im playing with the latest live DVD 18:57:53 seems ok 18:57:57 stable at least 18:58:05 patience does not crash 18:58:07 :D 18:58:11 =) 18:58:55 tittiatcoke: so for 1) undecided? or not enough votes to rule against kicker? 18:59:20 plinnell: Are you voting for kicker or kickoff ? 18:59:31 kicker.. strongly :) 18:59:47 Ok. Then this makes it 3 votes in favor. So we stick with Kicker :) 18:59:57 (the mentioned contacts integration should come in 5.3 afaik - not yet merged though) 18:59:58 oki 19:00:02 #info The default menu in Plasma5 will be kicker 19:00:24 wrt 2) i dunno. it's between bad and worse 19:00:44 that is the branding, right ? 19:01:15 yes. keep kdeglobals, inject them into ~/config instead, or drop completely 19:01:55 Let's see first what branding we go with ? Are we going back to the default upstream Breeze or do we want to keep the opensuse KDE4 branding ? 19:01:56 (2 most important settings we apply there are default browser, and used theme - both colorscheme, and plasmatheme) 19:02:43 i vote to drop current artwork (at least plasma theme). whether we want to go plain vanilla, or just colorize the breeze, not sure yet 19:03:21 krop: plinnell Any opinion ? 19:03:36 people seem to like (or hate) that we have some kind of artwork, but i don't have the strength, time nor motivation to keep it working properly with P5 19:03:43 +1 for vanilla (and a green icon somewhere to make everyone happy) 19:03:54 im with krop ^^ 19:04:08 what ever works best 19:04:14 Ok. So we drop back to breeze as desktop theme :) 19:05:11 we have an offer from somebody that is willing to change the icon colors into green (as seen on the os-kde ml) 19:05:14 * shumski finally won't have a guilty conscience for not porting the beast properly :D 19:05:20 yes 19:05:22 shumski: :) 19:06:05 shumski: Can I ask you to contact the volunteer and to see what can be done with the icons ? Whether just color or maybe some additional ones, etc 19:06:11 the svg looked ok to me. only i wonder will the same colorscheme be utilized for 13.3 19:06:14 tittiatcoke: sure 19:06:30 #info Breeze will be the default theme for Plasma5 19:07:06 #action shumski to contact the volunteer to openSUSE'ify the Breeze iconset 19:07:24 i wonder what reads default browser... so we can drop kdeglobals completely 19:07:39 shumski: I believe that is xdg-open 19:07:50 No, that one has its own settings. 19:07:57 tittiatcoke: but i guess it calls something within kde 19:08:19 will investigate that 19:08:25 Normally that would be the associations. e.g. clicking on a link in a KDE program 19:08:40 #action shumski to look into the default browser settings 19:08:58 tittiatcoke: 4) is upstream vs. suse menu ? 19:09:04 yup. 19:09:07 (i guess 3 is done?) 19:09:15 for now we use upstream 19:09:32 what is 'suse menu' ? 19:10:04 krop: in the past SUSE created their own categories and submenus. All desktop environments had to use this, so that each one of them had an equal menu. 19:10:35 what do the other desktop do nowadays ? 19:10:49 Gnome already dropped it and went back to upstream 19:11:04 perfect then :) 19:11:04 I believe that xfce might still use it 19:11:15 Yeah, that is why I wanted to propose to drop it also :) 19:11:28 ok. I guess we are aligned on using the upstream menu categories. 19:11:36 yep 19:11:42 #info the upstream KDE menu structure will be used 19:12:03 krop: We even had some bug reports about it in the past 19:12:18 ok. Anything else with regards to desktop stuff ? 19:12:47 Lets move on to the next topic. 19:12:58 #topic SDDM startup issue with Breeze theme. Solution, workaround, .. ? 19:13:47 I initially put this topic as that in the past we saw that SDDM had a big delay in showing the breeze login screen after booting. Seems however that with the latest tumbleweed this is resolved. Or does anybody still sees this ? 19:14:10 * shumski isn't too happy with it's speed, but nothing critical 19:14:17 its working ok for me 19:14:37 Ok. Then lets just keep an eye on it. 19:15:25 sounds good 19:15:26 shumski: I will submit a small patch for sddm in KUF to adjust the service file. It seems if you start using the real systemd service file, plymouth is not killed and causes some strange effect on sddm. einar77_work suffered from this 19:15:35 tittiatcoke: okies 19:15:48 #topic Status KDE Applications 15.04. 19:17:47 I have been preparing KDE Applications 15.04 in the repository KDE:Applications and those packages will obsolete the current packages. Only thing missing is the KTP packages. Target would be to release KDE Applications 15.04 for TW only together with the switch to Plasma5. Kdepim will remain to be KDE4 based 19:18:38 tittiatcoke: deps missing for KTP? 19:18:53 shumski: nope. Didn't had the time yet to create the packages :) 19:19:40 ok =) 19:20:34 #topic OBS repositories that will be used for Frameworks, Plasma and Applications. 19:20:41 the target has been spoken already, and at least to me it still sounds good 19:20:49 ah, new topic =) 19:21:57 As we have been discussing in the past. We would end up with two main repo's: KDE:Frameworks5 and KDE:Applications. This would follow more upstream as well. We also would have KDE:Unstable:Frameworks and I wonder if we should create a new KDE:Unstable:Applications and remove KUE. 19:22:28 Is this still something that we want to continue with or do we want to move back to the old repositories ? 19:22:58 shumski: krop plinnell ?? 19:23:04 that is something that i agree with (the 'new' setup) 19:23:36 Ok. Do we have reasons to pull Frameworks / Plasma apart ? 19:23:53 most due to name 19:24:09 components and files are still moving between the 2 19:24:31 ok. I don't see a reason for a split, but ... :) 19:24:31 mmh 19:24:31 e.g. kglobalaccel, libmm-qt, etc 19:24:51 KDE:Applications would contain what we moved to KDE:Extra ? 19:25:07 im agreement with whatever is easiest 19:25:10 krop: Nope. KDE:Applications would contain really the KDE Application releases 19:25:25 e.g. 14.12, 15.04, etc. 19:26:05 now that krop mentioned it, i wonder if K:E content could be merged into K:App 19:26:15 We could 19:26:21 (could, and should?) 19:26:46 just a thought 19:27:06 :) I will go with the majotiry :) 19:27:10 majority :) 19:28:28 Ok. I guess we can leave this so that we can think about it :) 19:28:50 I think a lot of the KDE:Extra packages are pretty well maintained in a quality sense 19:28:52 #action bring up the Repositories in the next meeting and particular if KDE:Extra should be merged with KDE:Applications. 19:29:07 true 19:29:23 ive been a pretty fussy reviewer 19:29:25 :) 19:29:25 and we have established good control of maintainership there as well 19:29:54 * shumski didn't mean they aren't, just that K:E and K:A content would be quite similar - just difference by whom is released 19:31:20 shumski: yup :) Another question would be what to do with the packages in KUE ? All of them have the suffix 5 now. I guess we need to recreate them after the transition to a package without 5 :) 19:31:24 I'm thinking about KUE as well, there are a couple apps that wouldn't fit KUA 19:31:48 to follow the packaging in KDE:Applications 19:31:54 if by KUA we mean snapshots of apps also living in KDE:Applications 19:32:05 tittiatcoke: yeah.. quite a few packages there 19:32:11 krop: like ? 19:32:27 scribus, kdenlive 19:32:53 krop why wouldn't they fit KUA ? Given that we want to merge KE into KA :) 19:33:24 the question is reversed then, do we want all of K:E in K:A 19:33:47 :Extra is really huge nowadays 19:34:18 yeah.. at least dropping some targets there reduced the used space =) 19:35:07 krop: Yeah. I am not really convinced that we want to merge K:E into K:A 19:35:30 hm. that would be a gigantic project 19:35:55 so looks we can drop the idea :D 19:36:25 shumski: Yeah. Lets stick with KDE:Frameworks, KDE:Applications and KDE:Extra. And then also the unstable repositories for those three. 19:36:26 thing is every update would be a maintenance request 19:36:32 oki 19:36:46 plinnell: how do you mean? 19:36:49 plinnell: Why a maintenance request ? 19:37:17 sorry i was thinking of what is shipped in the next release 19:37:26 sorry for the noise 19:37:40 :) 19:37:56 ok =) /me is still confused, but nevermind =) 19:38:13 Ok. So who is in favor of following the structure KDE:Frameworks, KDE:Applications and KDE:Extra. 19:38:35 these ones look fine 19:38:59 +1 19:39:03 Ok. And then we would also have an Unstable variant for those three. 19:39:03 same from here 19:39:13 +1 19:40:11 #info The new repositories would be KDE:Frameworks (for Frameworks and Plasma5), KDE:Applications (for the KDE Application releases) and KDE:Extra (for other KDE/Qt related community packages. For each one of these repos we would have an unstable variant. 19:40:29 Ok. that would bring us to the last topic. 19:40:35 #topic Anything Else ?? 19:40:52 shumski: plinnell krop: anything else that you would like to bring up ? 19:41:19 can't think of anything else now 19:41:19 all the hot topics were discussed 19:42:11 nope, you guys have done a great job keeping KDE in shape 19:42:16 really awesome 19:42:35 there is still an effort to get KF5 on SLES12 19:43:09 work in progress 19:43:13 hm, will try to unbreak plasma-nm5 for sles, only that one hasn't built 19:43:24 ok 19:43:33 cool, let me know if i can help 19:43:59 nah, just a condition to not build with openconnect 19:44:25 ok. Then I close the meeting. 19:44:32 Thank everyone for their participation 19:44:41 tnx for leading =) 19:45:17 #endmeeting