14:04:25 #startmeeting kde-sig -- https://fedoraproject.org/wiki/SIGs/KDE/Meetings/2010-07-20 14:04:25 Meeting started Tue Jul 20 14:04:25 2010 UTC. The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:04:25 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:04:31 #meetingname kde-sig 14:04:31 The meeting name has been set to 'kde-sig' 14:04:37 #topic roll call 14:04:43 who's present today? 14:05:09 * rnovacek here 14:06:14 than, Kevin_Kofler, jreznik, SMParrish : ping 14:06:25 Present. 14:06:28 * than is present 14:06:43 * SMParrish here 14:07:25 #chair Kevin_Kofler than SMParrish rnovacek 14:07:25 Current chairs: Kevin_Kofler SMParrish rdieter rnovacek than 14:07:37 #info rdieter rnovacek Kevin_Kofler than SMParrish present 14:07:46 * jreznik is here 14:07:57 #info jreznik also present 14:08:02 #chair jreznik 14:08:02 Current chairs: Kevin_Kofler SMParrish jreznik rdieter rnovacek than 14:08:07 #topic agenda 14:08:21 I threw a few items on https://fedoraproject.org/wiki/SIGs/KDE/Meetings/2010-07-20#Agenda 14:08:25 anything else for today? 14:08:42 * rdieter fetches some coffee quick 14:12:20 ok, guess that means nothing else. :) 14:12:34 #topic F-14: to kdepim-4.5 or not to kdepim-4.5 14:13:05 Kevin_Kofler: I figure you want to try to make the case to include this again? let's here it. :) 14:13:37 i thought we already made decision here! 14:13:37 I think Fedora is about shipping current stuff. 14:13:53 than: we decided last week to defer for a week, now's the time 14:13:56 And sure it's not stable yet, but neither are we, there are 3 months until release. 14:13:56 Kevin_Kofler: but not broken one 14:14:22 We can only fix the issues if we actually have the software packaged and tested by Rawhide users. 14:14:22 ok, anyone asked upstream for clear conclusion? without it - we can argue for nothing 14:14:34 Otherwise they'll never get fixed. 14:14:40 jreznik: +1 14:14:51 Plus, IMHO migration is not a showstopper for a new Fedora (only for updates to an existing release). 14:14:57 Sure, it's bad if migration doesn't work. 14:15:22 Kevin_Kofler: we can upload kdepim 4.5 to redhat-kde! 14:15:33 why is the problem? 14:15:35 But sometimes upstream just breaks it and there must be a place to do a nonmigratable update or we'll be stuck with the old version forever. 14:15:46 Kevin_Kofler: PIM is about data - if you loose data - it's bad... and not only migration - but what if we ship some beta that will have problems with data migration to stable version 14:15:55 people who want to test it can download from there 14:17:40 with clear statement from upstream (release schedule), promise not to break data with newer version - I'm +1 (at least for Rawhide, we can pull it back) 14:17:41 Fedora is not RHEL. 14:17:56 What's the point of Fedora if we stop shipping current software. 14:18:21 Kevin_Kofler: there's big difference - current software and unstable software 14:18:36 Kevin_Kofler: we just avoid to ship unstable software 14:18:40 Kevin_Kofler: we need to ship reliable software. If upstream says they cant guarantee stability and no data loss we cant ship it 14:18:43 There's not much new information than from last week, except that heliocastro tried it, and found it pretty bad still 14:19:23 upstream's recommendation is still that it's not ready, and I'm of a mind to follow their advice. 14:19:27 Is the data format stable now? i.e. have they said that they aren't going to change the way they save data during the beta 4.5.x releases? 14:20:37 good question 14:20:51 I tried it too and I was unable to fetch my gmail mailbox... it used a lot of CPU and it didn't finish in about an hour 14:20:57 I'd venture the answer is a qualified yes (format stable) 14:21:53 we will follow upstream's advice. 14:22:00 seems support for inclusion is limited to Kevin_Kofler, so I think this isn't going to happen. Kevin_Kofler, unless you want a formal vote or have more to add, let's move on 14:22:37 move on please 14:23:19 I'm for closely watching current status of kdepim - but I don't believe it's going to be ready by f14 14:23:41 I have no clue about this particular package, but I'm all for keeping rawhide usable. With the new stable updates release vision, I think more and more people will (and should) start using rawhide. If lots of people are saying that it doesn't work at all ... 14:24:02 #agreed kde-sig (majority) agrees to not include kdepim-4.5 in F-14 14:24:17 #topic include both plasma-nm and nm-applet on kde spin? 14:24:38 Sigh, nobody wants to ship current software in Fedora anymore. :-( 14:24:55 Are we "Fubuntu" now? Or Fedora Enterprise Linux? :-/ 14:25:06 moving on... I added nm-applet to spin-kickstarts, but this seems to have been a bit controversial 14:25:15 per on-list conversation. 14:25:23 jreznik's proposal doesn't make sense either, we can't wait any longer, if we want it, we need it imported NOW. 14:25:30 at least 2 suggestions were even made to switch to nm-applet by default 14:25:32 There's the feature freeze and we also need testing. 14:25:53 rdieter: Shipping nm-applet is entirely useless because there's no obvious way to turn it on. 14:26:02 We're just wasting space we don't have. 14:26:13 We need to ship one default applet (kde-plasma-networkmanagement) and stick to it. 14:26:19 tis true, it takes a bit of manual futzing to use it 14:26:44 People won't know how. 14:26:54 If they can get to the net to look up instructions, they can also fetch the package. 14:27:17 which is worse, provide no options for those folks who find plasma-nm non-functional or provide nm-applet which is a bit hard to use 14:27:53 how can they fetch any package, if they have no network? 14:28:10 oh ok, instructions = package, fair nuf 14:29:12 any other opinions? comments? 14:29:15 If they have no network, how are they to figure out the manual steps to enable nm-applet? It's not like those are easy for the average user. 14:29:26 It's just going to sit there and waste space we don't have. 14:29:40 Kevin_Kofler: the logical conclusion there is to just use nm-applet, that 'just works' 14:29:41 one or another one but not both 14:29:52 I would prefer shipping the plasma applet but only if its a fully functional replacement for nm-applet 14:29:54 rdieter: Ugh… 14:30:12 nm-applet is broken too quite a lot... 14:30:19 What are you missing from the plasmoid? 14:30:22 SMParrish: we're back to defining a minimal set of functionalities then or defining "fully functional" 14:30:38 Full support for mobile broadband? I can try to backport the stuff that's under development now. 14:30:57 Kevin_Kofler: good vpn support for one 14:31:16 rdieter: still minimal, wpa2, vpn etc 14:31:23 mobile broadband I (still) consider non-essential, but still nice to have 14:31:43 so, do we consider vpn support a blocker or not? 14:31:48 Uh, WPA just works, at least in knetworkmanager. 14:32:04 I can try the plasmoid if you think it might have trouble there. 14:32:18 Kevin_Kofler: yes, please do test it out 14:32:24 would be nice to have more data 14:32:35 Do we have a current snapshot in F13 now? 14:32:45 but, it should function almost identical to knm, since they share a common backend 14:32:49 i don't think vpn support is a blocker 14:32:51 (It's not very useful to test old stuff.) 14:33:04 Kevin_Kofler: f13 has a relatively new snapshot, yes 14:33:13 (matching what's in rawhide atm, I believe) 14:34:04 so, revert the change I made, drop nm-applet from the spin ? 14:34:28 shipping both nm-applets and plasma-applet doesn't make sense 14:34:31 +1 14:35:05 rdieter: is plasma applet a fully functional replacement for nm-applet? 14:35:19 than: define "fully functional" 14:35:21 Making it too easy to use nm-applet also means we won't get testing feedback if the plasmoid doesn't work. 14:35:38 if "fully functional" = supports *all* nm-applet features, then the answer is no 14:35:39 We can reconsider if we get closer to the release and have space left to spare. 14:35:46 vpn support would be nice 14:35:48 network/modem/dsl and mobil should work 14:36:12 of course wlan 14:36:36 and arguments were made onlist about plasma-nm's UI, it's a bit more complicated and less streamlined than nm-applet 14:37:17 I believe that was dgilmore who made that comment 14:37:20 it's basic things which should work in plasma-nm 14:37:21 Well, it's more powerful/flexible than GNOME's minimalist UIs. :-) 14:37:56 * dgilmore is going to lunch 14:37:58 oh, and apparently it's support for configuring static ip/dns either doesn't work or is lacking (I've heard complaints, not verified) 14:38:13 but connecting to a new wireless network is not simple and is full of bugs 14:38:53 * rdieter thinks new wireless setup is fairly simple. ? 14:39:02 Please send your complaints upstream… 14:39:09 click applet -> show more 14:39:10 task for all kde siggers - test, test and test knm, plasma-nm 14:39:16 It's not our job to improve the UI unless it's really broken. 14:39:22 (And even then the fix should be made upstream.) 14:39:38 though I think nm-applet announces new networks proactively 14:39:42 jreznik: The plasmoid is what needs most testing. 14:39:49 KNM is deprecated AFAIK. 14:40:08 rdieter: s/proactively/annoyingly/ 14:40:22 #agreed revert recent change to spin-kickstarts, do not include nm-applet on kde spin 14:40:28 from my observations all three are broken completely and it's shame for us (linux desktop) 14:40:47 I don't want to be offered some random neighbor's WLAN just because the one I want to connect to has a short hickup. 14:41:05 #help kde-sig'ers test test test plasma-nm 14:41:18 rdieter: not when it displays info for other networks when you try and do it 14:41:30 Kevin_Kofler: i sent them upstream. they were silent 14:42:07 Then they probably think their UI is just fine. :-) 14:42:32 is there IPv6 support in knetworkmanager? 14:42:36 as usual, there's a downside including this (similarly for kpk) when we have no fedora developers involved in the project 14:42:37 it doesnt work so its not fine 14:42:40 anyways im going 14:43:11 we're captive to their whims. 14:43:34 vs. including stuff that's developed and supported within fedora, by fedora developers 14:44:01 The disconnect between Fedora and upstream on KDE can be a problem indeed. 14:44:13 On the other hand, it's how an upstream-distro relationship usually works. 14:44:47 And it also means we're not subject to conflicts of interest when Fedora's goals and upstream's conflict (see e.g. the Mozilla trademark issues). 14:44:57 I'll bring up the topic of what to do with kpk next week 14:45:03 rdieter: ok 14:45:21 moving on... 14:45:24 #topic cmake macros: drop -DBUILD_SHARED_LIBS:BOOL=ON (by default)? 14:45:39 floated that around onlist awhile, are we ready to implement this now? 14:46:00 I'd like to try to get more involved upstream, but I'm already doing a poor job (at least according to my own standards) with Kompare, so I don't think trying to get into even more upstream projects is doable. :-( 14:46:19 orion had a concern about stuff breaking (pkgs that build shlibs now, that would change) 14:46:36 * Kevin_Kofler shares his concerns. 14:46:46 (As already said previously on IRC.) 14:46:48 but as long as we communicate the change clearly, as well as ways to revert to the old behavior, I think that's manageable 14:47:42 I pretty much agree with what Orion said: "Fedora strongly encourages shared libraries as shared libraries are good. 14:47:43 If a package really wants a static library it should explicitly state it." 14:48:03 FWIW, I think %configure should include --enable-shared, too, but that's not our decision to make. 14:49:06 * rdieter thinks shlibs for convenience libraries is a wee bit silly, wasteful (esp since it forces one to deal with multilib'ing) 14:49:41 now, for projects that provide shlibs, headers, api, all for that 14:50:30 i agree with Kevin, SHARED_LIBS should stay default 14:51:51 ok, looks like a no-go 14:52:24 #agreed (majority) NACK'd cmake proposal to drop -DBUILD_SHARED_LIBS:BOOL=ON 14:52:39 At the very least we should know what breaks before making that change in Rawhide. 14:52:53 (e.g. do local mass rebuilds or so) 14:52:54 sorry, I was in another window. I also agree with Kevin, I think we should instead write up a guide how to deal with convenience libs which doesn't have explicit STATIC in add_libraries() call. 14:53:13 #topic fedora-kde-icon-theme : Inherits=oxygen not working as expected (https://bugzilla.redhat.com/615621) 14:53:21 kalev: volunteering? :) 14:53:21 But IMHO stuff which wants STATIC should explicitly state it. 14:53:30 Kevin_Kofler: +1 14:53:46 rdieter: yeah, I'm stumped at work right now, but I'm planning to do it eventually 14:53:58 had several reports recently about mimetypes with '?' icons 14:54:13 Bug in the MIME type icon loading code? 14:54:18 with problems going away if one switches fedora-kde -> oxygen 14:54:35 If the Inherits works for everything else, but not that code, that sounds like a bug in that code. 14:54:38 dunno, interesting that this problem wasn't noticed until very recently 14:54:56 What DE and version were the reports with? 14:55:05 * rdieter verified with kde-4.4.5 14:55:05 I assume KDE, but was it only 4.5 maybe? Or also 4.4? 14:55:28 original reporter was using 4.4.92 I believe, but I can double-check 14:55:46 So 4.4.5 has the problem? What about 4.4.4? 4.4.3? 14:56:01 We need to figure out when it started, unless it was always there. 14:56:04 perhaps regression in 4.4.5 ? 14:57:02 however i cannot reproduce this issue on my machine with 4.4.5 14:57:02 * rdieter suspects kdebase-runtime-4.1.1-iconthemes-inherit.patch may have something to do with it 14:57:12 than : oh? interesting 14:57:20 fwiw, than, what's that old patch for ? 14:59:01 it fixes the inherit issue in old kde 4.1 14:59:10 preferences: 1. if it's a genuine issue, upstream it. 2. if not upstreamable, please document what it does, why we're carrying it, and why it's not upstreamable 15:00:11 we're out of time 15:00:14 Speaking of patch documentation, I noticed that the RHEL 6 Beta 2 specfiles have comments added for some patches, please also add those comments to the Fedora specfiles. 15:00:29 jreznik: indeed. 15:00:38 let's wrap up, thanks everyone 15:00:40 #endmeeting