19:12:55 #startmeeting 19:12:55 Meeting started Sat Feb 8 19:12:55 2014 UTC. The chair is einar77. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:12:55 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:13:13 #meetingtopic Welcome to the openSUSE KDE community IRC meeting! Please wait with other discussion until the meeting is over. This meeting is logged. 19:13:29 Ok, let's start 19:13:37 We have two topics on the agenda so far 19:13:43 oki, shoot 19:13:47 optimizations first 19:14:01 and also a request by tigerfoot on the OSC packaging workshop 19:14:18 let me alos go through the old notes 19:15:03 ok. i missed the last one where we should have discussed kf5 status, etc. my idea is to push it asap to O:F 19:15:15 #topic old action items 19:15:27 shumski: we're on alpha 1 for KF5 19:15:31 yep 19:15:41 I'm guessing you want to push it to Factoyr? 19:15:48 yep =) 19:16:00 It should be released soon IIRC 19:16:04 I have to check the schedule 19:16:06 i've created KDE:Frameworks5 project 19:16:09 tuesday 19:16:32 "stable" releases for KF5? 19:16:40 the name is open for discussion, but i need a place to push the proper tars 19:16:41 yep 19:16:56 and opened today security revieww for kinit 19:16:59 shumski: I'm guessing you'll have to announce it also the ML 19:17:15 I would say once alpha 1 is actually out 19:17:21 einar77: yes. but i wanted to see what others think 19:17:34 to be honest I?m not sure 19:17:44 KDE:Unstable:Frameworks is totally distinct 19:17:50 I would call it just frameworks though 19:17:54 KDE:Frameworks 19:18:22 ok. this is easily changed, as said, just needed a place to work with proper tars 19:18:39 (and publishing is disabled anyway there) 19:18:50 agreed that we need it 19:19:02 shumski: still uses the /opt mechanism for now? 19:19:12 einar77: nope. it is now in /usr 19:19:21 2 files left to adjust 19:19:37 kross manpage, and a desktop file for locale 19:20:01 but still coinstallable I assume? 19:20:22 everything else can co-exist. depending what will happen with kactivities and plsma-framework they'll need adjustements 19:20:25 yeo+p 19:20:29 *yep 19:20:58 at least my system didn't explode =) 19:21:03 ok, it's a start 19:21:15 I would say, notify the rest of the team first, then the mL 19:21:25 given it's just you and me 19:21:33 agreed =) 19:22:02 #action shumski to mail the team about the stable KF5 repository 19:22:52 given that SFaulken-AFK is not here, and he was suposed to pushing cloverleaf systemsettings to KUSC, I'll put action again for the future 19:23:09 #action 19:23:11 SFaulken to push the cloverleaf systemsettings to KUSC as a starting point 19:23:12 for further optimizations 19:23:14 bah 19:23:29 #action SFaulken to push the cloverleaf systemsettings to KUSC as a starting point for further optimizations 19:23:35 (atm i cannot open that optimization wiiki page) 19:23:46 I have it open 19:23:51 in fact let's go over that now 19:24:11 #topic openSUSE KDE packages optimization 19:24:27 Currently we have two actions open 19:24:33 "Make social desktop optional" 19:25:01 I'm guessing nepomuk, but I'm wondering, given that Baloo will be the default in 4.13, whether it makes sense to work on that 19:25:04 ok. i'd like an elaboration on that one =) 19:25:17 my guess is semantic desktop 19:25:19 and not social 19:25:28 nepomuk/baloo/akonadi are already optional 19:25:39 but as I said, Baloo makes the point kind of moot 19:25:40 so i am not sure what should be worked on 19:26:11 The other is "simplification of KDE systemsettings" 19:26:35 I would say we need other people to discuss on this 19:26:51 einar77: wrt first item. i've splitted baloo package to components, so one can choose between them, or all, or none 19:26:55 yep 19:27:06 so that means we already handled it sort of 19:27:14 also baloo is considerably lighter on resources than neopmuk 19:27:23 (e.g. baloo-file, baloo-pim, etc) libraries cannot be ommited 19:27:31 so I'm hoping it will get less flak 19:27:32 also true 19:27:43 (I'll say a bit more once we switch topics) 19:27:51 for the rest, discussion is deferred to next meeting 19:27:58 + 19:28:07 #info Discussion on optimizations deferred to next meeting, need more people present 19:28:24 #topic Q&A, misc 19:28:39 there's already one important thng that happened meanwhile 19:28:45 that i? 19:28:47 is? 19:28:48 13.2 is in November 19:28:52 right 19:29:00 so, no 4.13 =) more 4.15 19:29:15 I would say, use the latest stable version available at the time 19:29:24 provide KF5 for the corageous 19:29:31 KF5 + Plasma Next 19:29:35 corageous and developers, that is 19:29:46 if they go on schedule, we should have something like that 19:30:20 and as said, we should be able to squeeze in 4.15. but, there's time for that now 19:31:10 I would suggest after Plasma Next release to try and test it in parallel with traditional 4.x 19:31:19 so we get a feel of how it is 19:31:29 (and from my end to report - > i'll submit Qt 5.2.1 today/tommorow likely) 19:31:31 but for sure, offer it optionally 19:31:35 yes 19:31:57 KF5 / Plasma Next would be considered again for 13.2+1 19:31:59 IMO 19:32:21 considered again? 19:32:23 we can always provide repositories if things go exceptionally well but I wouldn't want to push it on users 19:32:24 as? 19:32:28 well 19:32:35 I have no idea what upstream will do 19:32:46 workspace is LTS for 2 years 19:33:02 we're getting close to one IIRC 19:33:38 also once KF5 opens up for features again, we'll likely see some more movement by app developers 19:33:42 so to sum up 19:34:02 was Thu Aug 8 when 4.11.0 was uploaded 19:34:10 1. 4.x default for 13.2 + KF5/Plasma Next as option 19:34:25 +1 from me =) 19:34:40 2. Re-evaluate if keep (1) or switch places for 13.2 19:34:47 er 19:34:49 132.2+1 19:34:51 13.2+1 19:34:53 correct 19:35:07 ok, sorry, need to run now =( 19:35:45 #info For 13.2, keeping 4.x (latest version available) and KF5 / Plasma Next as option, for 13.2+1 re-evaluate which use as default 19:35:48 no problem 19:35:56 Let's end it here 19:36:09 #endmeeting