Started at --> 06:00:09 PM jpr: Welcome to the weekly GNOME openSUSE meeting! FunkyPenguin: sorry to interupt jpr, but is it a pita to up grade to factory? ivanz: hola! jpr: where all your questions, concerns and ideas are meant to come! jpr: FunkyPenguin: Q&A :) *FunkyPenguin holds it for later jpr: just a reminder that next week will be our monthly time shifted meeting jpr: for captain_magnus 's sanity mw: too late for that, methinks ;) jpr: and for sreeves and btimothy to yawn jpr: repeatedly

Started at --> 06:01:51 PM captain_magnus: :-) jpr: mtgordon: would you care to update us on bug squashing? mtgordon: So... mtgordon: There was a bug day yesterday. mtgordon: Participation was somewhat light. mtgordon: We managed to reduce the count from 98 to 69, IIRC. mtgordon: Lost more bugs NEEDINFOed than previously, I think. mtgordon: I suspect we've gotten through much of the low-hanging fruit. jpr: do you have any thoughts on why it was light participation? mtgordon: Still, we've made good progress overall. srag is now known as srag|brb srag|brb: brb 5 mins jpr: (or does any one else attending for that matter) rodrigo: mtgordon: announcing it on the opensuse calendar might help rodrigo: mtgordon: it wasn't announced for yesterday mtgordon: rodrigo: I'm not sure how to do that. I'll look into it for the future. *btimothy admits hacking on packagekit yesterday (sorry) mtgordon: I'm wondering whether there was some burnout. mtgordon: It's not quite the novelty it once was. mw: i've always had more pressing things so far -- yesterday i was working on some secutiy updates mw: *security *captain_magnus is a sleep during bug squash mtgordon: So maybe it was just a day when lots of people got pulled away for other things? jpr: i think its important for us to all recognize this helps us immensely long term mtgordon: captain_magnus: I think you're off the hook. jpr: mtgordon: mono summit didn't help either for ivanz mtgordon: jpr: True jpr: Just a note: http://tinyurl.com/2aufcx *FunkyPenguin appologises for wanting goodies and not squishing pests jpr: shows the impact this process is having FunkyPenguin: i would definatel;y recommend trying to get it on the calendar rodrigo: yes jpr: getting rid of cruft allows better focus on significant problems btimothy: ...and more advance notice :) jpr: because you can find those problems more easily :-) mtgordon: jpr: Does that include firefox? I feel like I've closed a whole bunch of firefox bugs. jpr: mtgordon: no, thats just GNOME bugs jpr: we've had impact in other areas too of course srag|brb is now known as srag jpr: like FF and Xgl jpr: and srag 's team on evolution *srag reads up the logs jpr: mtgordon: is two weeks too frequent now, or...? mtgordon: I'm not sure what it's going to be like in two weeks. People might start going on holiday. mtgordon: Three weeks from now will be even worse, I suspect. srag: my son wants me again (brb 2 mins) srag is now known as srag|brb *btimothy thinks two weeks for everyone's participation is too frequent mtgordon: Four weeks from now we may as well skip. jpr: it would be nice to have one more before christmas jpr: and then maybe we should reduce to monthly? mtgordon: That's pretty much what I'm thinking. btimothy: that seems more reasonable jpr: +1 captain_magnus: Reducing to montly means closing lot's of bug in needinfo that got no answer... captain_magnus: +1 rodrigo: +1 mtgordon: Two weeks is considered sufficient. mtgordon: +1 mtgordon: We might have one person go (e.g. me) two weeks after the bug day to handle outstanding NEEDINFO. mtgordon: Doesn't really require a group effort. jpr: we also need to start reviewing the RESOLVED/LATER block at some point hpj: +1 monthly jpr: mtgordon: could we list ideas for future bug days somewhere? mtgordon: jpr: I can add a section to the bug day wiki on possible future topics. jpr: ok jpr: AI: mark add section on bug day possible future topics jpr: AI: mark to schedule bug day in 2 weeks jpr: AI: mark to move to monthly bug days after that jpr: mtgordon: anything else you'd like to add? srag|brb: I think two weeks is nice mtgordon: AI: mark to look into opensuse calendar srag|brb is now known as srag ivanz: I think 2 weeks is good enough ivanz: a month is too much tinme ivanz: *time ivanz: even if not everyone is available every 2 weeks it is still better to have at least some processing imho jpr: ivanz: i think at christmas at least mtgordon 's right and we should skip that zone jpr: we can reasses after that jpr: lets move on

Started at --> 06:15:12 PM jpr: federico1, rodrigo : rodrigo: I have just been categorizing more 11.0 bugs *captain_magnus points three fingers at jpr :-) *jpr wonders if federico1 is awak captain_magnus: Do we want to create more placeholder bugs for different component that receive a lot of them? federico1: eeek federico1: sorry captain_magnus: (or tracker bugs rather) federico1: was writing mail >( jpr: i'd also like to ask if its expected every bug will fall into a category jpr: and if not, are those WONTFIX or should_go_upstream or what cyberorg: we need close bug reason "UPSTREAMED" jpr: cyberorg: right now we have the keyword should_go_upstream with RESOLVED/LATER federico1: no, there are bugs which don't fall into categories... maybe enhancements, or those bugs that complain about a lot of abstract things and never get closed :) cyberorg: jpr, later means someone must relook when it is fixed upstream? jpr: cyberorg: yes captain_magnus: A bug should not be allowed to be marked shoud_go_upstream unless there is a pointer to an upstream bug federico1: jpr: we could mark some as enhancements and really see if they are gnome-usability or something else. Most should probably go upstream rodrigo: federico1: but I think we might need other categories, like gnome-enhancement rodrigo: federico1: gnome-security mtgordon: captain_magnus: We sometimes mark bugs should_go_upstream in bunches during bug review meetings. rodrigo: that's the 2 I've missed while categorizing jpr: captain_magnus: in the past we;ve tagged it like that but kept it open for processing jpr: and RESOLVED/LATER when actually upstreamed mtgordon: captain_magnus: Then, out of band, we check upstream, investigate the current code, etc. before filing upstream. hpj: how about a gnome-a-list category for things that PGO bloggers complain about? :) captain_magnus: Well, do we have the discipline to actually make it happen or is it only when someone finds 2 minutes of spare time federico1: rodrigo: hmmm, we could have those, but they'd duplicate info from the other fields rodrigo: federico1: yeah, right, so maybe we need to add those to the queries mtgordon: captain_magnus: I'll add it to the list of possible future bug day topics. jpr: captain_magnus: it should be part of bug days from time to time probably captain_magnus: Sounds good... jpr: hpj: hah - i like it mtgordon: hpj: homeopathy? ;-) srag is now known as srag|brb hpj: maybe call it something more neutral, like gnome-high-visibility or something hpj: mtgordon: haha jpr: federico1, rodrigo : how do we get to "done" on the tagging (realizing there will be on going work) rodrigo: I would call it done, at least for the "standard" we've set federico1: jpr: maybe we need to allocate a little time for tagging each day captain_magnus: In the project meeting there was talk about getting a wizard to frontend bugzilla (but still keep the old way of filing bugs)... Someone should try to get involved there... federico1: it's like scrubbing bathroom tiles while you shower - forget to do it and it starts getting gunky captain_magnus: That could help the tagging rodrigo: federico1: yes, that's a good idea federico1: or we could make a contest; who can tag the most bugs in a day :) rodrigo: yeah, with prizes :) captain_magnus: Dum de dum... jpr: so jpr: do we need to keep having bug plan as a topic? jpr: are we done for now? jpr: we are now committed to fixing all 11.0 showstoppers immediately rodrigo: I think we just need to include it in the bug squash days federico1: jpr: I think it's done for now - we just need to finish categorizing the bugs and fixing them in order rodrigo: once we're done for old bugs jpr: federico1: you and rodrigo seem to disagree on whether or not you're done :-) rodrigo: jpr: I agree we're done :) captain_magnus: Bring it up on planet if you are going to fight about it... rodrigo: I just say we need to include tagging as part of our squashing hpj: planet fight! rodrigo: :) mtgordon: I can put some instructions on the bug day pages. mtgordon: There's a link to the policy now, but I'm not sure who follows it. mw: don't bring it up in your blogs unless you're really going to slur each other, though jpr: AI: mtgordon to add link to bug policy to bug days jpr: AI: federico and rodrigo finishing tagging by next meeting and agree its done other than ongoing jpr: anything else for this? mtgordon: Two classes of "ongoing" captain_magnus: jpr: What about the wizard thing? mtgordon: New bugs, and bugs moved from older products. captain_magnus: Can we get an AI for that so that someone can get involved so that it benefits us as well jpr: mtgordon: yah, bthe the latter is dwindling right¿ jpr: do we have a volunteer on the wizard topic? captain_magnus: I can try but rather have someone on the inside... mtgordon: This would be in coordination with the Novell bugzilla team, I suppose. jpr: yes, presumably mtgordon: I'm not sure anyone here is really on the inside. captain_magnus: mtgordon: It was brought up in the project meeting and they will look into it jpr: how about federico1 monitors the progress on the project list? jpr: AI: federico monitors bugzilla wizard jpr: ok federico1: sure jpr: lets keep moving

Started at --> 06:35:42 PM *jpr watches btimothy pull out the whip btimothy: http://en.opensuse.org/GNOME/Tasks btimothy: first off, thanks to everyone who looked/reviewed their tasks before the mtg. :) btimothy: hpj: good work on http://en.opensuse.org/GNOME/Directory btimothy: okay, going by color this week btimothy: Red ... hpj: btimothy: thanks - it still needs some input from people, so add yourselves guys btimothy: no Riggwelter around today? :( btimothy: ai: btimothy poke riggwelter in mailing list jpr: perhaps he's too busy btimothy: jpr: can you clarify your red task abt. features and task list? jpr: and FunkyPenguin could step in and help mw: i think i could take over rigg's task next week jpr: yes sure jpr: originally i thought that i would list individual features on the task list btimothy: mw: awesome...can you update that item on the Tasks page? :) mw: or maybe tomorrow and saturday during p.d. jpr: like "pulseaudio" jpr: but now I'm thinking thats not necessary jpr: what do people think? jpr: (its covered in the 11.0 item in the developers section every week captain_magnus: I think it would grow out of control... And it looks as if the 11.0 ideas page is working quite nicely... rodrigo: I think it makes sense to have it on the tasks list rodrigo: just a link to the ideas page should work captain_magnus: rodrigo: See you on planet btimothy: i think if people want to manage (communicate) their specific plans on the Tasks page it would be good rodrigo: captain_magnus: yeah, sure :) btimothy: but wholesale create tasks for each of them may not be as effective btimothy: jpr: should we remove your task? captain_magnus: I guess if there is a deadline for one of the plans, it could be on Tasks jpr: yes, i think it can be cancelled btimothy: captain_magnus: +1 btimothy: moving on ... ? jpr: bug day was done jpr: boxes is now in progress *jpr updates btimothy: thank you jpr btimothy: mtgordon: please update your bug day task btimothy: (complete it) mtgordon: btimothy: Will do btimothy: (mark it completed) ;) btimothy: mw: sample spec file ... have you found a volunteer? btimothy: mw: for reviewing it? mw: btimothy: no. mw: anyone want to? btimothy: going once ... mw: http://en.opensuse.org/GNOME/Packaging/Simple_library_package <-- tell me what needs clarification, or where i tyoped btimothy: going twice ... (come on someone!  ;) ) captain_magnus: Is that for a n00b to review? cyberorg: send a sample on opensuse-packaging and you will have tons of feedback ;) btimothy: good idea mw: captain_magnus: sure. it's supposed to be understood by anyone captain_magnus: Ok, I'll have a look then btimothy: sold to captain_magnus ! cyberorg: buildservice ml is also good candidate btimothy: captain_magnus: please add your name as an assignee an update the ETA :) captain_magnus: btimothy: Off course :-) btimothy: okay...GREEN !!! btimothy: (on-track tasks) FunkyPenguin: sorry i was on a call, are my limited skills wanted for something? btimothy: federico1, rodrigo: please update the status & eta on your bug categorization :) btimothy: since we already talked abt. it rodrigo: ok btimothy: munkii not around ... btimothy: federico1, rodrigo: do you still need sample bugs from munkii ? rodrigo: yes captain_magnus: federico1: rodrigo: Is munkii's task still needed *captain_magnus types to slow rodrigo: he was going to send a11y bugs iirc btimothy: another AI for me to mail out to the mailing list (munkii) btimothy: okay ... btimothy: captain_magnus: it's my opinion that what we have on the GNOME/Tasks wiki page is pretty good (good job with the color organization). I also think having everyone review this weekly is a sufficient reminder. What do you think? I'd rather spend our time hacking on openSUSE directly instead of a tasking system. Any disagreements to drop this task? jpr: +1 for dropping captain_magnus: +1 for dropping btimothy: done federico1: btimothy: sure! btimothy: on to ORANGE (tasks with no ETA) federico1: arrr *federico1 kicks ichain srag is now known as srag|br1 mw: i don't think we should hack on a diff system, but if we find one ready to use elsewhere, we should revisit *btimothy pokes hpj, jpr, captain_magnus, mw, btimothy, rodrigo, federico1 to review orange tasks mw: editing mediawiki tables isn't fun btimothy: mw: +1 captain_magnus: After the meeting, can people stick around and discuss the tasks without ETA? It's been pretty static and we should do something about it. Prolly takes to long to do now... rodrigo: btimothy: no changes from me, PA thing in progress btimothy: what we need is ... jpr: still blocked on my two mw: no changes from my orange task rodrigo: btimothy: and nothing for the 0-tolerance thing, which I'll do later on btimothy: if you have a task in ORANGE that's "in progress" ... btimothy: please update so we at least have an idea what's already happened and what btimothy: what's left! :) jpr: and you probably have an idea then when it might be done :-) hpj: "where to keep openSUSE-specific code" is stalled btimothy: we don't need to go into in-depth review here in the mtg. btimothy: hpj: on what? srag|br1 is now known as srag hpj: on consensus jpr: hpj: thought we were going to try forge? btimothy: hpj: can we vote now in the mtg.? hpj: we haven't been able to decide on a solution, and nobody seems to want to use forge jpr: hpj: there is a general opensuse project on forge jpr: not sure if thats useful jpr: build service lives there mw: i want to go distributed jpr: ok jpr: lets take that offline from the meeting jpr: btimothy: anything else? hpj: yeah captain_magnus: I have more thing on the tasks page... I would like to add a "Mentor" column for tasks that belongs "Everyone" and "Tasks up for grabs"... btimothy: jpr: nope jpr: ooh jpr: +1 btimothy: captain_magnus: sounds good rodrigo: yes captain_magnus: It'd be easier for a "beginner" to digg in if they have someone to contact hpj: +1 mw: +1

Started at --> 06:52:10 PM jpr: we have several wiki questions this week jpr: Q: Could you compile Banshee with MTP support (for mp3/ogg audio players) and put it into GNOME Stable or Community repository (and include Banshee with MTP support in next openSUSE release) ? jpr: abock or abock_ : comments? *jpr is not sure what MTP support is captain_magnus: Mobile Transport Protocol? abock_: wow abock_: I am actually doing that *right* now rafa1: jpr: http://www.banshee-project.org/Guide/DAPs/MTP jpr: aha jpr: like PTP except for music abock_: yes abock_: it obsoletes NJB jpr: abock_: so you will check that into factory? abock_: Alan is maintaining MTP abock_: well, it's more complicated than just checking it in abock_: because we need libgphoto2 from svn abock_: so I am entertaining packaging libphoto2 for banshee privately abock_: from svn jpr: so A: yes, but in may take a couple of weeks abock_: so we can release an mtp plugin against the 0.13.2 release jpr: abock_: you know the gphoto maintainer works for novell right? :-) abock_: yes jpr: ok abock_: alan works with him abock_: (on gphoto/mtp stuff) jpr: A: yes, in the next couple of week you can expect banshee with MTP support in the build service jpr: Q: Default GNOME menu in openSUSE (not SLAB menu) looks horrible. Just take a look at GNOME menu in Fedora and you will understand why I'm complaining about it. Menu in openSUSE has double entries (like Evolution in "Office" section and in "Internet" section or two Banshee entries in "Multimedia" section) and mixed icons from GNOME and KDE. It looks inconsistent and not "professional" while "look&feel" is very im jpr: portant part of the distribution. jpr: thats not really a question :-) rodrigo: yes, I agree, it looks iglier than upstream rodrigo: uglier abock_: yeep abock_: much abock_: we have poor organization and maintenance of desktop files jpr: we have a shared menu system with kde i think jpr: sreeves: yes? abock_: (why?!) abock_: yeah, it's the KDE entries that really ugly it up too abock_: not tango, etc. abock_: we have a ton of entries that make no sense, and are hideous abock_: also abock_: my gtkrc patch helps the slab a lot I think abock_: in terms of the theme sreeves: those should be tagged in the .desktop files as onlyshowin *mtgordon nods abock_: pulse audio needs some serious .desktop love jpr: we actually have good support for cleaning up .desktop files with %suse_update_desktop_file rodrigo: yeah :) jpr: if you use its options jpr: A: yes, the menus should be reviewed for 11.0 jpr: AI: jpr to file bug to review menus for 11.0 abock_: s/should/will/ abock_: :) captain_magnus: jpr: No need to bring my Q up... Already discussed jpr: Q: Make Tango, not Industrial, icons as default for GNOME. jpr: captain_magnus: ok jpr: A: The art team wants to keep using industrial (they made tango :-) ) and are currently in the process of updating industrial which I believe uses a lot of tango jpr: open for questions from the floor! jpr: FunkyPenguin: i believe you had one earlier? abock_: I had some *abock_ loads industrial to remember why captain_magnus: Q: Why am I running out of coffee beans every time we have a meeting? abock_: well, for one, I really have been liking the new upstream/gnome icon theme, also all tango abock_: regarding icons/themes mw: A: go to Coles abock_: I really would like to see us using DMZ-AA as the cursor captain_magnus: :-) abock_: or at a min, DMZ federico1: abock_: YES rafa1: jpr: I have question about apparmour applet in gnome, could it be more sophisticated like similar tool for selinux in fedora? federico1: white cursors suck abock_: the Industrial pointer is just so outdated abock_: and white cursors *really* suck abock_: I found out immediately when I switched to DMZ-AA abock_: which is absolutely awesome abock_: I use the medium size cursor abock_: which has helped me so much jpr: rafa1: are you refering to the one available in yast? captain_magnus: rafa1: It's AppArmor... abock_: but DMZ-AA looks good at all sizes federico1: see, abock_ is a man of taste rafa1: jpr: yes abock_: haha rafa1: jpr: nope, sorry rafa1: jpr: im refering to applet FunkyPenguin: er sorry, chaos atmn here rafa1: version 0.8 jpr: rafa1: i'm afraid I don't actually know the applet rafa1: ah, ok jpr: does anyone else? jpr: rafa1: what package is it in jpr: ? jpr: abock_: not really a quesiton, more of a request :-) jpr: rafa1: we'll figure it out post meeting :-) abock_: well abock_: Icons+Pointers are the same abock_: same group abock_: so switching the industrial cursor is relevant to this abock_: (to the question) rafa1: jpr: apparmorapplet-gnome-0.8-28 jpr: ok jpr: FINAL CALL FOR QUESTIONS

Started at --> 07-05-41 PM jpr: jimmac is ill and can't lead this to day jpr: but he'd like to get the theme packages broken up a little better jpr: so its easier to update the art mw: sounds good jpr: (and makes more sense namespace wise) jpr: we discussed something like jpr: theme-opensuse-gnome-gilouche, theme-opensuse-gnome-gilouche-gtk, theme-opensuse-gnome-gilouche-metacity jpr: etc jpr: would help the space on live CD's too jpr: theme-opensuse-icons-tango jpr: i guess too captain_magnus: Sounds great jpr: not sure how the namespacing would work mw: lots of time to try different things before 11.0 jpr: mw: AI for you to discuss with jimmac :-) mw: ok hpj: not lots :/

Started at --> 07:09:11 PM jpr: hpj: take it away hpj: ok folks, this meeting is running late, so let's focus and get it over with. hpj: first off, SUSErocks and I have been trying to get the ball rolling on a11y features hpj: we've been probing the yast installer team/lists to see what can be done on that front hpj: it's tentative still hpj: and i've started making some noise on the gnome-usability list hpj: the first things is a wm features that would make life a lot easier for people with big fonts hpj: scrollin partially off-screen windows more easily hpj: (many users don't know about the alt+drag feature) hpj: i think that's it for me hpj: federico: intlclock? federico1: hpj: I'm still merging the code into the main clock applet hpj: federico1: intlclock? federico1: hpj: should be done relatively soon; I hope to have a mildly working version next week hpj: do you have a tentative deadline for the intlclock work? hpj: ok federico1: btw - setting your timezone with PolicyKit is really really nice hpj: can you say with any certainty when you'll be "all done"? federico1: we've been wanting this sort of machinery since the start of gnome federico1: hpj: put in the end of next week for me DimStar: apropos Timezones... any plan to have the time zones settable by DHCP? hpj: great mw: is that something dhcp is capable of? hpj: DimStar: can we fo that in developers Q&A? DimStar: (more general than gnome, I know) hpj: s/fo/do/ DimStar: sure DimStar: sorry hpj: btimothy/sreeves: packagekit? btimothy: well, we are working on building a zypp backend for packagekit btimothy: and ... btimothy: simple package install is working btimothy: but there's still a lot of work to do btimothy: to get it more robust sreeves: you need factory and a couple little tweaks to try it btimothy: libzypp isn't really the easiest to code to ... so we're working through a bunch of that to implement more of the methods for the zypp backend btimothy: we've gotten some good acknowledgement from the zypp team hpj: do you have a feeling for how much there's left to do? btimothy: they're working on a better API for apps, but no ETA as far as i can tell hpj: time-wise? btimothy: hpj: all depends on how far we want to take it btimothy: the feeling right now is ... sreeves: to get complete backend coverage is still a ways out btimothy: that we go ahead and use libzypp like it is to build out the most common features needed btimothy: we == sreeves and me btimothy: and encourage more participation from the zypp team btimothy: it could easily consume 2 - 3 weeks btimothy: what are your thoughts? worth it? hpj: ok, so we should look for something towards christmas time then? jpr: +1 for worth it hpj: +1 for worth it mw: hope to see it by festivus jpr: if we can get something in to factory that people will test that would be huge captain_magnus: +1 if it will be bug free :-) btimothy: thoenig was going to look at getting the packages building in 10.3 (sreeves and i will assist, but not worry too much abt. that) jpr: (assuming its not super buggy, some bugs are fine) btimothy: sreeves and i chatted yesterday and ... hopefully in the next week, we want to at least get packagekit with a somewhat working zypp backend committed to factory btimothy: ...if they'll take it in btimothy: we just don't want to push it out there too soon btimothy: ideally, we want to have the update icon working as well sreeves: update applet btimothy: btw, packagekit isn't entirely bugfree yet ... we've helped discover/fix a few bugs upstream btimothy: overall though, it looks very promising hpj: i think it'd be better to get it in too early than too late btimothy: sreeves: anything to say abt. timeframe? sreeves: I agree - plan is a fairly functional checkin to factory next week hpj: sweet sreeves: several weeks for complete coverage btimothy: factory checkin likely near end of next week sreeves: and then we could start things like speed optimizations - which are needed hpj: ok, sounds good hpj: rodrigo: PulseAudio update? captain_magnus: btimothy: sreeves: What about performance... Is it any faster/slower that what we have today? rodrigo: pulseaudio is mainly working for most people, but failing for others like FunkyPenguin :( btimothy: captain_magnus: well, we're not going to force a repo refresh on every operation, for one hpj: captain_magnus: can you hold it for Q/A? we're almost done here rodrigo: we are looking for better ways of debugging, so asked lennart about it, waiting for his answer rodrigo: and apart from that, I sent mail to opensuse-factory about whole distro plans, and there wasn't much interest in it rodrigo: kde would not change to PA in the short term (no plans for long term neither) hpj: that's a shame *jpr is personally for much better PnP audio support jpr: it will give us the ability to automute music when a voip call comes in and other cool stuff rodrigo: but well, I think we can go ahead with the GNOME side, and if it works better, everyone will adopt it :) hpj: so you're mostly done then, apart from some yet unknown debugging quantity? rodrigo: yes rodrigo: cyberorg, anything to add? cyberorg: rodrigo, nope, you covered it, i'll take a look at updating packages to latest svn checkout later this week and cleaning the spec cyberorg: i'll be adding it to next kiwi-ltsp release rodrigo: cool hpj: ok hpj: captain_magnus: main-menu update? captain_magnus: Got several ideas on how to improve performance but nothing code wise yet... Sort of waiting to see what's going on with the next version of libslab as well hpj: ok hpj: any updates i missed? captain_magnus: There's to main areas that needs to improve.. One is in libslab and one is in gnome-menus captain_magnus: s/to/two jpr: ok, next up

Started at --> 07-28-36 PM jpr: mw: two minute update? mw: Packaging day is tomorrow *sreeves looking forward to it rodrigo: woohoo! mw: nothing new to add, really mw: a few people have asked for me to describe my setup, so i'll write that up before tomorrow morning mw: i think that's it DimStar: very bad.. I'll only be able to join quiet late in the day tomorrow.. like at 7 CET jpr: oops mw: oh, i'll be unavailable for an hour in the afternoon (my time) during a meeting :/ jpr: DimStar: its saturday too! DimStar: jpr: ah.. then I have more time :-)

Started at --> 07:30:53 PM jpr: questions on the development? hpj: DimStar/captain_magnus: Sorry for cutting you off earlier. You can go ahead now :) captain_magnus: btimothy: Anything else to add on the performance bits? captain_magnus: hpj: Totally ok... It was your show :-) btimothy: sreeves: did you have more in mind re: performance? DimStar: no problem hpj... jpr: DimStar: what was the question again? btimothy: if we had all the time in the world, i think it'd be nice to get the yum backend working and compare times DimStar: I was curious if openSUSE will soon be able to support time zone adjustments by DHCP (as per RFC 4833). cyberorg: how about weekly opensuse-gnome-devel status update like the OBS guys do? btimothy: yum vs. zypp ... but that's essentially gonna be a problem the libzypp team has to solve sreeves: I would like to look into cutting down /caching init and query calls into libzypp jpr: DimStar: well, this policykit stuff would certainly help, it would be easy to set it if NM added support for that jpr: tambet: ^^ jpr: DimStar: also there will probably be at some point work in NM to detect location and broadcast the information captain_magnus: cyberorg: Isn't that sort of what we're doing here? jpr: for automatic changes for other stuff as well btimothy: captain_magnus, sreeves: yeah, querying a package, we shouldn't have to load all the resolvables into a "pool" and iterate through them just to get simple information about a package (it's REALLY slow) jpr: cyberorg: thats not a bad idea cyberorg: captain_magnus, yes, posting on ML helps to know what all the other gnome devels are doing and those not attending here are updated DimStar: jpr: so you think I should try bringing my question to the NM-ML? captain_magnus: cyberorg: Ahh,, ML... Yeah, +1 for that jpr: DimStar: thats probably a good place to start cyberorg: it will also help us discuss stuff about what devs that are not part of these meetings DimStar: jpr: I will do so... hopefully we get some results soon then. jpr: rodrigo: can you add a status of the development to your mails? rodrigo: yes jpr: AI: rodrigo to do a dev summary for mails jpr: anything else? btimothy: has anyone else tried out the email notification on the wiki? *btimothy thinks it stinks (comparing with what you get from live.gnome.org's wiki) rodrigo: I haven't got any notification rodrigo: and I think I am subscribed *rodrigo re-checks btimothy: i finally got a notification and ... if you don't visit a page again after getting a notification, you don't get notified jpr: lets take that offline for the rest jpr: THANK YOU ALL jpr: ANOTHER GREAT MEETING! Meeting ended at --> 07:39:00 PM