Started at --> 00 jpr: Welcome to the openSUSE GNOME team meeting! jpr: this is our monthly time shift meeting captain_magnus: Thanks jpr :-) jpr: trying out a new time to better accommodate Asia and Australia jpr: i think we may be missing a few people today :-) srag: jpr, thx for the new timings.

Started at --> 00 jpr: We have http://en.opensuse.org/GNOME/11.0/Testing jpr: with a couple specific items on it jpr: for testing jpr: generally Factory is finally in good, synced shape atm jpr: with no conflicts for GNOME that I see jpr: and containing GNOME 2.21.90 jpr: couple issues are that nautilus is a little flaky atm with the switch to gvfs prasadk left the room. jpr: not crashing, but somethings don't work properly jpr: does anyone know the status of the X crash in vmware? captain_magnus: The X crash is only when you install VMwares drivers I believe... captain_magnus: So if you don't install/use them, it will work... (at least it works for me) jpr: also https://bugzilla.novell.com/show_bug.cgi?id=353489 is now fixed jpr: which is excellent jpr: go sreeves for chasing that down :-)

Started at --> 00 jpr: So, bug days jpr: we had 3 of them last fall jpr: and completed reviewing most of the old distro bugs jpr: except about 70-80 on openSUSE 10.2 jpr: plus we're getting to the time to start review 10.3 bugs for fixes in 11.0 jpr: http://en.opensuse.org/GNOME/BugDays captain_magnus: jpr: Is anyone going to fix those 70-80 bugs? jpr: captain_magnus: they still need to be reviewed jpr: and yes, a few bad ones may still be fixed jpr: sreeves wants to take a look at least jpr: so, we need a volunteer to organize the bug day page for 10.2 :-) jpr: mostly copying what mtgordon did in the past jpr: and to set a time/date for the bug squash jpr: we tried both Friday and Wed. before jpr: i think both days were ok prasadk [n=tester@125.16.129.16] entered the room. jpr: i'm going to let an uncomfortable silence linger until someone volunteers :-) captain_magnus: Haha captain_magnus can't volunteer as most peoples "Wed" and "Fri" is when he's working and can't participate captain_magnus: munkii: You'll take it then? jpr: kallepersson, lakhil, lejo_, munkii : don't have to run it, just setup the page :-) captain_magnus: mmeeks: You? chen was about to propose lakhil :) kallepersson: jpr: ? mmeeks hides elsewhere. kallepersson: Run what? captain_magnus: jpr: Ok, I'll start it... jpr: kallepersson: bug day jpr: captain_magnus: ok :-) lakhil: jpr, munkii and I can ownershipid he is ready :-) lakhil: *take jpr: yes! captain_magnus thinks jpr so owns him an iPhone... :-) jpr: AI: lakhil and munkii to setup up next bug day page, date and announce in email lakhil: * ownership jpr: nice jpr: thanks guys!

Started at --> 00 jpr: ok, task review jpr: i finally did the tshirt mail jpr: and i have the system down pat now jpr: so if you want to recommend a tshirt or hat for someone jpr: just email me the snail mail address captain_magnus: jpr: How many people? jpr: lets see jpr: five, plus one was already done that i sent jpr: (cyberorb) jpr: any other task updates? captain_magnus: jpr: You should blog about it and show us a photo of the shirt... Could perhaps get us more people... :-) captain_magnus: I have not had a working factory tree for weeks so have not been able to setup an automatic install from the tree... I think we have fixed most issues with factory now so I can start soon.... jpr: hehe captain_magnus: (Which would be the task called "Find out ways to automate nightly distro installations (autoyast, kiwi)") jpr: 10.3 updates are in progress jpr: suseRocks is a better task master than me :-)

captain_magnus: I think we should discuss the RTM evaluation at the next meeting jpr: good idea jpr: AI: review RTM usage at next meeting jpr: so, the X guys can do a meeting jpr: but not the next meeting jpr: on the 14th jpr: so, buildservice was very popular last time as weel jpr: should we invite Adrian instead? jpr: +1 jpr: :-) captain_magnus: Sounds like a good idea... If we get people to understand BS at this stage of 11.0, perhaps we can get some quality packages packaged before the release... captain_magnus: So... +1 psankar: +1 from me too. jony: +1 ( wud need info on building for other distros) jpr: AI: JP to request Adrian attend next theme meeting jpr: jony: ah, good topic suggestion

jpr: questions this week? jpr: and i forgot to mention in the factory testing thing suseROCKs [n=IceChat7@70.19.117.123] entered the room. jpr: to a) test the live CD b) GNOME 2.21.91 should be going in Feb 18-20 just before FOSDEM jpr: other questions? suseROCKs: sorry Im late folks captain_magnus: jpr: LiveCD... No Mono app works :-( captain_magnus: jpr: I don't know why as my "real" install and my "livecd" have the same packages installed jpr: ick captain_magnus: jpr: So we need someone that undertsnad mono to troubleshoot that jpr: captain_magnus: bug #? captain_magnus: jpr: Have not opened a bug for it yet captain_magnus: jpr: Been busy filing bugs for the real A2 install :-) jpr: hehe, ok jpr: srag, jony, psankar, prasadk - this is your chance! no questions at all? jpr: anyone else for that matter psankar: nothing from me suseROCKs: for once I don't have annoying questions captain_magnus: Oh... I have some admin stuff... Not really quesions but I need to talk about it anyway lakhil: jpr, i had issue in upgrade , it was not listing down all the packages for which updates are available (i found in evolution basically) srag: jpr, no questions really. jony: just on BS .. since we'll be discussing it next time ... nothing for now .. captain_magnus: We keep failing on updating our wiki pages with regards to our meetings srag: me and captain_magnus were thinking of some proposal lakhil: jpr, i need to check again if it happens captain_magnus: This results in us missing out on the weekly news, and just the other day, we missed out on Zonkers blog post srag: captain_magnus, go ahead. captain_magnus: We really need to make sure that we fix up all the pages with regards to meetings straight after the meeting or the day after at the latest captain_magnus: I am talking about this: http://en.opensuse.org/GNOME/Meetings#Weekly_Duties jpr: captain_magnus: yes, agreed jpr: lakhil: ok jpr: other questions? captain_magnus: I would like us to try to get a volunteer to do this task... And it should be a different person each week... (Nobody likes these admin tasks, hence this proposal) suseROCKs: I think we're also not getting our meetings listed in news.opensuse.org calendar for which I subscribe via evo calendar captain_magnus: We should ask for a volunteer in each meeting jpr: suseROCKs: we are, i just missed this week jpr: captain_magnus: i think its better someone own the task jpr: fully captain_magnus: jpr: Well.. Unless you think that you can do this every week, I can't see it working jpr: well, i have been doing it every week jpr: just at the wrong time :-) captain_magnus: jpr: We all have jobs, hobbies etc... suseROCKs: how about this... is there a wiki page that explains what needs to be done? such as posting minutes/transcripts? captain_magnus: jpr: So I thought that if we spread the workload around, we might get this done on time every week jpr: true jpr: suseROCKs: yes jpr: http://en.opensuse.org/GNOME/Meetings#Weekly_Duties srag: jpr, may be a round-robin approach would be nice jpr: ok, so far i see srag, captain_magnus and suseROCKs volunteering :-) jpr: and I will do it as well jpr: first up, captain_magnus :-) captain_magnus: Hah! I am really busy tomorrow... jpr: ok jpr: srag then :-) srag: jpr, sure for Today's thing jpr: great jpr: any other questions? captain_magnus: jpr: The only thing is that none of us have rights to news iCal... suseROCKs: yeah captain_magnus: jpr: So perhaps you could fill it up for the next couple of months? :-) jpr: ok, i will do that, I'll add several meetings at once this time jpr: yes

jpr: scott has submitted the patch info to autobuild jpr: so hopefully the packages will be on the test update server soon captain_magnus: AI: Create round robin schedule between jpr, srag, captain_magnus, suseROCKs for http://en.opensuse.org/GNOME/Meetings#Weekly_Duties jpr: mw submitted a fixed xulrunner jpr: for 10.2 and 10.3 jpr: and federico is almost done with the intel driver fix jpr: hpj is poking xdmcp breakage on 10.3 with gdm that mmeeks blogged about

jpr: lets see :-) captain_magnus: I want to know why we still don't have the latest g-m-m in Factory... jpr: GNOME 2.21.90 is in as mentioned, 2.21.91 coming in 11 days jpr: captain_magnus: sreeves is going to do a release this week upstream and check that in jpr: pulseaudio is installed by default now suseROCKs: aren't we expecting 2.22 beta to be in factory? munkii: hey, i didn't know were having an early meeting today! jpr: suseROCKs: it is, 2.21.90 is a beta captain_magnus: suseROCKs: 2.21.x is beta jpr: sreeves is working on PackageKit with the yast team again suseROCKs: ok now Im confused, I thought I read last week that GNOME released 2.22 in beta. (shrug) rodrigo: oh, meeting was announced for 13:00 GMT (14:00 CET), and it's still 11:41 GMT! jpr: the yast team has a student Stephan Haas we are working with rodrigo reads back jpr: rodrigo and hpj are also going to start on improved compiz/xgl config soon suseROCKs: munkii are you on the opensuse-gnome mailing list? captain_magnus sent out meeting notices yesterday. jpr: and federico is lining up bug fix weeks for multihead and gtk file chooser

jpr: rodrigo: you're up :-) rodrigo: ok munkii: suseROCKs: i don't read the ML mail that often! *ducks* rodrigo: I hold down a bit the patch upstreaming work, because of the difficulties for external people to help rodrigo: that is, we were in the middle of the 2.21.5 update, with not always up-to-date packages in openSUSE:Factory rodrigo: and also, for a simple work like tagging is, we don't have a place for external people to do it, all submissions need to be done internally in autobuild rodrigo: we are looking for a way to have GNOME:UNSTABLE (oor whatever) for the patch upstreaming work rodrigo: and sync it after that to the internal abuild jpr: mw had problems with that recently because of lingering oS:F breakage from the disk outage rodrigo: but anyway, I started on my own the patch upstraming: http://en.opensuse.org/GNOME/Projects/PatchUpstreaming captain_magnus: rodrigo: Isn't all of this going to build in BS soon anyway? So internal abuild is not needed? rodrigo: captain_magnus: I hope so jpr: well for certain definitions of soon jpr: april at least before the build service supports it captain_magnus: I tought we were building 32bit Factory in BS at the moment rodrigo: we are, but that's a copy of the internal abuild packages afaik captain_magnus: Oh, ok... rodrigo: so, see the wiki page above rodrigo: it contains the list of (almost) all of packages coming from upstream GNOME captain_magnus notes that rodrigo have done a fantastic job with that page... rodrigo: I haven't included, for the time being, other packages, like external deps, mozilla, etc jpr: mmeeks: orbit and bonobo patches on that list :-) rodrigo: so, if you maintain one of those packages (/me looks at evo hackers), please tag / upstream patches rodrigo: there is still the question what to do so that external people can help srag: rodrigo, sure. I'll have a look at them jpr: srag: you know how to tag them? rodrigo: for the time being, if someone wants to help, just send me patches of the .spec changes, and I'll submit them myself psankar: rodrigo, i looked at it today morning. we started upstreaming sled patches psankar: already and will continue to 10.3 as well jpr: http://en.opensuse.org/GNOME/Patches rodrigo: psankar: great, also, could you please have a look at the tagging? -> http://en.opensuse.org/GNOME/Patches jpr: lists how to tag them in the spec file psankar: rodrigo, sure. rodrigo: great!! rodrigo: update the wiki page as you work on those packages jpr: rodrigo: anything else? rodrigo: apart from that, the only thing is, who wants to help upstreaming patches? rodrigo: you get bugzilla points in b.g.o for each patch you submit :) suseROCKs: rodrigo was there any consensus made about how to get comments from testers for the /11.0/testing page? captain_magnus: rodrigo: How does upstream work but... Would they listen to unknown people like myself if I were to submit a patch...? rodrigo: suseROCKs: not that I know jony: (srag is offline. power cut) captain_magnus: rodrigo: I'm asking because perhaps is better to have well known hackers to submit the patches? rodrigo: captain_magnus: yes, patches are welcome from everywehre rodrigo: captain_magnus: sdpecially if the patch is correct rodrigo: of course, we don't want to file all patches, we should make sure what we upstream is good for upstream psankar: srag told he will get the meeting logs from jony and will publish them jpr: part of the patch review is simply tracking down the upstream or bnc bugs jpr: doing that you find we sometimes have obsolete patches rodrigo: yeah, a lot jpr: where the fix is elsewhere now rodrigo: and patches that fix things that upstream might want jpr: there were 2 in gnome-session yesterday captain_magnus: So this requires you to know svn/git/abuid/osc and all of that to be able to do it properly? rodrigo: so, it's an easy task, with bugzilla points :-) jpr: captain_magnus: no, because the patch is already generated jpr: in the package suseROCKs sells his B.G.O points on eBay for cash. rodrigo: captain_magnus: well, not really mmeeks: jpr: interesting wrt. the orbit/bonobo patches, not sure what they are, rodrigo: yeah, the patch is known to apply in our packages, and if not, we should rework it to make it apply if it makes sense mmeeks awaits rodrigo filing them to review ;-) captain_magnus: rodrigo: I think you should do a couple of patches and "think out loud" here in this channel to make people understand what's needed... (I know I don't understand....) rodrigo: mmeeks: ok :) rodrigo: ok rodrigo: let me show you what I did: captain_magnus: rodrigo: Perhaps set a time where people can "listen in" captain_magnus: rodrigo: Should probably do it after the meeting? rodrigo: yeah, if you want rodrigo: much better, we can start doing a package in group, and then have each one go on thjeir own captain_magnus: rodrigo: Sounds like a plan jpr: AI: rodrigo to set up 30-60 minute meeting to teach patch review and send to mailing list

jpr: questions? jpr: comments? jpr: concerns? captain_magnus: I've been talking to coolo regarding the LiveCD's.... captain_magnus: We have an opportunity to help out with them (or rather, be responsible) suseROCKs: since I stepped in late to the meeting.... How is the latest Alpha installing? Are we past the troubles we had before? captain_magnus: Is this something anyone would be interested in helping out with? captain_magnus: Note that we would also have to be responsible for the KDE side to make sure it works there as well suseROCKs: what specifically are you referring to captain_magnus? What are they needing help on? captain_magnus: We would NOT play around with what packages would be included/excluded... captain_magnus: We would make sure that the external scripts etc works captain_magnus: suseROCKs: This is based on KIWI... rodrigo: captain_magnus: what external scripts you mean? munkii: any showstoppers in alpha2 that i should be concerned about? considering that i'll start using it as my main desktop, instead of VMing from now on captain_magnus: rodrigo: When you build an image with kiwi, it is stock standard... You need external scripts to make decisions based on what DE you are running (If you run GNOME, then you do specific things... If you run KDE, other things are done rodrigo: ah ok rodrigo: then I guess we *really* need to help out, don't we? :) rodrigo: if that affects the gnome live cd, right? captain_magnus: rodrigo: You also need to specify what services should be started/disabled etc captain_magnus: rodrigo: I think we should help out... But as I said before... All of us have day jobs, hobbies etc, so we would need to work together... captain_magnus: The "code" is in a public svn repository so anyone can check it out and play with it munkii has no day job, and likes to collect icons for a hobby captain_magnus: ( svn co https://forgesvn1.novell.com/svn/opensuse/trunk/distribution/images/kwliveCD-suse-11.0 ) rodrigo: captain_magnus: let's open a Projects/LiveCD wiki page with instructions, goals, things to test, etc, ok? captain_magnus: rodrigo: Yes, that would be good... rodrigo: AI: captain_magnus to create a Projects/LiveCD page captain_magnus: AI: rodrigo, captain_magnus to create a wiki page with regards to LiveCD ( instructions, goals, things to test, etc) captain_magnus: :-) rodrigo: :) captain_magnus have no more "questions" jpr: anyone else? srag: jpr, should_go_upstream ? jpr: srag: what about it? lakhil: srag, you missed ..jpr had pointed out http://en.opensuse.org/GNOME/Patches srag: just back. srag reads above jpr: Thanks all!

AI: lakhil and munkii to setup up next bug day page, date and announce in email AI: JP review RTM usage at next meeting AI: JP to request Adrian attend next theme meeting AI: captain_magnus Create round robin schedule between jpr, srag, captain_magnus, suseROCKs for http://en.opensuse.org/GNOME/Meetings#Weekly_Duties AI: rodrigo to set up 30-60 minute meeting to teach patch review and send to mailing list AI: captain_magnus to create a Projects/LiveCD page AI: rodrigo, captain_magnus to create a wiki page with regards to LiveCD ( instructions, goals, things to test, etc)