16:09:45 #startmeeting 16:09:45 Meeting started Thu Jul 22 16:09:45 2010 UTC. The chair is llunak. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:09:45 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:09:55 agenda: 16:10:05 * repositories specific for KDE SC versions (e.g. 4.5.x) 16:10:12 * unstable repositories reorganization 16:10:23 * wiki move 16:10:31 * add individual bugowners for packages in KDE:Extra 16:10:38 * procedure/time frame to dissolve KDE:KDE4:Community repository 16:10:44 * old action items 16:10:49 * status report 16:10:52 * Q&A, misc 16:10:58 #topic old action items 16:11:14 * llunak will post the conclusion around repository reorganization to the list 16:11:21 llunak: that's from which wiki? 16:11:39 Beineri: http://en.opensuse.org/openSUSE:KDE_Meetings 16:12:13 llunak: that one has at least one more entry (playground repositories) 16:12:33 as for the AI, done in practice, the repos are already in place, written down also in http://old-en.opensuse.org/KDE/RepositoryRenaming 16:12:55 Beineri: those happen to be unstable too; I'm not removing the item second time 16:13:16 * All think about correct naming for KKUD and Playground 16:13:24 will be discussed as one topic 16:13:31 * javier announce and run a bug triage 16:13:37 announcement done, so in progress 16:13:52 AI: javier run a bug triage 16:14:00 * wstephenson see if rpmlint warnings can be hung on a lime tree for easy plucking 16:14:21 wstephenson: for somewhen later, right? do you want to keep this one? 16:14:25 i'm doing that as part of the next Junior Jobs boosters team sprint. 16:14:28 * rtyler waves to Kmetamorphosis 16:15:05 i am going to look at using KDE's krazy infrastructure to collect opensuse JJs 16:15:31 btw 16:15:45 hmm, nice idea 16:15:56 'krazy' is not an adjective, it's the name of a service that combines junior jobs, minor bugs, static code testing results 16:16:05 * llunak,wstephenson document how-to-maintain Extra 16:16:22 http://old-en.opensuse.org/KDE/Extra_Repository , http://old-en.opensuse.org/KDE/UpdatedApps_Repository 16:16:31 they haven't been moved yet 16:16:44 AI: llunak move wiki pages about maintaining Extra/UpdatedApps repos 16:16:50 not done here 16:17:11 * javier will create LiveCDs of unstable KDE 16:17:17 javier_: ? 16:17:41 yes 16:17:55 they are built 16:17:55 is that 'done' ? 16:18:04 well, there are some issues in the last build 16:18:08 ok 16:18:15 ie: it doesn't build 16:18:24 but small stuff? 16:18:28 i'm also working on a kde-four-live cd 16:18:29 yes 16:18:36 some dependencies 16:18:54 imho, kde-unstable-live looks good 16:18:59 at least the last build i tried 16:19:01 Is unstable set to 4.5 now? 16:19:09 good 16:19:10 i'm going to look at kde-unstable-live tonight, if i see any bad bits, i'll fix. 16:19:29 FL1SK: unstable is 4.6 16:19:35 right now there's an issue on obs 16:19:41 * mrdocs waves 16:19:43 4.5rc2 is in factory 16:19:54 ok, that's all for AIs 16:19:57 javier_: so kde-four-live = K:D:F, kde-unstable-live = KKUD? 16:19:58 first time in a meeting in a while 16:20:09 wstephenson: that's right 16:20:21 k-u-l is based on openSUSE Factory as well 16:20:29 #topic status report 16:20:41 where are the change docs for 4.6 16:20:42 k-f-l: openSUSE 11.3 + K:D:F 16:20:49 how do we know what's supposed to be different 16:21:03 FL1SK: too soon 16:21:07 FL1SK: read the release announcement in 6 months :-) 16:21:16 FL1SK: it's very much in flux now, no specific plans 16:21:21 4.5 was just branched from trunk and not yet released, there are barely any changes in trunk yet 16:21:30 ok 16:21:38 lots of mobile UI stuff for kdepim has been merged already, for meego :) 16:21:40 where are the plan guides 16:21:42 that's your sneak preview. 16:21:50 oh good 16:21:52 FL1SK: can we keep this for the 'misc' topic the next time please? 16:21:56 glad to see meego using it 16:22:09 ok llunak 16:22:18 status: 11.3 is out, looking good so far 16:22:29 KDE:Distro:Factory is at 4.5rcsomething 16:22:51 just a thought: maybe it would be nice to have an updated wiki that shows differences in each unstable;factory;stable 16:22:55 anybody notice the livecd starting with a broken folderview for the desktop? 16:22:56 4.4.93 i believe 16:23:13 sorry for the off topic 16:23:24 remur_030: no.. broken how? 16:23:24 remur_030: 11.3 livecd? 16:23:26 anything else worth mentioning? 16:23:28 the 11.3 kde i586 livecd that is 16:23:41 yeah, 'dbus crashed' 16:23:53 status: patched k3b, kipi-plugins, kdelibs, doing some akonadi fixes from trunk atm. 16:23:58 err from 1.4/4.5 16:24:51 what about froscon? 16:24:58 llunak: are you going? 16:25:00 ah yes, the KDE:Extra, KDE:UpdatedApps, KDE:Distro:Factory and KDE:Distro:Stable repos are up 16:25:11 but that's been already kind of mentioned during old AIs 16:25:19 still, big job, well done everybody 16:25:26 wstephenson: everybody is, as far as I understood 16:25:56 ok, next 16:26:04 ... what is 'new items' topic ? 16:26:07 so is froscon in Bonn convenient for any of the rest of the kde community to meet up with me and llunak? 16:26:11 jussasec.. 16:26:13 http://en.opensuse.org/openSUSE:Managing_KDE_meetings mentions it 16:27:36 maybe it just means "additional agenda items to the standard set" 16:28:04 well, I'll simply dump it, until somebody starts missing it 16:28:35 hmm, it was rabauke who's added it 16:28:38 anyway 16:28:43 wstephenson: just a sec for what? 16:28:51 froscon answers. 16:29:04 seeing if we can do something useful for opensuse-kde there 16:29:16 froscon is http://froscon.org, aug 21st-22nd 16:29:56 ok, think about it, it's still a month away 16:30:16 and I think I'll juggle the topics now, easy ones first 16:30:21 k 16:30:31 #topic procedure/time frame to dissolve KDE:KDE4:Community repository 16:30:55 every maintainer in the repo has been already notified, so I suggest we give them a week, then warn again it's going away, and good-bye 16:30:58 when is tittiacoke back? he has the best overview here... 16:31:01 somebody seeing a problem with that? 16:31:15 llunak: you really want to delete the rest? 16:31:23 will you delete it or just disable? 16:31:53 first thing i would do is disable build on :Community 16:32:05 no need to waste OBS power 16:32:12 Beineri: what else do you want to do with it? it's just useless rubbish if nobody has been bothered to move it to KDE:Extra 16:32:13 KDE:Extra only has 29 packages today, KDE:KDE4:Community 188 16:32:35 llunak: why is it useless rubbish? 16:32:45 because nobody cares about it? 16:32:57 llunak: the old opensuse releases are also moved to discontinued with barely anyone taking a peek 16:33:00 and it's not exported anymore in the community list in yast 16:33:01 llunak: someone cared to package it? 16:33:09 much of it is old stuff irrelevant for recent releases 16:33:14 and stopped caring afterwards 16:33:23 llunak: has there been newer releases? 16:33:25 like plasma theme air for 4.2.. systemloadviewer plasmoid .. 16:33:31 move what's interesting, the rest is not interesting by definition 16:33:56 but.. all titti's packages prolly still need moving 16:33:59 well then we should wait for more then one week, maybe disable in a week but not just drop it 16:34:07 and at least let tittiacoke have a say 16:34:18 I'll wait for tittiacoke then 16:35:05 It's not nice to delete someone's work whatever. 16:35:12 AI: llunak take care of removing KDE:KDE4:Community as appropriate 16:35:16 Beineri: they have been told 16:35:30 if it happens, it's because they don't care 16:35:56 Beineri: bitshuffler e-mailed all the maintainers directly I think 16:35:57 llunak: so did you ask if someone thinks a package is useful and wants to take over a package which hasn't been moved yet? 16:36:16 but of course they might all be away on holiday like titti 16:36:29 just because an initial maintainer left openSUSE doesn't mean that a package is not interesting (to others) 16:36:40 Beineri: so take over and move it 16:36:48 or anybody else 16:37:03 llunak: I can make a loop with copypc in one command shell line ;-) 16:37:11 I'll wait longer, that makes sense, but there's no point in keeping old rubbish around forever just because somebody might find it useful maybe perhaps one day 16:37:17 llunak: maybe we can do a 'packages for sale' style mail 16:37:33 llunak: ... if you're not seem to be interested trying to find a new maintainers. 16:38:29 if it builds keep it 16:38:30 so how about a post/blog that supposedly any now left package in KDE:KDE4:Community searches a new maintainer? 16:38:42 Beineri: do you want that as AI? 16:38:53 * Beineri doesn't blog anymore ;-) 16:39:04 nobody reads blogs anymore anyway 16:39:32 * rtyler weeps 16:39:55 llunak: perhaps the weekly news team could mention something? 16:39:59 how about a dummy maintainer account to symbolize a package searchs a maintainer? 16:40:08 bugowner: kde-maintainer-wanted 16:40:14 or alike 16:40:23 reminds me of someone's gitorious 'orphaned' project status suggestion... 16:40:49 well, on package level. not having orphaned packages in a separate project 16:41:22 Beineri: I don't think that'd do anything useful in practice 16:41:51 or by definitions that are all packages which have only inherited maintainers 16:42:14 actually that is another topic 16:42:48 can we just wrap up this one? I'll wait for titti to come back, post to opensuse-kde@ and eventually dump the repo 16:43:11 fine by me 16:43:39 remember to say "packages for sale" in the post to opensuse-kde :-) 16:43:44 with 'eventually' being when there's nobody caring anymore 16:43:58 #topic add individual bugowners for packages in KDE:Extra 16:44:11 the full description is: add individual bugowners for packages in KDE:Extra (I think this would be useful to get bugs for these packages addressed. Now one has to go through the changelog of a package to guess who is usually responsible for updating it to find the right assignee.) (I will probably not be able to attend the meeting. ctrippe) 16:44:46 sounds like a good rule for :Extra 16:44:51 which is like what was started above - having somebody directly reponsible for a package 16:45:03 although I think it'd be better to have a maintainer rather than bugowner 16:45:21 so explicit maintainers per pkg too? 16:45:40 maybe maintainer+bugowner set 16:45:54 i think that was actually meant anyway 16:45:59 I think it makes sense, right now it'd save us some trouble with KDE:KDE4:Community 16:47:08 so I'll add a rule that a package should have an explicit maintainer and bugreport owner set, if not, it's maintainer by the KDE team as a whole, with all consequences (dropping if we feel like it, etc.) 16:47:10 ok? 16:47:55 so if no one wants to maintain it gets dragged in anyways? 16:48:02 as long as it currently builds? 16:48:09 works... ;-) 16:48:19 there man be multiple maintainers 16:48:25 can 16:48:29 remur_030: that's up to the repo maintainers :) 16:48:39 generally, I think that's ok 16:49:03 llunak: well the project gurus should decide then, as the burden will propably lay upon then if something breaks... 16:49:07 "maintainer(s)" then 16:49:22 remur_030: yes 16:49:30 as in current community status =( 16:49:56 ok, anything else here? 16:50:21 AI: update KDE:Extra docs to suggest explicit package maintainers 16:50:50 actually, there may be a little problem if the package is maintained by somebody who's e.g. new and we don't trust them yet to get maintainership 16:51:05 i.e. only SRs 16:51:23 hmm ... they still can get a bugowner then, so no problem 16:51:25 ok 16:51:28 whose AI? 16:51:40 AI: llunak update KDE:Extra docs to suggest explicit package maintainers 16:51:41 (i can take it) 16:51:57 #topic wiki move 16:52:22 as you've probably noticed, the wiki has been replaced by a new instance, with the old one being at old-en.opensuse.org 16:52:39 and since it's a new one ,from scratch, many articles haven't been moved yet 16:52:52 so if you see something missing, feel free to move it 16:52:53 however 16:53:07 respect the law! 16:53:08 there are new rules e.g. for structure, so don't do that completely blindly 16:53:37 http://en.opensuse.org/Portal:Wiki has all the info and you should very preferably read all of it 16:54:29 the two most important changes: 16:54:31 1) it is not KDE/Meetings/Managing, but it's "Managing KDE meetings', i.e. normal speech, no subpages 16:54:57 contributor stuff is in the openSUSE: namespace, e.g. "openSUSE:KDE meetings" 16:55:11 the default namespace is only for "showing off", i.e. only for users who do not contribute at all 16:55:22 note that whining in bugzilla is considered contributing here too 16:55:43 questions on this? 16:56:07 what are the big things we lack in the new wiki 16:56:11 repo structure was done 16:56:53 all the meeting archives weren't moved afaik 16:56:57 I'm not sure, I expect these things will slowly turn up when needed 16:57:05 cb400f: I'll do that 16:57:10 the kde developers guide needs love, i'll do that. 16:57:15 * Beineri mumbles Configuration Management... 16:57:28 oh, btw, there's http://old-en.opensuse.org/Special:Export and http://en.opensuse.org/Special:Import , which can be quite useful 16:57:52 Beineri: what is configuration management? 16:58:15 shouldn't the kde page have bug reporting and contributing? 16:58:21 ... read, don't throw away all history/documentation why/how or not something was developed. old meetings minutes, ideas pages, ... 16:58:47 old-en.opensuse.org is supposed to stay 16:58:52 forever? 16:59:00 as far as I understood 16:59:14 or long enough, at least 16:59:14 * Beineri hasn't seen an announcement about that 16:59:30 initialZero: no, bugreporting is contributing 16:59:51 a link to openSUSE:KDE page can be there though 17:00:02 yeah 17:00:22 and it is there, at the bottom 17:00:38 llunak: what's the name of reporting already reported trouble, but closed with a sentence as this bug report is a mess, please open a new one :-) ? 17:00:43 ahh I expected an icon 17:00:49 initialZero: /KDE == "marketing" - /Portal:KDE == the interesting stuff :-) 17:01:10 tigerfoot: I don't know what you mean 17:01:14 where i find packages with 4.4.5 version of kde? 17:01:23 mad_soft: topic 17:01:36 ok! 17:01:39 mad_soft: meeting, please wait until the end.. 17:01:42 hmm? the bugbot doesn't keep the meeting topic?? 17:01:43 mad_soft you can ask after the meeting 17:01:51 llunak: it sets it to #topic 17:02:11 see bug 624321 (after the meeting of course) 17:02:14 openSUSE bug 624321 in openSUSE 11.3 (OpenOffice.org) "openoffice under kde unable to open smb:// uri files" [Major,New] https://bugzilla.novell.com/624321 17:02:22 that's lame 17:02:23 anyway 17:02:44 two topic remaining, 4.5 repo and unstable repos ... hmm, the dilema of which one to choose first ... 17:03:09 #topic unstable repositories reorganization 17:03:24 (naively hoping this one would be quicker and we should finish it anyway) 17:03:43 http://old-en.opensuse.org/KDE/RepositoryRenaming is the original page 17:03:50 http://old-en.opensuse.org/KDE/RepositoryRenaming2 is about today 17:04:01 we still need to do something about unstable software 17:04:24 as said in the page, there are two kinds of unstable KDE software, SC snapshots and any other KDE software 17:04:38 mixing them is bad (I think we agreed on this already the last time), so we need 2 repos 17:04:51 so for today there is deciding on the layout and on the names 17:05:10 the page has some options for the layout 17:05:21 some other options for the layout missing? 17:05:28 or other questions? 17:05:30 I think we need 3 repos :-) 17:05:36 cb400f: why? 17:05:37 kde:unstable:sc 17:05:42 kde:unstable:apps 17:05:45 kde:playground 17:05:59 what's the difference between the last 2? 17:06:03 what's the diff 17:06:05 and I wonder where an unstable user would get stable amarok or so 17:06:26 from updatedapps 17:06:44 built vs K:U:SC 17:06:57 but at certain times it might not be there, if the stable version is the latest 17:07:01 wstephenson: I don't think tha'ts generally needed 17:07:14 cb400f: it may not be where? 17:07:17 or Kde:extra 17:07:18 a stable release apps using features of a yet to be released SC? 17:07:20 in UpdatedApps 17:07:35 Beineri: same as kdepim44 built vs kde sc 4.5 17:07:52 cb400f: UpdatedApps has always (in theory) the latest stable version, so why shouldn't it be there? 17:07:53 anyway, generally a hypothetical problem, put it out of your mind 17:07:54 but I should prolly shut up.. I'd never use unstable anyway.. unstable users should speak for themselves 17:08:16 I use unstable 17:08:19 I just don't think alin, titti etc. want to use random snapshots of every single kde app 17:08:25 (non sc app) 17:08:30 and typically I never want stable 17:08:32 they won't 17:08:55 they'll just use SNAPSHOT and whatever else repo with apps they'll want 17:09:04 SNAPSHOT is just SC 17:09:25 ok, so other questions or proposals or can be just vote? 17:09:33 vote 17:10:03 before vote, let me ask : would somebody vote for 2) or 4) ? 17:10:42 can I get a link 17:10:50 http://old-en.opensuse.org/KDE/RepositoryRenaming2 17:11:22 why this capitalization? 17:11:27 because if not, we're just down to "do we group unstable repos together?" and "what do we name them?" 17:11:51 what capitalization? the one that says "with SNAPSHOT and PLAYGROUND used as name placeholder" ? 17:12:06 SNAPSHOT v Snapshot 17:12:18 caps indicate placeholder 17:12:26 we should have written $SNAPSHOT 17:12:42 makes more sense 17:12:59 ok, then let's run it just as the two questions: 17:13:05 do we group unstable repos together? 17:13:23 vote either as "together" or "separate toplevel" 17:13:32 now: 17:14:05 (that means the vote should be done now :) ) 17:14:26 together 17:14:26 tough choice 17:14:28 * Beineri demands a recount 17:14:46 can't we vote on the names first? ;-) 17:15:13 separate 17:15:30 you mean, directly vote on the final result? 17:15:58 if grouped together, some other option then KDE:Unstable:(something) ? 17:16:03 s/then/than/ 17:16:05 together 17:16:39 well my suggestion for 'together' would be KDE:Unstable:SC and KDE:Unstable:Extra 17:16:43 my vote for separate is conditioned on SNAPSHOT being replaced with something very scary :-) 17:16:58 which motivates them being together 17:17:16 let's try including names then, I hope it wouldn't get too complicated 17:17:34 wstephenson: Extra I find strange, because it has associations with KDE:Extra 17:17:44 ok, so throw around some options 17:17:52 KDE:Unstable:SC + KDE:Unstable:Playground 17:18:10 KDE:Snapshot + KDE:Playground 17:18:12 <_sc_> but -- doesn't "separate" mean someone could get a scary app by itself, where if 'together' they'd have to get a lot of scary stuff at once? 17:18:20 is playground still used elsewhere? 17:18:45 nope.. the other playgrounds would be removed 17:18:48 _sc_: no, 'separate' refers to the use or not of a 2nd level namespace 17:18:49 _sc_: that's just grouping at repo level, there are still two separate repos 17:18:56 'Unstable' in the suggestions above 17:19:15 why not just apps instead of playground 17:19:23 KDE:Unstable:SC + KDE:Unstable:Other 17:19:28 it already says unstable 17:19:47 ok, but it may not be just apps 17:19:49 other is good too 17:19:55 initialZero: same reasoning why we called KDE:Extra what it is 17:20:25 llunak: i used K:U:Extra above because it should have associations with KDE:Extra, why is that bad? 17:20:51 wstephenson: KDE:Extra does not have digikam, but K:U:Extra might - it'd also prevent saying just 'Extra' 17:21:18 * cb400f is sold on KDE:Unstable:SC + KDE:Unstable:Playground 17:21:19 so no more options? are people just tired from the heat outside :) ? last time there were so many options 17:21:46 not that I'm complaining, I'm just surprised 17:21:55 ok, so let me sum the options up and number them 17:22:11 1) KDE:Unstable:SC and KDE:Unstable:Extra 17:22:21 2) KDE:Unstable:SC + KDE:Unstable:Playground 17:22:28 3) KDE:Snapshot + KDE:Playground 17:22:38 4) KDE:Unstable:SC + KDE:Unstable:Other 17:23:12 more? otherwise I'm starting the vote 17:23:12 will unstable:extra be similar to extra 17:23:27 it would be extra++ 17:23:32 initialZero: I wouldn't say so, more like free for all 17:23:44 got it 17:23:46 since it could have apps which are in the distro (digikam, amarok, k3b) 17:24:07 then I vote 4 17:24:16 2 17:24:16 ok, vote now: 17:24:30 1 17:24:31 4, then 17:24:35 what bout KDE:Snapshot and KDE:Snapshot:Playground? 17:24:38 * _sc_ votes #4 17:24:53 4 17:25:19 javier_: that's what http://old-en.opensuse.org/KDE/RepositoryRenaming2 listed as one option, as a subrepo 17:25:36 you're voting bad :-) .. k:u:other doesn't make much sense when not used together with k:u:SC 17:26:24 people with stable, factory etc. could add "other".. and then it would look and sound weird 17:26:27 there's no KDE:Snapshot:Extra or KDE:Snapshot:Playground 17:26:35 cb400f: I think the name fits quite well - it's simply random unstable stuff 17:27:07 javier_: that's 2) in the page, you just swapped it around 17:27:25 ok 17:27:35 * javier_ votes for 1 17:28:01 1: 2 votes, 2: 1 vote, 4: 4 votes 17:28:21 somebody really unhappy with KDE:Unstable:SC + KDE:Unstable:Other? 17:28:27 <_sc_> dang -- that's with 74 nicks in the channel 17:28:31 dirkMobile: you specifically? 17:28:55 llunak: Extra or Playground sounds better than Other 17:29:16 Playground is only meaningful to the insiders 17:29:31 1 17:29:32 other is only meaningful if you know that it is "other than sc" 17:29:42 well, you probably won't want others to play with the repo anyway :) 17:29:43 yepp 17:30:03 Other sounds like the outcasts to me 17:30:07 lol 17:30:23 unstable:playground <- double warning, less risk of the wrong people messing with it :-) 17:30:23 there is no perfect naming 17:30:39 cb400f: +1 17:31:02 hmm, but that's actually a good point, we can name most repos on their own now, but 'Other' alone doesn't fit 17:31:04 but isn't unstgable a playground somehow 17:31:20 we have Extra, UpdatedApps, Factory, Stable, SC and Other 17:31:42 then extra if other so bad 17:31:49 llunak: and the version-specific repos might introduce more 17:32:01 What is the difference between Extra and UpdatedApps? 17:32:03 i could be persuaded to support Extra again 17:32:07 initialZero: that's not really an improvement if Extra is already taken :) 17:32:13 Kmetamorphosis: UpdatedApps is only apps, no libs 17:32:23 just updates to things that are already on distro releases 17:32:28 Kmetamorphosis: UA newer versions of stuff in the distro.. Extra, stuff that's not in the distro 17:32:34 llunak: if extra is taken, then playground? 17:32:39 but updatedapps makes it sound like they are better 17:33:02 updatedapps should be better most of the time 17:33:07 which is good because we don't want beginners attracted to other repos 17:33:51 unstable:snapshot:playground:testing then 17:34:08 ;-) 17:34:10 what about NotSC 17:34:12 ;) 17:34:48 NotSC could be everything except SC 17:34:49 actually, if I try to think logically about it, then KDE:Unstable:Playground makes the most sense - Playground alone is meaninful, it's under Unstable:, so those who do not get the meaning won't play with it, and it leaves us with separate names for every repo 17:35:06 llunak: +1 17:35:07 llunak: its good enough for me. 17:35:34 me too :-) 17:35:37 I used to get beat up on the playground 17:35:41 :( 17:35:49 that's an argument _for_ the name 17:35:51 and everybody voted for KDE:Unstable:SC + KDE:Unstable: 17:36:02 because that's what'll happen when you use the repo :-) 17:36:11 lol @ cb400f 17:36:17 good point 17:36:39 so are we voting on 17:36:44 ok, KDE:Unstable:SC + KDE:Unstable:Playground - "yes" or "no" ? 17:36:50 yes 17:36:53 yes 17:36:57 no 17:37:09 yes 17:37:36 yes 17:37:42 * llunak hopes he hasn't confused the hell out of everybody here by now 17:38:01 yes 17:38:09 yes 17:38:13 As a new openSUSE user, the word Playground scares me (as it should). 17:38:13 10 ... 9 ... 17:38:34 where's wstephenson 17:38:44 3 ... 2 ... 1 ... 0 ... boom :) 17:39:05 ok, congratulations, we've survived it 17:39:13 yeah! 17:39:16 * wstephenson just wants it to be over 17:39:20 and was getting food. 17:39:26 KDE:Unstable:SC + KDE:Unstable:Playground 17:39:30 now the next one 17:39:35 AI: llunak arrange renaming of unstable repos 17:39:46 #topic KDE SC version-specific repositories 17:40:12 the story is simple - users turn up again and again and want a repo with KDE SC 17:40:20 that sounds like having several stable repos 17:40:35 so kde:playground and k:u:s will be the same? 17:40:47 preferably the latest stable KDE SC, even if there's no important difference to KDE:Distro:Stable 17:41:01 ok 17:41:24 initialZero: kde:playground will dissappear and become kde:unstable:playground 17:41:26 and 50% of the time (roughly) KDE:Distro:Stable lags the latest SC by one release 17:41:40 this however doesn't fit the way we create repos for openSUSE 17:41:41 s/k:u:s/K:U:P 17:41:54 llunak: with suse patches? 17:42:19 dirkMobile: I think they don't give a damn about that ... version whores is probably a very good description here 17:42:38 KDE:VersionWhores:45, ...? 17:42:48 llunak: but i do 17:42:50 I'm offended 17:43:14 wstephenson: but not Kdf 17:43:16 I mean, KDE:Distro:Stable is probably a stabler choice than 17:43:49 llunak always 17:44:05 initialZero: sorry, I didn't make this up, and I think it actually describes the motivation quite well 17:44:52 Is this name describing those who want access to 4.5 once it is released, or only those who nitpick between 4.4.x or 4.5.x? 17:44:53 anyway, technically this is not a big deal - the repo can either be created only before K:D:Factory goes to another minor version, or it can just follow it 17:44:54 I'm a recovering version whore is all 17:45:19 aren't we all? 17:45:35 so the work is mainly doing something after K:D:Factory goes the version up 17:45:51 Kmetamorphosis: not sure what the difference is between those 2 variations. 17:45:54 where do testing packages go before updates to stable 17:46:00 so the two questions are: 1) do we want such a repository? 2) is there somebody to do the work? 17:46:50 What I was trying to get at was, I don't care if I'm using 4.4.5 over whatever the stable is, but I would like to be able to use 4.5 once it is released without having to deal with downgrading once factory updates. 17:46:56 a lot of people want it surely, prolly not many of them here 17:47:11 e.g. Cristian Morales Vega said he'd take care of such a repo, but only until K:D:Factory has the next version stable, which is about a month, and also only for 11.3 17:47:18 Beineri and reddwarf mentioned some interest in doing some work 17:47:25 I probably wouldn't want such a repo under KDE: 17:48:01 reddwarf: there? 17:48:30 cb400f: uhm, sure - i'm lacking work ;-) 17:48:33 Kmetamorphosis: it's about access to 4.5 once released 17:48:37 hmm ... I suggest we postpone this topic until next time, so that such people can be told more in advance to join here 17:49:07 and it's been going on for quite long today already 17:49:09 cb400f: I'm also interested in helping with that repo 17:49:41 llunak: we could also investigate the use of zypp services to reduce the work 17:49:49 AI: llunak lead discussion about KDE:45 repo on opensuse-kde list 17:49:56 wstephenson: how? 17:49:59 afair someone on the -gnome list said they are finally viable 17:50:05 zypp services? 17:50:23 maybe kde:temp:45 or so.. if it really comes to that 17:50:34 llunak,dirk: as far as I know they can be something like a symlink 17:50:46 since it's a recurring problem 17:51:04 dirkMobile: you build all KDE SC releases somewhere anyway, don't you? 17:51:16 ideally, there would be a repo for kde stables releases so that repo switching is not needed 17:51:16 that we could use to point eg "KDE:SC:45" to "KDE:Distro:Factory" until it becomes 4.6pre 17:51:39 wstephenson: can you find out details about that? 17:51:59 wouldn't it be mosre beneficial not to put 45 in factory 17:52:19 wstephendon: 17:52:26 if factory has a newer release than kde45 maybe we could copy the kde part into factory 17:52:37 or link it 17:52:40 does the build service support it? 17:52:59 llunak: sure, gimme an AI 17:53:20 initialZero: the next release isn't going to ship 4.5, i think that's why 17:53:25 openSUSE release 17:53:26 the zypp services are just a list of repositories 17:53:27 we should move this to -kde 17:53:33 AI: wstephenson investigate details about creating repository symlinks 17:53:40 dirkMobile: o-g may be in error, i'll find out 17:53:55 javier_ yes that's why factory should not have it 17:54:04 ok, let's wrap up 17:54:06 well zypp does supor 17:54:09 #topic Q&A, misc 17:54:22 item: KDE:KDE4:UNSTABLE:Desktop:kdepim45 17:54:31 initialZero: sorry, I understood that you understood the opposite 17:54:34 I wanted to say great job on 11.3! 17:54:48 support it however you need to create the list manually i think 17:54:51 when KKUD was 4.5pre, this repo contained kdepim 4.5 packages in kdepim4 etc 17:54:51 * javier_ has to upgrade his laptop to 11.3 17:55:16 somehow now KKUD:kdepim45 started containing 4.6 snapshots 17:55:29 dirkMobile: is one of your update scripts touching that repo too? 17:55:56 hmm, yes 17:55:58 i have reverted it to kdepim* 4.5 for akonadi port testing 17:56:14 i might have uploaded the wrong version there 17:56:17 which is a bit weird since it doesn't build vs KKUD now, but vs K:D:F 17:56:25 yeah 17:56:31 but temporary so roll with it 17:56:36 it's still unstable. 17:56:41 we should rename it 17:56:45 maybe it should move to k:u:p :-) 17:56:56 shouldn't this be done in K:D:Factory now? KKUD should be now just trunk, no? 17:57:30 llunak: no, putting kdepim45 in factory is like handing out grenades at a kindergarten 17:57:37 lol 17:57:53 so i'd like to keep it under KKUD where angels fear to tread 17:58:39 but an official beta release is coming up, or? 17:58:40 where it goes after the KKUD rename, ? 17:58:51 KUP 17:58:52 cb400f: yes, keeps getting postponed 17:58:59 something like kde:unstable:pim should make sense 17:59:03 KUP:kdepim45 subrepo? 17:59:46 KUP main repo.. that's what it's for.. unreleased stuff :-) 17:59:51 or simply unstable:extra 18:00:13 same as KUP 18:00:23 ok, i'm fine with that, if KUP can build vs KDF 18:00:35 it can 18:00:52 dirkMobile: can you take care of your script before the next K:U:SC update run? 18:01:28 that's a scary silence 18:01:33 i don't know if i dare to osc up 18:02:06 wstephenson: dirkMobile is just a script and you triggered an unimplemented path... 18:02:12 i just got the project to build through because kdepim45 depends on new stuff in kdepimlibs from 4.5 branch 18:02:44 i'll assume that's a yes 18:02:54 I have another * any other business item 18:02:59 11.4 features 18:03:12 i have a longish list of things we could do for 11.4 18:03:28 most of them are about hardware/platform integration 18:03:29 has the Ideas wiki page been moved? 18:03:37 and feature parity with other desktops/distri 18:03:38 is there a wiki for ideas 18:04:07 http://old-en.opensuse.org/KDE/Ideas/11.3 18:04:13 wstephenson: sure 18:04:23 its the place before things go to features.o.o 18:04:29 the antechamber if you like 18:04:33 dirkMobile: thanks. 18:04:56 so i'll make a 11.4 ideas page and put them up there for discussion, contemplation 18:05:04 i may also start a series of blogs about them 18:06:19 preview: kbluetooth testing, polkit-1-kde, kpackagekit/shaman, mobile broadband, working xrandr stuff, 18:06:31 the rest is on my whiteboard, i can't recall atm 18:07:13 some of that sounds more like upstream, but ok 18:07:16 is that it 18:07:53 llunak: well it may be integrating upstream stuff well into opensuse. 18:07:59 anything else to discuss? 18:08:03 btw, I would like to know if it's ok for the openSUSE/KDE team to have KDE:Open-PC 18:08:08 https://bugzilla.novell.com/show_bug.cgi?id=623979 18:08:11 openSUSE bug 623979 in openSUSE.org (OBS Request) "Kiwi-enabled project for Open-PC" [Normal,Needinfo] 18:08:45 if you want to add your comments, please do so in the bug report 18:08:46 javier_: was the 'why is this in KDE namespace?' question answered? 18:08:59 yes 18:09:15 one of the main features of the Open-PC is KDE 18:09:35 but its not only kde 18:09:43 right 18:10:00 but some people didn't like the idea of making the Open-PC namespace 18:10:14 so maybe it fits on KDE: 18:10:33 openSUSE:Derivative:Open-PC ? 18:10:41 I think it'd be better to have it as toplevel (there is other toplevel stuff, so why not) 18:10:50 wstephenson: that could be another option 18:11:20 ok 18:11:38 respin:open-pc? 18:11:50 then medical and edu should be there too 18:11:54 how does Edu-life do it? 18:12:03 hmm good question 18:12:31 and meego? 18:12:36 i think it's under education 18:13:01 yepp 18:13:02 https://build.opensuse.org/project/packages?project=Education 18:13:22 they are all at root 18:13:44 ok then 18:14:01 propose Open-PC as a root namespace, saying that it is not just KDE customisation 18:14:08 derivative would have been nice 18:14:19 then when we get too many root namespaces, propose openSUSE:Derivative 18:14:33 ok 18:14:53 remember the most important software part of Open-PC is KDE 18:15:13 but i don't mind if it's under namespace 18:15:19 *other 18:15:50 ok 18:15:52 i gtg 18:16:01 ok 18:16:05 thanks everyone for coming, and doing stuff 18:16:07 you can always have open-pc:kde 18:16:09 if there's nothing else, the meeting is over, thanks for taking part 18:16:12 javier_: good work on the bug triage btw 18:16:22 thanks 18:16:39 i finally talked with her :) 18:16:41 and thanks everyone for facing up to the renaming, i know it's fiddly and annoying 18:16:43 she was very helpful 18:16:43 (at least i think so) 18:17:06 I had a lot of fun! 18:17:09 thanks especially llunak :) 18:17:14 well that's the motto around here. 18:17:26 #endmeeting