14:00:21 #startmeeting kde-sig -- http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2010-07-13 14:00:21 Meeting started Tue Jul 13 14:00:21 2010 UTC. The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:21 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:27 #meetingname kde-sig 14:00:27 The meeting name has been set to 'kde-sig' 14:00:36 #topic roll call 14:00:39 who's present today? 14:00:51 * rnovacek here 14:01:02 than, ltinkl, jreznik, Kevin_Kofler, smparrish, kde*foo : ping 14:01:02 * smparrish here 14:01:03 * jreznik is here 14:01:08 * ltinkl is here 14:01:14 * than is present 14:01:46 Present. 14:01:51 #info rdieter rnovacek smparrish jreznik ltinkl than Kevin_Kofler present 14:01:57 #chair rnovacek smparrish jreznik ltinkl than Kevin_Kofler 14:01:57 Current chairs: Kevin_Kofler jreznik ltinkl rdieter rnovacek smparrish than 14:02:12 #topic agenda 14:02:20 http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2010-07-13#Agenda 14:02:29 anything to add to the agenda for today? 14:02:46 (otherwise, looks like we'll have plenty to discuss) 14:03:04 yes, first point: welcome rnovacek :) 14:03:16 * cwickert is here too 14:03:21 ltinkl: thank you 14:03:52 #info cwickert present 14:04:12 #topic kde-sig welcomes rnovacek 14:04:20 * maxamillion is kinda here 14:04:21 rnovacek: indeed, welcome 14:04:39 #info maxamillion (kinda) present :) 14:04:50 Welcome rnovacek! :-) 14:04:52 rdieter: rnovacek the one the "who the hell is ?" email was about? 14:04:58 maxamillion: yes 14:05:02 awesome! 14:05:03 rnovacek: Welcome 14:05:06 rnovacek: welcome!! :) 14:05:15 thanks to you all ;) 14:05:23 rnovacek: welcome 14:05:38 rnovacek: thanks already for the bz triage, earned our gratitude already. 14:05:40 rnovacek is already helping us a lot, just in the shadow ;-) 14:06:11 rdieter: I'm not finished with it yet :) 14:06:48 alright, let's get started on the juicy stuff 14:06:53 rnovacek: Yes BIG thanks on that, my time for it has been scarce these past few weeks 14:07:19 #topic http://fedoraproject.org/wiki/Features/KDE45 14:08:06 Not too thrilling, but please look over the kde45 feature page, in case there's anything obviously wrong or missing 14:08:18 thanks to Rex who has initially copied over the KDE44 feature as a template 14:08:25 erm, do we follow the agenda from top to bottom? is kdepim a topic of it's own? 14:08:34 * rdieter has mad copy-n-paste skillz 14:08:40 cwickert: will come next :) 14:08:55 ok 14:09:00 sorry, I took the liberty of ordering (what I consider to be) import stuff first 14:09:11 ** kde-plasma-networkmanagement by default 14:09:20 Well, I put kdepim first because I consider it more important. ;-) But whatever. 14:09:23 have we agreed on that already? 14:09:36 ltinkl: IMHO it's obvious. 14:09:36 ltinkl: yes (I thought so) 14:09:39 knetworkmanager is deprecated. 14:09:46 The plasmoid is the way to go now. 14:09:52 I mean, default as in replace nm-applet 14:09:52 So let's default to the plasmoid from now on. 14:10:00 We already replaced nm-applet in F13. 14:10:05 (not that I'm against it) 14:10:33 +1 for the plasmoid, knetworkmanager is kinda crufty 14:10:37 umm, on LiveCD only? 14:10:48 On KDE installs. 14:11:03 Also nm-applet does not by default autostart in KDE if installed (since F13). 14:11:10 I still have the nm-applet here as the default :) 14:11:13 * ltinkl wonders why 14:11:22 ok, one related question there, for f14+ do we even want to ship monolithic knetworkmanager at all? 14:11:31 rdieter: I'd say not 14:11:44 I'd say ship it, but disable autostart by default. 14:11:45 rdieter: can it be left out at compile stage? 14:11:58 And don't put it on the live CD, only ship it in the repo. 14:12:07 besides, there's currenlty a problem missing kde45's dbusmenu-qt and knm anyway 14:12:07 /win move 5 14:12:10 sounds ok 14:12:19 s/missing/with/ meh 14:12:41 it can be left out or autostart disabled. 14:12:43 But if you want to discontinue it entirely, I guess we can do that, too. 14:12:55 anyone against making the applet default? jreznik, than, rnovacek? 14:12:56 I would say leave it out entirely 14:12:57 Upstream seems to have decided that the plasmoid is the way to go these days. 14:13:01 I'd tend to provide it for those who want/need it (agreeing with Kevin_Kofler) 14:13:14 but meh. 14:13:18 I'm for applet 14:13:31 I also think shipping knm as a non-default option in the repo can't hurt. 14:13:34 how about this, ask upstream. if they truely want knm deprecated, then omit it 14:13:40 But the plasmoid is the way to go for default. 14:13:43 rdieter: Good idea. 14:13:48 yup 14:14:16 #action rdieter to consult knm upstream about future of monolithic client 14:14:18 we should ask upstream first 14:14:25 before makinf decision 14:14:41 anything else wrt kde45 feature? 14:14:53 anything else to add? 14:15:12 not sure if it's worth mentiong qt47 here, it's not required by kde45 14:15:26 but we will base KDE on it, right? 14:15:39 it could almost be mentioned as a separate feature, 14:15:52 so, may as well include it here I guess 14:15:52 btw, what is the state of phonon-vlc? 14:16:15 rdieter: it can be combined in one feature page 14:16:15 Unlikely to make F14, I'm afraid. 14:16:17 today is deadline 14:16:33 ltinkl: still largely experimental (support for vlc-1.1 is still evolving anyway) 14:16:40 Phonon-VLC is not ready for production upstream, nor is our VLC packaging going along for Fedora. 14:16:46 Kevin_Kofler: +1 14:17:14 ye I thought the legal issues with packaging might be a problem 14:17:31 ltinkl: That, and also the usability of phonon-vlc itself. 14:17:38 Sho_ says there are crashes. 14:17:38 ltinkl: the legal blockers are resolved, just the pkg review is moving a bit slowly 14:18:02 k, let's move onto kdepim 14:18:05 kwizart's attention/focus is getting vlc-1.1.x in shape for rpmfusion 14:18:06 rdieter: Another thing is that phonon-vlc should not depend on vlc the app, only the libs. 14:18:14 So vlc should get split properly according to that as well. 14:18:31 Kevin_Kofler: that too, though it only pulls in vlc-core atm, not vlc itself 14:18:49 alright, let's move on 14:18:56 Also, kwizart absolutely wants libva support in vlc 1.1, and libva has been blocked under FE-LEGAL for a while. 14:19:02 Now he's getting libva into RPM Fusion. 14:19:15 But that means he won't like having to build vlc without libva to move it into Fedora. :-( 14:19:25 ok, that's definitely a related problem, not sure if that affects the core library, or just plugins 14:19:46 :( alright 14:19:48 He's not updating vlc in RPM Fusion before he has libva. 14:19:54 #topic kdepim 4.5 in Rawhide 14:20:02 I think we could do fine without libva. 14:20:53 ok, kdepim-4.5 beta/prereleases for rawhide, who's topic is this? 14:21:03 Well, I put it on the schedule. 14:21:15 This is really an important decision. 14:21:23 IMO rawhide is not the question, the question is about F14 14:21:27 Do we want to ship kdepim 4.5 in F14? 14:21:39 cwickert: Well, if we want it in F14, we'll need to import it into Rawhide ASAP. 14:21:47 excellent question alright. 14:21:53 If we don't want it in F14, then we should only import it after F14 branches. 14:21:54 and if not, what do we do in the F14 cycle? 14:22:07 we cannot update it during the release because of the stable release vision 14:22:10 IMHO, we should put 4.5 into F14. 14:22:13 +1 14:22:23 this means having it in rawhide ASAP 14:22:28 If upstream doesn't release the final version on time, we ship whatever prerelease is there. 14:22:32 +1 14:22:37 I'm not sure if kdepim 4.5 stabilizes enough for F14 14:22:38 As we did for other stuff. 14:22:48 ltinkl: upstream says yes 14:22:49 ltinkl: that's my concern too 14:23:07 We already have something in devel CVS, we should put it into Rawhide now. 14:23:13 cwickert: they can't say yes, that is nonsense :) nobody has a crystal ball 14:23:18 Then track the prereleases from now until the F14 release. 14:23:40 I'd propose something similar as in the knm case, someone take the task to consult with kdepim upstream on their opinion on it's readiness in time for f14 development cycle 14:23:42 ltinkl: it's not magic, they are working on it very hard 14:23:51 it's to early to have kdepim 4.5 in f14 14:23:56 And if we don't have a final release by the F14 release, we should be able to push it as an update, it's clearly a bugfix, so I don't think anybody will complain, new update policies or not. 14:23:58 cwickert: I'm not saying they aren't 14:24:06 how stable is it` 14:24:15 (a bugfix compared to the prereleases, I mean) 14:24:20 than: right now pretty unfinished 14:24:36 rdieter: We don't have much time. 14:24:49 cwickert says we should write a feature page, the deadline for that is today. 14:24:50 remember even upstream can change their plans in 1 month or 2 14:24:50 I would like to see it in F14, but concerned about stability and testing time 14:24:55 And feature freeze is in 2 weeks. 14:25:02 I think that if we want it, we should import it NOW. 14:25:04 ltinkl: i'm strong against shipping kdepim 4.5 in f14 14:25:05 than: the big question is: what if we don't ship it in F14 and then it comes with KDE 4.5.1 or 4.5.2 do we want to build kdepim 4.4 again? 14:25:28 cwickert: the anwer to that question is yes, stick with 4.4 14:25:37 answer 14:25:49 cwickert: Yeah, plus, 4.4 is a pretty much temporary migration release, in the middle of the Akonadi migration. 14:25:50 but this will slow down the KDE 4.5.x updates 14:25:58 So there's KAddressBook using Akonadi and the rest not. 14:26:05 than: +1 14:26:10 +1 Kevin_Kofler, I doubt 4.5 will be worse than 4.4 14:26:11 cwickert: how so? 14:26:20 I think usage pim is crucial for most users 14:26:47 so I'm +1 for stick with 4.4 14:26:49 rdieter: I#am afraid it will require extra work. what is kdepim 4.4. doesn't build with 4.5 libs? 14:26:55 anyway, how about we not get ahead of ourselves, with second guessing on if it'll be ready for us or not. 14:26:56 * ltinkl sees a voting inevitable :) 14:27:06 I'm for putting kdepim 4.5 (back) into Rawhide and kde-unstable ASAP and shipping whatever prerelease will be current at release time in F14. 14:27:10 cwickert: devs have said they are committed to kdepim-4.4.x being compat with kde-4.5 runtime 14:27:14 and have 4.5 in kde-redhat for deeper testing... 14:27:26 ltinkl: it's about voting - even upstream is scared from data migration issues 14:27:32 and PIM is all about DATA 14:27:42 I'm also worried about the KDE 4.6 update, which I'm sure we'll provide one way or the other. 14:27:47 rdieter: only the e5 branch, not head 14:27:51 exactly for that reason I am strongly against kdepim 4.5 in F14 14:28:01 cwickert: that's not the message I got 14:28:02 (be it in updates, "updates-features" or whatever it will be called, kde-redhat stable or wherever) 14:28:23 we can try to build kdepim 4.5 in the kde-redhat repos for testing 14:28:23 Upgrading kdepim from 4.4 to 4.6 mid-release might cause a lot of disruption. 14:28:31 rdieter: I'm sitting next to many people, so I consider my info up to date 14:28:34 4.5 to 4.6 is going to be a much smaller change. 14:28:54 cwickert: ok, I'm going off the mails sent to the kde release team from winterz 14:29:08 It'll be much simpler to upgrade to 4.6 from 4.5 than from 4.4. 14:29:19 I'll try pinging him (or other kdepim devs) after meeting to get their take on whether we should include it. 14:29:31 any objections? (or counter-proposals)? 14:29:42 Kevin_Kofler: but then mayby data migration will work in time of 4.6 14:29:59 cwickert: You're confused. 14:30:02 as long as it's not a feature of it's own, we don't need to decide today 14:30:07 4.4 is neither e5 nor head. 14:30:08 Kevin_Kofler: ? 14:30:24 e5, 4.5 and trunk are all Akonadi-based. 14:30:25 Kevin_Kofler: I know 14:30:29 4.4 is the last non-Akonadi branch. 14:30:33 yes 14:30:46 The compatibility question here is about kdepim 4.4 and KDE 4.5 libs. 14:30:57 right, that's what I said 14:30:57 This should fall under library backwards compatibility. 14:31:01 i.e. of course it's compatible. 14:31:12 If not, it's a bug in kdelibs or kdepimlibs. 14:31:25 I don't think they will work on the 4.4 branch later in order to vierfy it still builds 14:31:27 The libs are expected to be compatible with older apps. 14:31:39 cwickert: it will build 14:31:53 kdelibs stay BC 14:32:25 anyway, we cannot complain about kdepim lagging behind all the rest of KDE and not providing testing. 14:32:28 Building 4.4 forever is not what I'm worried about. 14:32:48 Having the choice between being stuck on 4.4 forever or forcing a scary update on users is what I'm worried about. 14:33:08 4.5 leaves users with a straight upgrade path to newer Akonadi-based releases. 14:33:08 Kevin_Kofler: not forever, life doesn't end with F14 14:33:18 kdepim is now in a state where it can be tested, by october it will be in a state where it can be deployed to people. having it in F14 is a great chance of getting more testers 14:33:31 ltinkl: "forever" in the context of F14, i.e. until its EOL. 14:33:56 Plus, I'm worried that we'll get burned by other distros again as for K3b. 14:34:06 you can't tell it will be ready by October... 14:34:06 One of our core objectives is to be the first ones to ship new stuff. 14:34:29 k3b is different... and much smaller 14:34:50 ltinkl: Do you know what other distros are planning to do re kdepim? 14:35:00 kdepim is very complex and has a large source code base, lots of apps are interconnected, etc... 14:35:03 * rdieter ping'd winterz in #kontact for his opinion 14:35:18 there is no migration problem with k3b, so it's different 14:35:27 ltinkl: F14 will be supported until november 2011 which is KDE 4.7.something. you really think that kdepim 4.4 will still build then? 14:35:41 yes, that as well: k3b doesn't need to migrate (important!) data 14:36:14 cwickert: yes, against 4.5 14:36:17 Migration being troublesome is exactly why it's better to have 4.5 in F14. 14:36:22 Kevin_Kofler: k3b was small kde apps and is easy to update 14:36:37 ltinkl: this basically means we don't ship any more updates for F14, correct? 14:36:38 Because then there's no migration to worry about for users when going to 4.6+. 14:36:40 kdepim is core component in KDE 14:37:06 Kevin_Kofler: I'm not sure they finnish it before 4.6 14:37:13 I thought we have learned from the KDE 3 -> KDE 4 disaster in kdepim... 14:37:18 i think we need to vote for kdepim 14:37:26 it's not stuff for 4.5.x 14:37:27 this is a similar situation 14:37:29 please let start to vote 14:37:34 ltinkl: Disaster? F9 was a success! 14:37:42 than: I don't think it's time to vote now 14:37:43 We were the first ones to ship KDE 4 and we did it well. 14:37:51 we need clear message from upstream first 14:37:53 ltinkl: I don't think we have learned, learning IMHO means that we understand it needs wider testing 14:37:53 Kevin_Kofler: i did not see so 14:37:53 I'd propose we defer voting at least until we get feedback from upstream, on their opinion if it'll be shippable in time for f14 14:38:02 please... the first couple of kdepim releases were completely unusable... 14:38:03 rdieter: +1 14:38:03 it's disaster for me too 14:38:07 We should be bold like that again, not start getting wimpy like some other distros. 14:38:13 rdieter: +1 14:38:25 ltinkl: because nobody cared to test them... 14:38:31 rdieter: +1 14:38:36 anyway, lets delay the vote by one week 14:38:42 Wait a minuteā€¦ There's an upstream person here now. 14:38:46 can someone paste the last few lines of backlog to pastebin please? 14:38:48 cwickert: not true, look at KDE bugzilla first please 14:38:49 tmcguire: Hi! :-) 14:38:56 #agreed delay kdepim-4.5 decision/voting pending feedback from upstream 14:39:00 tmcguire: hello 14:39:10 tmcguire: Meetbot logs everything, let me dig up the running txt. 14:39:36 tmcguire: http://fpaste.org/3dTN/ 14:39:48 * ltinkl brb 14:39:52 OK, that works too. :-) 14:40:15 Re delaying, I think there's not much time to delay stuff. 14:40:32 This really needs to go in ASAP. 14:40:51 We need all the testing time we can get. 14:41:23 moving on then 14:41:27 #topic kde-4.4.5 updates status 14:41:30 Kevin_Kofler: if we don't declare it a feature of it's own, we don't need to vote today 14:41:53 cwickert: But we only have 2 weeks until feature freeze, and the release is coming close. 14:42:06 All the time we lose delaying is time we miss for testing. 14:42:09 I was a bonehead and missed including libmsn in the latest f14 push, otherwise, I think 4.4.5 is good 14:42:10 so next fedora version is released in october? 14:42:16 tmcguire: yes 14:42:19 rdieter: hi 14:42:41 tmcguire (and winterz) : http://fedoraproject.org/wiki/Releases/14/Schedule 14:42:44 the first possible chance for a kdepim4.5 would be early Sep 14:42:45 winterz: hi, 14:43:05 that's about when KDE SC 4.5.1 will be released 14:43:25 winterz: that's doable, I think, provided no more suprises or sipages. :) 14:43:30 but i'm doubtful 14:43:35 winterz, tmcguire: do you think that kdepim will be usable by october 26 without data loss? 14:43:55 Sep 7 is when things should in principle go in, but up to Oct 11 is possible. 14:43:57 My private opinion, which is known to be different from the opinion of others from the kdepim team, is that kdepim at that time will not be stable enough. 14:44:23 cwickert: Oct 11 please. We can't stuff in things in the last 2 weeks before release because rel-eng needs time to compose the spins. 14:44:24 tmcguire: by september or october? 14:44:47 But of course the Fedora schedule MIGHT slip. But we shouldn't rely on that. 14:44:51 tmcguire: what we need is clear statement from kdepim team... we will (have to) believe you :) 14:44:56 Kevin_Kofler: we can still ship a 0 day update, nobody will throw his mails into dhe version that is on the livecd 14:45:28 cwickert: sorry, that's not a good idea to use 0 day update for this 14:45:44 * smparrish agrees with jreznik 14:45:47 by september/october, kdepim will probably be useable, and migration will work in most cases, but I doubt it will be a joy for users. again, my private opinion. 14:45:51 jreznik: I have to admit that it's abusing the freeze 14:46:04 tmcguire: a joy in general, or compared to kdepim-4.4.x ? 14:46:09 winterz: what is your opinion? :) 14:46:26 rdieter: compared to kdepim 4.4.x 14:46:31 Well, if the version on the spin is almost final, shipping a 0-day (or even non-0-day) update to final looks fine to me. 14:46:32 ok 14:47:28 Of course, if it's something like KDE 3.96.0 (the KDE 4 prerelease which was current when F8 released), it'd be a different story. 14:47:41 (Yes, even I think it was right not to ship F8 with that. ;-) ) 14:47:55 But F9's 4.0.3 was fine, IMHO. 14:48:15 it sounds for me we should stay with kdepim-4.4 14:48:21 alright, I've heard enough I think, both winterz and tmcguire have reservations and doubts. than, +1 14:48:26 * ltinkl nods 14:48:32 yes. too bad 14:48:46 winterz, tmcguire : thanks for stopping by 14:49:09 ok 14:49:10 tmcguire, winterz: thanks for your infos 14:49:17 nothing stops the more adventurous souls from testing kdepim 4.5, either by compiling from source or from the kde-redhat repos 14:49:19 +1 to not ship in F14 8-( 14:49:20 * Kevin_Kofler votes -1 to than 14:49:32 (i.e. +1 for 4.5) 14:49:50 now, that doesn't mean we can't continue to build/test kdepim-4.5.x for testing and feedback (we can figure out the logistics of doing that later) 14:49:53 you could also provide packages for kdepim 4.5, not installed by default, for adventerous users 14:49:54 I just don't think it's wise to release something unstable onto the masses 14:49:54 We're going to let some other distro steal our show again like for K3b. 14:50:26 tmcguire: we can't ship anything that can't be parallel installable (without great pain and suffering anyway), is that possible? 14:50:27 than: +1 14:50:52 Kevin_Kofler: I would rather someone else deal with user headaches, especially on something as important as this 14:50:57 rdieter: Oh, it is not parallel installable, right. I thought installed it instead the other package. 14:50:58 Kevin_Kofler: it's not about show, we still have kde sf repo with hot stuff 14:51:02 And our users are going to be stuck with either an outdated kdepim or a painful migration for the whole life of F14. 14:51:43 rdieter: we could upload kdepim 4.5 to kde-redhat 14:51:44 rdieter: Well, we could put it into kde-unstable or something. 14:51:53 than, Kevin_Kofler : ye 14:51:54 yes 14:51:57 btw, I don't know how well Fedora packages work in general, but I'd really like to see Akonadi and GPG working out of the box. 14:52:05 We made a Readme.packagers file for that 14:52:11 smparrish: What happened to our "First" objective? 14:52:24 Fedora is not about letting other distros deal with the problems. 14:52:30 We're supposed to lead the innovation, not trail it. 14:52:43 Kevin_Kofler: first doesn't mean stupid/unwise, not listening to upstream 14:52:57 Kevin_Kofler: rawhide fullfills that I think more than enough :) 14:52:58 Kevin_Kofler: we should listen to upstream 14:53:05 rdieter: Undoubtedly some distro WILL ship this thing! 14:53:10 anyway, we're running real short on time, let's move along 14:53:12 And so we'll be late. 14:53:23 And everyone will complain that we're not shipping the new stuff Distro XYZ ships. 14:53:33 wrt kde-4.4.5, anyone of the opinion we should push this stable yet? or wait a bit more? 14:53:41 silly argument, sorry Kevin :) 14:53:44 * Kevin_Kofler misses the Fedora 9 times where we actually had the balls to ship current software. 14:53:53 we shouldn't do something just because others do it as well 14:53:59 (KDE 4.0 was only one of the scary things in F9, BTW.) 14:54:49 no opinions on kde-4.4.5 ? bueller? 14:54:51 ltinkl: But Rawhide doesn't have kdepim 4.5 yet because you (plural) just refused to put it in now targeting F14. 14:55:14 No objections to pushing KDE 4.4.5 to stable from me. 14:55:31 Kevin_Kofler: we can put it in rawhide as soon as KDE 4.5 gets released (and F14 branched) 14:55:48 Kevin_Kofler: +1, I want Fedora to be leading edge again, it's getting worse and worse 14:56:01 F14 will be branched on Jul 27 according to the schedule. 14:56:11 cwickert: Yeah. 14:56:27 cwickert: what prevents you from installing kdepim 4.5 from kde-redhat or even compiling from source? that IS bleeding edge approach 14:56:29 It's visible from the changes to update policies and many other things. 14:56:35 We're becoming more and more like another Ubuntu. 14:56:46 ltinkl: Ubuntu users can do that too. 14:57:09 We're losing our most distinctive feature if we stop being the first to ship new stuff. 14:57:18 Kevin_Kofler: if kdepim people says they make it, then no problem for me... but if we hear they can't make it, it's clear for me 14:57:27 People who want boring old stuff should use RHEL or CentOS. 14:57:34 Or Debian or Ubuntu or whatever. 14:57:36 But not Fedora. 14:57:36 shipping unfinished product killing users data - that's bad marketing 14:57:55 ltinkl: it's not about me but about my colleges that are doing the QA and desperately need more testers than me and the people here 14:58:06 shipping brand new Plasma desktop (even not ready) - it was OK for me and I still think it was a good idea 14:58:27 cwickert: Yeah, nobody tests stuff if nobody ships it. 14:58:39 cwickert: we'll get you testers, it just may not end up being the whole f14 userbase. 14:58:41 That's exactly why a bold Fedora is also valuable for upstream. 14:58:43 Kevin_Kofler: but you can't ask everyone to test it 14:59:17 alright, we're up for time today. 14:59:24 let's continue on in #fedora-kde 14:59:26 jreznik: But we can FORCE everyone to test it. :-) 14:59:29 any last words ? 14:59:37 * ltinkl is melting 14:59:39 delay by a week 14:59:59 cwickert: we can revisit the issue, sure, esp if there's any new information to consider 15:00:28 Re the next agenda topic, "Desktop validation testing expansion", I thought we already agreed to take that up on the ML? 15:00:40 I would give it a try if it would be in kde-redhat 15:00:45 And since QA now sent a mail (bad bad me for not doing it before they did), let's just discuss it there. 15:01:55 Kevin_Kofler: right, ml is fine 15:02:03 #endmeeting