Started at --> 06:59:28 PM jpr: Welcome to the openSUSE GNOME Team Meeting! jpr: today we'll be continuing our series of theme meetings with Evolution jpr: (Networking, Bluetooth being past topics) jpr: and we have some of the evolution team with us here today

Started at --> 07:00:43 PM srag: Hello every one jpr: srag: why don't you start off with a brief summary of who you are and who is here with you :-) chen: hi srag psankar: hi all. I am half-slept. So excuse if I make any mistake ;) lakhil: hello to every one hpj: thanks for coming, guys suseROCKS: High-Fives to the Evolution Team! srag: I'm the maintainer of Evolution and I work for Novell and been there for almost 6.5 years schooms: suseROCKS: high-five !! srag: I have abharath, psankar lakhil kandepu chen jony schooms from my team srag: except ashish from my team rest of us are here kandepu: hi all ..:) federico1: hi guys! jony: hello .. abharath: hello all jpr: great jpr: srag: why don't you jump in and give us an overview of evolution in 10.3 and the future for 11.0 :-) srag: We release Evolution 2.12 with GNOME 2.20 which was with 10.3 srag: sure jpr srag: We focused on some of the important things like SPAM, New mail notifications and more importantly stability of Evolution srag: We are now working on Evolution 2.22 for GNOME 2.22 which will be with OpenSUSE 11.0 srag: Yes, we synced Evolution version with GNOME srag: We have already made 3 dot releases of Evolution in the GNOME cycle (2.21.3 is out and 2.21.4 is on Monday) srag: We have added some nice things like srag: Google Calendar Support ( chen would speak more about it) srag: External editor support (You can use VI/Emacs for message composing) srag: and importantly crash-detection srag: where in if Evolution previously crashed, it gives a option to hide preview panes (if the last read mail caused it to crash) srag: so that users wont have situations like can't start it at all srag: With this we are also working on lot of new things and fixing loooots of bugs psankar: srag, you missed the most important thing Exchange 2007 srag: By 2.21.4/5 Evolution should feature new way of Error reporting (Non-intrusive error reporting, with logging support) srag: psankar, I'm coming to that * psankar keeps quiet srag: http://www.go-evolution.org/NonIntrusiveError has the plans for it srag: around the same time, we also expect configurable labels/email tagging to be there srag: we expect the basic support to be there for 2.22 and We would improve tagging hugely during the next releases srag: We have a hacker from redhat working on bonobo less composer with new look and feel srag: http://www.go-evolution.org/New_Composer has the informations on that srag: and the most important things is that srag: there is lot of effort being spent on MAPI based Exchange connector srag: it is developed based on OpenChange's libmapi srag: It may not hit the trunk/2.22 but we hope that a build service would be available for all the 2.22 users to install and use srag: it should fix all the performance/stability issues with Exchange and most importantly it would work with Exchange 2007 servers also srag: so one connector that can work with Exchange 5.5, 2000, 2003 and 2007 srag: I'm sure that it may take a release or so for it to stabilize or to have a feature parity with the current connector, but we hope that it should be the future for Exchange connectivity srag: jony, would be speaking more about it srag: In the stability front, srag: we are almost fixing/commiting 20-30 bugs per week and lots of crashers being addressed srag: and we are planning to have a "Stacktrace" hackfest during Jan srag: where we plan to involve everybody to fix ONLY crashers on that day srag: if it works out well, we may have one more as well for 2.22 srag: but these are our plans for 2.22 srag: For the future srag: we are thinking of Evolution Splitting to individual apps (lots of things being worked out) srag: and may feature lots of protocol improvements (IMAP and Pop) srag: chen, ? chen: w.r.t calendar front chen: As srag mentioned, we would have Google calendar write support which is one of the big features done during googe soc. program, the basic support for creating/modifying/deleting appointments is already in. chen: currently we are working on missing features in it such as, chen: recurrence, sending meeting requests, importing calendars, viewing multiple folders etc. which should be in within the end of this month chen: Some usability enhancements/bug fixes which are in progress are, chen: Showing additional timezones in the calendar view (http://brokenclay.org/images/calendar-big.png/) and the favourite timezones from clock applet chen: Using send/receive to refresh calendars srag: chen, done? psankar ? chen: Reloading the calendars automatically when EDS restarts without poping up much dialogs. The error messages would be displayed in status bar chen: srag: a last one to be updated.. srag: sure chen: We also have plans for reducing the EDS memory and improve the cache performance. Not sure whether it would be done in this release though... chen: and with more bug fixes .... :) psankar: Thank you chen/ srag . I am one of the initial authors of Evo-GroupWise mailer and I maintain EPlugins federico1: chen: do you have a breakdown of EDS's memory consumption? chen: If anyone has any critcal issues which needs to addressed, please ping later :) psankar: For 2.22 and beyond, I will be focussing on reducing the horrendous size of evo-prefs dialog which is annoying a lot of users on low resolution psankar: and I will be working on splitting ui into seperate apps. chen: federico1: we have identified some areas where we can reduce the memory, mainly related with cache and live queries stored srag: federico1, I think, chen knows the memory hogs in the code. I dont think we have a valgrind or any other report for that munki1: chen, any chance we will see RSS feeds in evo soon? chen: we have a plan to move to a DB based cache so that we need to keep the cache in memory always munki1: sorry if this has been addressed before, i just came in psankar: munki1, you can already see it lemme url you jpr: munki1: wait for Q&A please munki1: jpr: sorry, i didn't know there's one =) psankar: munki1, http://www.go-evolution.org/EPlugin munki1: psankar: thanks! srag: psankar, anything more? srag: jony, ? jony: hi all .. i'm currently working on MAPI provider for exchange. psankar: With 2.22 you can confiugre plugins within plugin-manager so that plugins wont abuse the general preferences federico1: chen: those "keep everything in memory" caches scare me, as they don't have a clear eviction policy federico1: chen: what if you simply evict live queries that haven't been used for some time? or just keep the latest N ones? hpj: i think chen's sentence was missing a "don't" psankar: UAM is some thing we are looking forward to doing - http://www.go-evolution.org/Unified_Account_Management chen: federico1: ah yeah "dont" :) federico1: chen: ah, ok hpj: still needs an eviction policy though :) srag: psankar, done? psankar: srag, yup

Started at --> 07:29:17 PM jpr: great Iznogood: evolutions support for NNTP is, well lets face it, lacking in ease of use, any plans for further development? I dont want to be able to download binaries, but adding "groups" with evo as of now is a pain + I'm aware of the rss plugin for evo, any plans for making it a standard/included by default? Oh and what about icon for the tray, meaning being able to minimize to tray (yes yes, there is a plugin that does that too, but this is also a federico1: chen: please mail me if you want some ideas :) there were some plans to reduce the amount of data kept in e-d-s when we wrote the calendar a long time ago, but never got around to implementing jpr: open it up for questions chen: federico1: sure! munki1: psankar: i know about the plugin, i was hopping for something more integrated, like in KDE's Korgnizer federico1: chen: srini and I talked about the alarm daemon in GUADEC a while ago, too suseROCKS: As srag and I briefly discussed in an email exchange recently, there's scant community-created plugins for Evo. I read psankar's blog with interest and his efforts to improve on the framework. Where do you see things happening 6 months to a year from now for increased community plugin contributions/development? chen: federico1: cool, will catch up with srini offline :) federico1: question: any plans to integrate Tinymail's memory-saving patches into camel? the mmap()ed mail summaries are really nice psankar: suseROCKS, yes. you are true. Teh community participation is a little less when comapred with othe rprojects like Firefox. Once we spend enough time on the framework, I guess this can eb improved. Also, srag: suseROCKS, psankar promised a 7 steps (clicks? ) for a EPlugin guide for users to easily write plugins jpr: srag: Iznogood has an question that was missed psankar: suseROCKS, I had some *grand* plans of writign a plugin through 7-clicks in a wizard which will auto-generate some skeleton code for you and chen: federico1: I will email you on the areas which we have noted and the solution we were thinking about and get more suggestions from you :) srag: federico1, mmaped patches has a list of mentioned problems, which were discussed before chen: *areas to reduce memory in EDS srag: federico1, but there are some other plans there dliang: At present, we can read mails in list view, is there any plan to read dliang: mails in icon view, just like Nautilus? psankar: suseROCKS, point you to relevant docs. but plugins are still in a little less priority comapred with the core providers work and hence the delay in it. I hope plugins will improve mroe soon if not late srag: Iznogood, missed you. sorry Iznogood: np federico1: dliang: you have some pretty cool patches for evo :) suseROCKS: psankar I agree that core development is important, but I also think plugins is what spurs increased community partiticipation. srag: Iznogood, currently there is no strong effort spent on NNTP, but definitely we aren't ignoring it though. psankar: Iznogood, that minimize to tray is considered a panel abuse and ehcne didnt make it as part of default list federico1: srag: ok - I hope camel can shrink its memory consumption as much as those patches allowed it to srag: Iznogood, the rss plugin lacks a few things, which cooly (author) is working on psankar: Iznogood, but we will see if we can ship it without enabling ti by default srag: if that is done, it would be surely * federico1 watches his 600 MB evo process psankar: suseROCKS, accepted. eys srag: federico1, sure. that is our plan for sure. suseROCKS: one of you mentioned low-resolution enhancements/fixes. That includes a11y users, if there is anything I can offer to help out with testing, let me know. psankar: suseROCKS, Sure. Will do Iznogood: psankar: really, I find it the best thing since sliced bread, since I always run evo anyway srag: Iznogood, about the plugin for minimize to tray, It may be the part of the trunk, but definitely made available as a external plugin to users who want it (It is ia HIG violation :) hpj: federico1: peanuts! mine is 900MB psankar: Iznogood, :) psankar: federico1, sorry I missed the discussion. which camel patch you are referring to ? suseROCKS: Simple end-user question here. I have multiple imap accts. When I get notify saying "You have 1 message in INBOX" I can't tell which mailbox it is for. Is there a way to alias inbox folders? srag: hpj, federico1: there are plans of db based summary, so that what you see is what is there in memory. (also the Disk summary branch) federico1: psankar: tinymail's version of camel uses a slightly different format for mail summaries so you can mmap() them and save a ton of memory, instead of exploding the summaries into data structures srag: suseROCKS, if there isn't bug already, file one and CC me :) It can say the account/folder-to-path srag: should be a easy fix federico1: srag: ooooh, is that getting resurrected? that's a pretty major piece of work suseROCKS: srag great... will do srag: federico1, there of lots about it psankar: federico1, but if we just pass the memory requirement from memeory to mmap is it not liek jsut blinding top, but the consumption is still high ? May be I am missing something srag: s/lots/lots of thought srag: federico1, we aren't planning to take it at one, but planning to take small things and grow it jpr: ok, lets wrap up the questions lakhil: suseROCKS, feel free to add you comments here http://bugzilla.gnome.org/show_bug.cgi?id=496380 ( hope it addresses same issue) bugbot: Gnome bug 496380 in Evolution (Miscellaneous) "Mail notification applet does not give useful information" [Normal,New] jpr: any more questions from the cheap seats? captain_magnus: gmail and imap... If you have "search folders" in gmail, they will show up as folders in evo. Evo will then download not only the folder but the "All Mail" jpr: the heavy technical discussion can continue after the meeting :-) captain_magnus: folder as well. I've tried to "unsubscribe" to the "All Mail" but it always keeps coming back. So it ends up downloading duplicate emails all the time suseROCKS: Thanks lakhil.... initial view of it looks like it is similar to what I was thinking yup lakhil: suseROCKS, welcome :) captain_magnus: Any one looking at fixing that? federico1: psankar: you avoid all the overhead of exploding things into structs. Strings don't require an extra pointer, flags remain packed instead of living in separate int-sized fields, etc. srag: captain_magnus, gotta bug for this? CC me if you have filed one already captain_magnus: srag: Not sure if I did file one but will do otherwise srag: sure and CC me there :) psankar: federico1, okay. I guess I dont understand fully. I will contact you offlien for knowing more of it captain_magnus: Yep, will do... Thanks :-) hpj: federico1/psankar: plus you don't need to load the whole thing into memory, which takes time :) jpr: ok, thanks srag, psankar, chen, lakhil , jony whoever else I missed :-) jpr: hopefully you can stick around until after the meeting for more information srag: and thanks jpr for the chance to speak out :)

Started at --> 07:42:23 PM psankar: Thanks everyone srag: sure dliang: Everyone here is crazy on Evolution. jpr: federico1: take it away psankar: hpj, okay suseROCKS: I vote we get Evolution t-shirts! federico1: heh * psankar doesnt have one :( federico1: we have a pretty hefty tracker bug now for main-menu problems: https://bugzilla.novell.com/show_bug.cgi?id=341831 srag: dliang, :) bugbot: openSUSE bug 341831 in openSUSE 10.3 (GNOME) "Tracker bug for gnome-main-menu" [Normal,New] schooms: suseROCKS: +1 schooms: :) federico1: I've started a page to organize a bug week for main-menu: http://en.opensuse.org/GNOME/Main_menu_bug_week - it's totally empty right now, but we'll use it to organize bug fixing dliang: A T-shirt with a monkey at the front and a man at the back? munki1: dliang: no, just a man on the front :P federico1: what I want to do next is to sort main-menu's bugs, and look for volunteers to fix them. THAT'S YOU :) federico1: sreeves knows the code really well; I am more or less familiar with it federico1: I guess next week we can focus on fixing some behavior problems and the most egregious performance problems munki1: i'd love to get involved, but i'm REALLY busy these days cyberorg: i promise to checkout svn everyday :) mtgordon: federico1: So how would the bug day work? mtgordon: federico1: Would you be asking people to test patches? jpr: federico1: will you have a page that describes how to set up all the requirements for building and install main menu jpr: and how to test the source package? federico1: mtgordon: bug week. Yeah, ask people to test patches (the build service will be busy...), see if people want to help out with fixes, etc. federico1: jpr: yeah, that's on my to-do list munki1: are we going to test current main-menu, or svn? federico1: zypper makes it easy these days mtgordon: Ah, s/day/week/ jpr: federico1: when are you proposing we do this? federico1: munki1: probably current... sreeves, how different is svn from what is on 10.3? and do you know the status of tiles-2? btimothy: would be nice if we could provide our own build service machines so that when we do organized events like this, we can guarantee certain performance levels (i.e., get packages built fast) federico1: jpr: next week, all week! federico1: OKAY PEOPLE federico1: FORMAL ANNOUNCEMENT sreeves: jpr federico1- I can add the setup to the wiki page - I have a cheat sheet sreeves: svn head is only slightly changed from 10.3 federico1: I welcome you to participate in the Bug Fixing Week for main-menu, NEXT WEEK (Dec 17-21) federico1: we need testers and hackers sreeves: the tiles-2 branch is a major overhaul sreeves: and it's not completely finshed federico1: sreeves: ok, then we can postpone tiles-2 federico1: sreeves: thanks, the cheat sheet would be very useful :) federico1: sreeves: can you put it in http://en.opensuse.org/GNOME/Main_menu_bug_week ? jpr: will tiles-2 trample what we do next week though? sreeves: federico1: yup suseROCKS: Since I'm rebuilding test machines these days, i guess I can be present to test things out suseROCKS: Are we testing on 10.3 or 11? munki1: do we need to test patches too? sreeves: jpr: yeah, thats an issue - we need to pour through that branch and see if we want to go forward with it jpr: do we have enough time before next week? sreeves: jpr: unfortunately we did not get a status from jimmy before he left sreeves: so I do not know what exactly is in there, or how close to done it is federico1: I can take a look after next week captain_magnus: jpr: I don't suggest that we use tile-2 for this... Better to stay on svn trunk and fix bugs there for now jpr: ok jpr: as long as you're sure the efforts won't clash jpr: ok jpr: federico1: AI send more details to the mailing list

Started at --> 07:53:25 PM jpr: btimothy: go man go btimothy: everyone knows the routine btimothy: not sure how much i need to say/do here ;) btimothy: looks like jpr took care of the evo mtg. stuff :) suseROCKS: I don't have much to report on progress on my end. Got unfortunately sidetracked with the fall and alpha 11.0 annoyances btimothy: federico1: done with bug categorization yet? or should we move that to an ongoing state? btimothy: munki1: any additional items needed for bug categorization from you? munki1: neither do i, i'm completely swamped with college stuff btimothy: k munki1: btimothy: i suppose not btimothy: munki1: should we remove that line then? munki1: yep federico1: btimothy: yeah, ongoing... it's about 70% done for 10.3 btimothy: munki1: k btimothy: thanks federico1 btimothy: jpr: boxed 10.3's? jpr: no progress :-/ captain_magnus: jpr: Prolly time to skip that one now... It's old... btimothy: jpr: need help? captain_magnus: Organize some shirts or something instead perhaps? btimothy: yeah btimothy: possibly srag: captain_magnus, +1 suseROCKS: what is this topic about?? jpr: no, i just need to sit down and pull all the addresses and people together jpr: and mail them to Martin btimothy: jpr: something possibly by next mtg.? * captain_magnus thinks jpr wants to play santa and send it out as a christmas present :-) btimothy: captain_magnus: +1 :) btimothy: suseROCKS: tracker bug for a11y? btimothy: suseROCKS: still on track? btimothy: federico1: good work organizing main menu bug hunt :) suseROCKS: btimothy, like I said, i got sidetracked this week with the fall, but cappy has offered to help me set up tracker this week which we will do. btimothy: suseROCKS: fair enough (sorry abt. the fall) federico1: btimothy: hah, it's just whipped up :) btimothy: k, anything else... * btimothy quickly grabs last week's AIs btimothy: how'd we do ... suseROCKS: btimothy just have to wait for captain_magnus to finish his pole-dancing btimothy: AI: Federico to schedule and announce bug hunting for main menu dec 17 AI: suseROCKS to create tracker bug for a11y AI: captain_magnus to write up factory installation pointers and send to the list AI: Darragh and suseROCKS to test instructions? AI: captain_magnus , jpr , cyberorg to note final feature decision AI: JP schedule Evolution theme meeting with srag captain_magnus: btimothy: I added all the AI's from last week (i hope) to the task list so no need btimothy: ah, right btimothy: good btimothy: well, anythign else then? jpr: excellent btimothy: i think we can move on jpr: gained back some time :-)

Started at --> 08:00:23 PM jpr: so jpr: for a lot of western europe and north america jpr: having meetings of the next 3 weeks will be rough jpr: particularly Dec 27 * srag may not be available for another 2 weeks srag: s/weeks/meetings jpr: i would suggest we hold the meeting on Dec 20 and on Jan 3 (the asia/australia one) but not the meeting on Dec 27 jpr: +1 :-) munki1: jpr, does that include any sort of communication, or just meetings? jpr: just this meeting captain_magnus: +1 sreeves: jpr: I agree btimothy: jpr: works for me! hpj: sure munki1: ok, no probs here suseROCKS: that's only missing one meeting I see no issue so +1 mw: + * captain_magnus thinks mw is lazy... :-) jpr: any dissenting opinions? suseROCKS: but I'll be sad and lonely on the 27th

Started at --> 08:03:31 PM jpr: questions? jpr: especially in light of the alpha 0 release this week jpr: which i hope people have been doing some testing on suseROCKS: well I installed the 11.0 alpha dvd a couple of times so far and have had great problems hpj: how many of you are unable to configure their graphics? hpj: using SaX suseROCKS: and now I am installing over network per Cappy's instructions munki1: i've been running 11.0 on VirtualBox, and it seems pretty fast captain_magnus: Do we have one package with the default Desktop settings or is this spread across multiple packages? captain_magnus: hpj: No problems on ATI for me jpr: captain_magnus: multiple packages suseROCKS: hpj there's a few people on the factory ml who are reporting similar problems in vmware I pointed them to your bug report captain_magnus: jpr: Figured! Would it make sense (be possible) to put it in one package? munki1: and i only dedicated 350 migs of ram munki1: jpr, is it supposed to be that fast, or is it all in my head? cyberorg: i updated 10.3 to 11 on running system, everything went smooth (its alpha0) suseROCKS: question... when I installed alpha0 DVD it was still gnome 2.20 Isn't there supposed to be a newer version? captain_magnus: Tip to everyone! If you use Factory for clean installs, you can probably look forward to the new themed installer in a near future... (although it was pulled today due to issues) munki1: yea, i was wondering about that actually jpr: captain_magnus: maybe, have to figure out how that would work exactly jpr: captain_magnus: a bit painful because the .schemas are in several places i think jpr: suseROCKS: yes, mw should probably discuss in 11.0 devel updates what the 2.21.x schedule is like jpr: any other questions? jpr: munki1: i think in your head :-) munki1: jpr: any plans to include WebKit in the official build? jpr: good question jpr: no plans jpr: but there probably should be jpr: munki1: please add to the wishlist

Started at --> 08:09:08 PM hpj: federico1 promised us he'd finish merging intlclock last week. federico1, how'd that work out? munki1: jpr: k, will do hpj: suseROCKS: a11y pattern/bug filing? i guess you didn't have much of a chance to work on that captain_magnus: Hehe... suseROCKS have said twice that he didn't get around to it... hpj: ok suseROCKS: no, was too busy mesmerized with captain_magnus's pole-dancing this week hpj: i'm done packaging accerciser, but need to package gnome-python-extras to enable some of its functionality hpj: i was a bit surprised we didn't have that packaged already jpr: i'm pretty sure we do actually federico1: hpj: I keep being 85% done :) right now I'm fixing bugs in the preferences dialog and merging the last bits of code jpr: mw: ^^ ? hpj: couldn't find it in factory munki1: jpr, yes we do, but for some crazy reason most running apps don't recognise it jpr: i have the pulseaudio update for rodrigo mw: cleaning up our various python packages is on my todo list jpr: rodrigo has been checking everything into Factory jpr: darix just had a few small changes he requested jpr: and it should all be in and one of our first big features will be off the list :-) hpj: jpr: sweet jpr: hpj: python-gnome-extras captain_magnus: I started looking at the next version of slab (called tile-2 in svn) captain_magnus: There's been a complete rewrite of AB in there jpr: :-) hpj: jpr: ah captain_magnus: I found that it is possible to use threads to make AB appear visually before all the applications are populated in the window captain_magnus: The threading thing did not work though, but after some poking I got it working hpj: so accerciser packaging is done by tomorrow hpj: and that's a quick little win captain_magnus: Result is that AB displays it's main window (with an empty app section) in ~0.2 seconds captain_magnus: AB then loads all the apps and once loaded it shows then jpr: yes, that will be nice jpr: hpj: will we drop at-poke then? captain_magnus: I poked a bit more so that AB starts showing apps before all of them are loaded and the result looks pretty good to me jpr: hpj: or ? hpj: jpr: yes jpr: ok jpr: more patterns bugs :-) hpj: btimothy: last week you mentioned wanting to wait for this week for putting PackageKit into factory munki1: captain_magnus: you can have the same effect by applying less ram ;P sreeves: PackageKit and gnome-packagekit have been submitted into factory btimothy: and accepted :-D hpj: sreeves/btimothy: great! jpr: oh, yes, thats another feature win :-) hpj: another one off the list btimothy: right now, however, packagekit trunk moved to use a newer policykit, which, in turn, requires a new hal hpj: so captain_magnus, main menu redesign? btimothy: so i'm in the middle of trying to restore things to a working state for any new code btimothy: and on a sidenote, i got the yum backend running for packagekit on 10.3. kind of interesting to compare against ;) captain_magnus: The latest call for m-m and ab is to combine them to one... Something like this: http://www.coolice.org/g-m-m-simple.png/ jpr: btimothy: the yum backend calls out to the command line tool all the time right? captain_magnus: So when you click on More Apps, it will populate the "white space" instead of opening a new window munki1: captain_magnus: ah, i see btimothy: jpr: not entirely sure ... i think yum provides a python library (or however python works) and the backend calls that directly? cyberorg: captain_magnus, you looked at gimmie? jpr: ok suseROCKS: I looked at captain_magnus's sample yesterday, and I liked it so far. captain_magnus: Lots of users in this channel think that's the way to go... But I have yet to hear anything from the GNOME devs here...:-) btimothy: jpr: i don't really see performance degregations with it (especially compared with the zypp backend) captain_magnus: cyberorg: Nope jpr: ok hpj: jpr: last time, you mentioned starting on the Xgl/Compiz work hpj: jpr: any update on that? jpr: no, we should still start on it soon :-) hpj: ok :) munki1: captain_magnus: it's quite nice, a memory hog though jpr: but we need to organize a team around that jpr: cyberorg: i presume you'd like to be involved there? hpj: then i don't have anything else for the 11.0 update cyberorg: on alpha0 i saw some work in Xsetup that enabled compiz automatically cyberorg: jpr, me can't code :( suseROCKS: gotta ask another quick question about Alpha. Did anyone else have sound-card detection problems? If so, Darragh may not be able to test out a11y speakout issues jpr: cyberorg: the Xsetup if its the same as 10.3 just setups compiz to run at gdm time to get drop shadows and such there as well

Started at --> 08:20:37 PM cyberorg: jpr, yeah saw that bit, it is just 5 lines or something there * jpr sneaks in an agenda item jpr: cyberorg: is there more in alpha 0? cyberorg: what i dont understand is will compiz relaunch after login? jpr: cyberorg: yes jpr: so, tentatively next Thursday Dec 20 we'd like to consolidate a bunch of smaller fixes in one maintenance update for 10.3 jpr: we are collecting fixes now if people have suggestions munki1: what are the more subtle changes in alpha0, btw, i haven't been able to spot anything new so far? cyberorg: jpr, i guess xorg.conf profiles sax2 uses will need work to automatically enable composite/aiglx for nvidia and intel jpr: cyberorg: yes jpr: let me know here or on the mailing list about suggestions cyberorg: relaunching compiz is bad idea it stutters/freezes etc

Started at --> 08:23:06 PM jpr: questions on development? hpj: munki1 had one above jpr: munki1: not much changed for GNOME other than package splits and a few updates for packages jpr: mw: do we have a timeline for GNOME 2.21.x? 2.21.4 already on monday * munki1 pokes mw * munki1 is now known as munkii jpr: other questions? hpj: i second jpr's Q to mw suseROCKS: will we get an announcement on the ml when 2.21 is available? Seems rathe rpointless to test when it s still 2.20 mw: grumble mw: i can aim for next thursday hpj: well, the good thin about having installed 11.0 is that you've cast loose from 10.3 at least :) jpr: mw: do you need people to help? hpj: so you can update with zypper when new stuff arrives suseROCKS: hpj trying to  :-) mw: jpr: yeah, probably jpr: ok jpr: i will help some hpj: i can help some too mw: ok jpr: LAST CALL FOR QUESTIONS mw: i'll prepare the spreadsheet tomorrow mw: (about to leave for the day today) jpr: suseROCKS: the veal is now over cooked jpr: thanks all! Meeting ended at --> 08:33:18 PM

jpr: federico1: AI send more details to the mailing list