Started at --> 19:11:30 suseROCKs: We shall... jpr: Welcome to the openSUSE GNOME Team meeting! jpr: surprisingly this is our first in 3 weeks jpr: due to FOSDEM and hackweek jpr: so its time to get back on track as we march to 11.0 jpr: which has a feature freeze in ~ 6 weeks

Started at --> 19:12:50 jpr: so, a question was posed to me about how to make our agenda more focused and relevant as its sort of static week to week jpr: a couple ideas jpr: posting to the mailing list beforehand jpr: and collecting ideas jpr: or collecting next agenda items jpr: at the end of the current meeting jpr: (or both) jpr: comments? suseROCKs: How is that different from the present system where we all can edit the agenda before the meeting? ** FunkyPenguin votes for end of current meeting and ML with a cut off day of the following monday jpr: well, in reality i'm the only one who ends up editing it atm vuntz: I guess it's a good thing since it makes everybody think a bit about the agenda before the meeting jpr: with captain_magnus a little bit ivanz: suseROCKs: you end up with an e-mail in your inbox.. more chance for feedback then having to log in on a web page and edit it vuntz: can't hurt suseROCKs: hey I've edited too :-) ivanz: less effort required jpr: so FunkyPenguin votes for both jpr: +1 suseROCKs: Although it could be more like what btimothy and I usually do (but didn't this week) where we remind people to tend to their tasks before meetings via ML federico1: does anyone have projects they may like done during the Summer of Code? jpr: federico1: meeting ivanz: +1 for both wiki and mailing list jpr: any major complaints? suseROCKs: none jpr: sounds good FunkyPenguin: there needs to be a cut off point though jpr: yes rodrigo: monday sounds good jpr: i would suggest Tues rodrigo: or tuesday, 2 days before the meeting rodrigo: yes jpr: thats when i try to send the announce jpr: ok FunkyPenguin: ok that works, but in the reminder include the agenda sreeves: we just need to not move static items forward unless there is information to report on them tmielke: sreeves: Is there really an rpm attached to bug 350318? I can't seem to find it. jpr: AI: jpr and captain_magnus to collect agenda items on the mailing list by Tuesday bugbot: openSUSE bug 350318 in openSUSE 10.3 (GNOME) "GDM/X crashes in VMWare" [Major,New] https://bugzilla.novell.com/show_bug.cgi?id=350318

Started at --> 19:17:53 ** sreeves looks for someone else to report this week jpr: i moved to factory full time this week sreeves: have not done any updating due to hack week, fosdem, germany trip jpr: yast and totem-pl-parser are mucking things up rodrigo: I have moved my 2 main machines also for 2/3 weeks now rodrigo: but yes, updating is now a bit hard, lots of yast conflicts suseROCKs: Do you guys think that Factory is stable enough now to be a primary machine? vuntz: couldn't install factory on my second laptop jpr: i think in general as per the project or factory mailing list we should launch a factory test project rodrigo: suseROCKs: it has some problems, but it's usable jpr: with KDE and other teams vuntz: https://bugzilla.novell.com/show_bug.cgi?id=365337 ivanz: I've tried installing factory yesterday but I can't go past the first user setup for now bugbot: openSUSE bug 365337 in openSUSE 11.0 (YaST2) "Current installer fails with an error after entering my user information" [Normal,New] ivanz: yeah I ended up filing a duplicate of that one vuntz: ivanz: heh jpr: the work around is to install 10.3 or a1 or something ivanz: hey wasn't my fault I did try searching :) jpr: and upgrade from there federico1: ugh, I never finished writing my "first impressions" mail about factory suseROCKs: ok then I will go full time Alpha this weekend federico1: the bugs are being fixed, though :) suseROCKs: federico1 has more important pressing problems. He can't use the One-Click-Backup button on his usb drive :-) vuntz: jpr: I was kind of waiting for the yast people to ask me to test some new version to check it's fixed vuntz: my main laptop is on factory, though jpr: vuntz: true, installer needs testing, but lots to test in between alpha's as well ** vuntz starts downloading the latest alpha FunkyPenguin: is a3 out? suseROCKs: Installation was a huge problem for me the past two months and why it prevented me from doing any real testing. munkii: most installer bugs have been fixed though, only zypper bugs remain jpr: no, still a couple of weeks for mar 3 jpr: oh rodrigo: I found you can do a base x system install, and then install additional packages when everything is installed jpr: the new szypper is super fast jpr: highly usable suseROCKs: +1 for rodrigo's tip. It's what finally got me on Alpha the last time. lejo_: every 20th bug about factory should be rewarded with a small gift ;) munkii: i would say, but requires constant maintenance by the user jpr: hehe jpr: yes, it does require user maintenance jpr: but every thing that does jpr: should cause a bug to be filed ** vuntz tries rodrigo's trick jpr: anything else on factory? munkii: yeah, KDE4 sucks munkii: :P jpr: AI: rodrigo to post install trick on wiki jpr: nautilus and gdm aren't exactly setting the world on fire atm vuntz: can't get gvfsd to work jpr: me neither vuntz: even when I manually launch it suseROCKs: let's not get into a KDE/GNOME war during the meeting. It's bad enough its getting pervasive outside the meetings lately. munkii: yes, nautilus is the single most bug infested piece of software on my desktop now vuntz: need to test jpr's workaround for NM & ethernet interface jpr: ok, lets move on

Started at --> 19:27:11 jpr: so, not really sure what happened to bug day munkii: any new date? jpr: lakhil: ? suseROCKs: I don't think Bug Day ever happened after all jpr: it was lakhil and someone ? munkii: jpr: it was set to be held friday last week jpr: suseROCKs: who's listed on RTM? munkii: jpr: me ^_^ jpr: ok jpr: munkii: so, bad timing because of FOSDEM munkii: yep jpr: munkii: would you like to try for Mar 7? munkii: np suseROCKs: munkii: Just don't run pidgin while running BugDay :-) munkii: that's next friday, right? munkii: suseROCKs: it's fixed now.. i think rodrigo: yes munkii: ok, i'll fix the dates on the wiki suseROCKs: So are we done talking about Zonkers behind his back? :-) vuntz: suseROCKs: sssh, we should stop talking about him! suseROCKs: ok the room is quiet now... Speak up people! suseROCKs: (tap tap) Is this thing on? jpr: ok

Started at --> 19:34:27 jpr: federico1: take it away federico1: ok federico1: we can start a hack week next week, or is it too short-notice? jpr: depends on the topic :-0 jbrockmeier: suseROCKs: I sure hope so. rodrigo: next week I'm on holidays, it's too short notice :-) federico1: I was thinking file chooser or multiscreen stuff federico1: right now I'd prefer file chooser, since it's what I'm working on right now anyway :) suseROCKs: federico1 is hackweek for 11.0 or previous versions? vuntz: stupid question: how does a hack week exactly work? :-) federico1: suseROCKs: it would depend on the topic, I guess... the file chooser is pretty generic; for multiscreen I'd prefer to have the latest and greatest everything federico1: vuntz: task for me: make a page on how hack weeks work jbrockmeier: federico1: are you talking about an "official" hack week? jpr: AI: federico1 to describe hackweeks in GNOME/Projects on wiki jbrockmeier: or a week we publicize for a specific thing to be worked on? federico1: vuntz: basically, we pick all the bugs in a category (all main-menu bugs, all file chooser bugs, all bugs related to xinerama) and try to fix them vuntz: federico1: also, is multiscreen important in the randr1.2 world? suseROCKs: vuntz Hackweek = Federico dumps patches on us poor unsuspecting testers and we break our machines :-) federico1: jbrockmeier: nope, these are our bug fixing weeks jbrockmeier: ah, OK ** jpr introduces jbrockmeier aka Zonker jpr: (hi) jbrockmeier: federico1: want to publicize it, though? jbrockmeier: Howdy :-) federico1: jbrockmeier: sure! the more helping hands, the better :) federico1: vuntz: heh... we've been using "multiscreen" generically for "you have more than one monitor", not for actual X screens :) suseROCKs: jpr can we insert something into the agenda at the last minute here? Since we have two new (and I consider important people here) Give them a few minutes to chat about themselves and their vision? munkii: jbrockmeier: a gnomer? vuntz: federico1: right, but it seems randr1.2 world makes most of the bugs disappear jbrockmeier: munkii: sometimes :-) munkii: well, welcome to our ghetto anyway suseROCKs: munkii he's a Windows 3.1'er :-) jbrockmeier: munkii: I use GNOME on my laptop, and KDE on my desktop -- at least, I did when my desktop was still alive... :-) federico1: vuntz: we have a little bunch of bugs in apps... some dialog comes up in the wrong screen, etc. vuntz: federico1: nod federico1: vuntz: and (hint hint) the panel screws up sometimes ;) vuntz: federico1: really? jbrockmeier: federico1: OK -- when are you planning? I'd like to have at least a week ahead of time to start putting out announcements, etc. jbrockmeier: suseROCKs: you promised not to tell anyone! federico1: vuntz: well, the applets do. we had a bug or two on deskbar, the clock, etc. suseROCKs: :-) federico1: vuntz: http://en.opensuse.org/GNOME/Multiscreen vuntz: federico1: applets != panel. The panel is perfect. Everybody knows this ;-) jpr: jbrockmeier: yah, but that cuts a week out of feature time before beta1 rodrigo: jbrockmeier: can we add to the minutes you are a gnomer, at least "sometimes" :-) jpr: so i don't think its mandatory vuntz: federico1: I checked this a few weeks ago, most of the bugs there are xinerama bugs jbrockmeier: rodrigo: absolutely. I'm using GNOME right now, as a matter of fact. jpr: lets not get into a detailed discussion on specific bugs :-) jpr: federico1: so, next week on the file chooser? jpr: +1 jbrockmeier: jpr: OK, I'm just thinking from a promotion perspective... vuntz: anyway, federico1: I'm in for multiscreen or file chooser bugs federico1: jbrockmeier: I'd like to start next week - do you think you can get all those ads in Times Square and Piccadilly Circus on time? jpr: jbrockmeier: right, and i agree, better in future suseROCKs: +1 FunkyPenguin: nuts, /me needs to go - i'll mail regarding my questions on non-dev QA federico1: jpr: sounds good! ** federico1 starts writing an announcement ** munkii uninstalles kde4 rodrigo: -1, I'm on holidays, so will miss it :-( jbrockmeier: federico1: something like that. jpr: AI: federico to plan gtk file chooser hackweek jbrockmeier: federico1: what day? federico1: jbrockmeier: all week next week suseROCKs: yeah, what day is the week? :-) jbrockmeier: federico1: starting Monday? federico1: jbrockmeier: yeah, starting monday. Ping me offline for details :) jbrockmeier: groovy ** munkii doesn't know what the heck hes supposed to do in a hackweek jpr: munkii: test build service packages federico1: munkii: fix bugs, test fixes... suseROCKs: munkii its easy. As federico1 puts together a new patch, we download from his repo and tell him whether it worked. Then we move on tot th enext patch. federico1: munkii: I'll put up a page to explain how these hack weeks work ** munkii is glad pidgin's been fixed suseROCKs: really munkii? munkii: federico1: ok jpr: ok

Started at --> 19:45:08 suseROCKs: ok I don't think any of us has really focused on tasks lately with everything else going on. munkii: suseROCKs: yes, i suppose i can safely conclude this now suseROCKs: So for now, I'll just say, check the RTM and update whatever tasks you're assigned. ** rodrigo rtm's suseROCKs: And a quick question to everyone. Everyone happy with RTM? I hear Tasky integrates nicely with RTM ** sreeves taskys rodrigo: if it works with tasky, yes, I0m happy vuntz: suseROCKs: RTM ? suseROCKs: sreeves maybe you can briefly tell us how tasky improves on RTM? rodrigo: sreeves: where are tasky packages? suseROCKs: vuntz We have a Rememberthemilk.com setup jpr: i'm not so keen on RTM jpr: i prefer the wiki suseROCKs: vuntz and we're still working out the getting accustomed to RTM. I'm having a bit of trouble with it myself. jpr: awkward as it was sometimes sreeves: rodrigo: http://code.google.com/p/tasky/ ** munkii thinks it doesn't matter suseROCKs: +1 to jpr. I'm a bit uncomfortable with us leaving our own wiki to another place. vuntz: makes more sense to keep things on the wiki to me, yeah munkii: RTM can sync with evolution too, so no need for that tasky thing rodrigo: the wiki looks better, but doing it via tasky sounds quite good jpr: i think the other alternate is bugzilla jpr: like the project meeting uses vuntz: I can tell you it's hard for someone new to find everything that's relevant ;-) hmacht: sreeves: is it not stable enough to be put into the buildservice? or just because of lack of time? rodrigo: sreeves: package it!!! :) jbrockmeier: vuntz: +10 jbrockmeier: :-) suseROCKs: as vuntz points out, a newbie has alot to catch up on with accounts all over th eplace. jbrockmeier: speaking as a relatively newbie, it's definitely hard to get accountified everywhere you need to be. suseROCKs: munkii RTM integrates with Evo? I ddin't know that. munkii: suseROCKs: that's because your a n00b :P munkii: oh well, it does anyway suseROCKs: jbrockmeier and vuntz but on the flipside, The reason everyone moved to RTM was because we needed some automated task notification process. jpr: ok jpr: so jpr: how to move forward on this topic jpr: a few votes for moving back to the wiki jpr: but a lot of discussion munkii: vote! vote! vote! jpr: mailing list? jpr: is there enough consensus here? rodrigo: seems not :) vuntz: what does RTM provide? Automatic mails? suseROCKs: jpr I think its hard to vote because we have a positive benefit to both solutions. munkii: who's in favor of continuing with RTM? rodrigo: I guess having newbies having to create several accounts on N places sounds a counterargument for RTM indeed munkii: Raise your hand please federico1: I'd prefer wiki/bugzilla munkii: o/ rodrigo: we have notifications in the wiki now, so if we use RTM just for that... rodrigo: wiki +1 ivanz: bugzilla doesn't provide a good overview suseROCKs: wiki +1 jpr: +1 ivanz: wiki+1 vuntz: wiki sreeves: -1. I'd say give tasky a quick whirl before you vote - it does away with the awkward web interface jpr: ivanz: bugzilla would give search and rss feeds suseROCKs: Would ical of our gnome team work? Then we can track our tasks there? ivanz: still search isn't a good overview jpr: sreeves: i think its not currently pervasive enough munkii: i'm not in favor of the bugzilla/wiki solution because the login session expires too often vuntz: munkii: oh yes, I noticed this. That's annoying suseROCKs: munkii not for me. munkii: i awnt something that i can open while doing the task then close it just after i'm done federico1: munkii: people are working on moving them away from ichain jpr: ok jpr: so I'm hearing no strong proposals for keeping RTM jpr: and mostly agreement for wiki munkii: also neither can sync with evolution ivanz: There is a Greasemonkey script I use to log me in auto in bugzilla if you want it jpr: i propose moving off RTM back to wiki for now federico1: poor boyd; he went through so much trouble to set up RTM :) jpr: and further discussion on tasky jpr: does that sound right? sreeves: editing/updating/completing tasks is a lot easier on a setup that does not require manual cut and paste rodrigo: yes, although the wiki still has problems, like archiving tasks, etc jpr: true jpr: i'm just going off the voting above suseROCKs: rodrigo is the problem because we don't know of available plugins or because it simply isn't possible currently? jpr: suseROCKs: you run the tasks show, what do you believe is the best course of action? rodrigo: suseROCKs: because it's all done by hand suseROCKs: jpr I believe the best thing is a) give btimothy a chance to speak on this b) continue to use RTM at least for a few weeks and C) consider finding ways to achieve some ease on the wiki jpr: ok jpr: AI: suseROCKs to discuss RTM with btimothy suseROCKs: ok jpr: AI: suseROCKs and others to send RTM tips to the ML ** sreeves will post a link for tasky packages jpr: maybe we just aren't using it the right way jpr: AI: sreeves post tasky package link jpr: ok

Started at --> 19:57:29 jpr: just an update suseROCKs: and AI: suseROCKs to see if we can't find tools to amke this possible on wiki jpr: blew having a Feb theme meeting suseROCKs: I thought FOSDEM was the theme meeting? jpr: the consensus was build service jpr: after the X team couldn't meeting the next couple of times jpr: so unless anyone objects... jpr: AI: jpr to setup build service theme meeting

Started at --> 19:58:35 jpr: questions? vuntz: is this the time where I can ask tons of question as a user? :-) jpr: yes :-) ** suseROCKs actually has no questions this time. vuntz: cool suseROCKs: vuntz just remember, there's only 24 hours in a day. :-) vuntz: is there any place where I can get gstreamer plugins for factory? vuntz: or should I just forget about my mp3s? rodrigo: vuntz: see non-oss repository vuntz: s/about// ** rodrigo looks for it vuntz: rodrigo: it's still missing stuff for me jpr: packman is the other usual spot munkii: vuntz: download a mplayer source package, and use some frontend mediaplayer vuntz: and packman doesn't do factory :/ rodrigo: http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-extra/suse/ munkii: that's what i did vuntz: munkii: heh. I'm a totem user ;-) munkii: vuntz: not a time to get picky :P vuntz: and rhythmbox for music rodrigo: vuntz: yeah, I just installed a few packages from packman and then the non-oss repo rodrigo: for mp3s just install gstreamer_0_10-fluendo-mp3 rodrigo: or something like that vuntz: yes, that's the one munkii: vuntz: this is the best audio player around --> http://squentin.free.fr/gmusicbrowser/gmusicbrowser.html munkii: and you get to choose which codec backend you want to use rodrigo: gstreamer010-fluendo-mp3 munkii: including mplayer jpr: other questions? ** vuntz forgot what he wanted to ask munkii: jpr: will there be factory Q&A later?> vuntz: I'll ask later anyway jpr: munkii: now is fine suseROCKs: since this is non-dev and non-technical... I want to ask a question... suseROCKs: Can vuntz and jbrockmeier tell us quickly their vision (now that they're new) and how it pertains to our team? vuntz: suseROCKs: vision of? munkii: jpr: ok, whatever happened to the old yast-gtk installer proposal? jpr: munkii: i'm unclear about whats going on there, i have to track down ricardo suseROCKs: vuntz basically... what does it mean having you here. :-) vuntz: suseROCKs: that's a good question. I don't know the answer ;-) suseROCKs: Fair enough vuntz: suseROCKs: I know that, basically, I want openSUSE to improve on the desktop side suseROCKs: and jbrockmeier? jbrockmeier: suseROCKs: well, my "vision," so to speak jbrockmeier: is to do a couple of things munkii: jpr: ok, i can wait jbrockmeier: 1) Promote openSUSE and other Novell open source projects so they get the attention they deserve jbrockmeier: this means attending shows, encouraging developers to be more public with what they're doing (blogging, speaking, publishing articles, etc.) jbrockmeier: and generally marketing the heck out of the distro and projects that are going on in our community. jbrockmeier: 2) To make sure Novell is giving the community what it needs to make openSUSE the best distro possible and basically act as an "ombudsman" for the project. suseROCKs: jbrockmeier AI: Please blog/publish that Novell is also a partner in the new GOPA (Gnome outreach program for a11y) People need to know that Novell is a committed partner as well. jbrockmeier: 3) try to "grow" the community by bringing in more developers and work with upstream projects to make sure we have healthy relationships with upstreams. jbrockmeier: suseROCKs: sure. Have a link for this? vuntz: link for gopa: www.gnome.org/projects/outreach/a11y/ suseROCKs: wow vuntz is fast! vuntz: jbrockmeier: if you need help, I'm part of the organization team jbrockmeier: vuntz: I'm sure I will :-) mhwork|gone is now known as mhutch jbrockmeier: that's about it in a nutshell. suseROCKs: jbrockmeier I have heard some people assume that your role will facilitate better community relationship with Novell where previously they feel unheard. Is this a role you facilitate? jbrockmeier: as far as my vision, etc. jbrockmeier: suseROCKs: that's the idea, yes :-) suseROCKs: Lord have mercy on jbrockmeier for the onslaught from some people :-) jbrockmeier: suseROCKs: that's the ombudsman part jbrockmeier: suseROCKs: yes, I've been getting a ton of input jbrockmeier: so I hope folks will be patient with me as I try to get everything sorted. DimStar: I like the part: Promote openSUSE and other Novell open source projects so they get the attention they deserve... it would be nice if the Novell Tools would at least all be installable on openSUSE (like the NW Client.. bug report open for more than a year) jbrockmeier: DimStar: could you shoot me an email on that? DimStar: jbrockmeier: we're all nice people and patiant with you... don't worry :-) suseROCKs: jbrockmeier I realize you are likely swamped which is why I haven't bugged you yet. But rest assured, I intend to. jbrockmeier: with any specifics, I'll try to hunt down the appropriate parties. jbrockmeier@novell.com or zonker@opensuse.org suseROCKs: in a good way of course. jbrockmeier: suseROCKs: :-) cool suseROCKs: ok I'm done with my questions. (hands microphone back to jpr ) DimStar: jbrockmeier: I can also just add you as a CC to the bugreport if you wish... jbrockmeier: DimStar: please. suseROCKs: hmm... should we cc jbrockmeier on every bug filed? :-) jpr: other questions? munkii: yeah, when is dinner?

Started at --> 20:12:10 munkii: jk, move along ¬_¬ jpr: sreeves: take it away? DimStar: suseROCKs: I hope not for him :-) otherwise just make his mail address an alias to bug-bot sreeves: hrmm, I do not have an update on this, the combined update was submitted into the works jpr: it was on the testing site at least jpr: ok jpr: federico1: and the intel 945gm bug? its *still* not released afaict jpr: and people are still hitting it jbrockmeier: suseROCKs: let's call that plan B suseROCKs: hehe federico1: jpr: argh, I haven't fixed that gtk package in the build service - I should pull it out, since it's breaking people's boxes jpr: ok coolo: sreeves: your hours are long. It felt like 8h since you said "update within an hour" :)

Started at --> 20:15:51 suseROCKs: aww we have to listen to sreeves again??? :-) jpr: rodrigo, cyberorg : anything to report? jpr: hpj seems to be MIA in Norway atm rodrigo: jpr: no, still need to get more info on what's needed jpr: cyberorg is the man

Started at --> 20:17:06 munkii: compiz is acting kinda weird in A2, stable however munkii: sreeves: speak to us sreeves: ok, as coolo just hinted there is an updated version of PackageKit that will be submitted today sreeves: it is built against the new satsolver in libzypp rodrigo: cyberorg: tell me more about it after the meeting cyberorg: sorry, was occupied sreeves: which is very nice as it's quite fast cyberorg: compiz in factory is too old, needs an update suseROCKs: PackageKit does what? sreeves: there are still some issues though with the latest zypp packages sreeves: there are being resolved though munkii: sreeves: it's fixed now i think sreeves: PackageKit is a common GUI abstraction for installing/updating/removing packages on your box sreeves: by common I mean it's the same front end regardless of what backend you use - zypp, yum, apt ... suseROCKs: versus Yast sw_single? munkii: unless it's the one causing all the screwiness in zypper now lejo_: how will it relate to sw_single ? lejo_: both will be available ? suseROCKs: lejo_ and I think too much alike. I'm scared. sreeves: exactly how far it will be integrated into the stack is still under heavy discussion. sreeves: for now treat it as a technology preview jpr: its important to note though that it just uses libzypp jpr: so it works with anything else that does too jpr: ie zypper, yast, PK will co-exist jpr: (ie this is not zen vs zypp from 10.2 :-) sreeves: yeah, the will all just be based on top off ( and thus get the nice speed of) the new libzypp jpr: sreeves: anything else? sreeves: I think thats it suseROCKs: sreeves thanks for the explanation cyberorg: new libzypp is just great, using it since today, PK should do well using that munkii: it is kinda nice, but too many menu items, i was hopping you can group them, or make a multi-modular interface

Started at --> 20:24:08 rodrigo: ok, so patch upstreaming is going slowly, but no stop :) munkii: slow and steady wins the race \o/ rodrigo: I've started with the most difficult packages, so the others are free for everyone to see suseROCKs: I need to get going, and this is the part of the meeting where my eyes usually glaze over... so I'll catch you all later rodrigo: yu can see what captain_magnus did here: http://en.opensuse.org/GNOME/Projects/PatchUpstreaming/gnome-panel vuntz: I'll probably help with my upstream modules soon suseROCKs: Nice to meet you jbrockmeier munkii: no pictures =( rodrigo: so anyone having a look at patches can do the same, add a page with the status of their review rodrigo: and I'll go over these pages and submit / review for factory jbrockmeier: suseROCKs: thanks :-) rodrigo: of course, if you have direct access to autobuild, do it yourself :-) vuntz: do we have a strict policy for new patches? vuntz: ie, documented, with link to a bug, etc. rodrigo: vuntz: we should tag all new patches as stated in http://en.opensuse.org/GNOME/Patches rodrigo: btw, federico1: you're the best, nautilus has been a pleasure to review, with good comments, links to bnc/bgo bugs rodrigo: patches already upostreamed, etc vuntz: is it possible to enforce this with some check when uploading a new version? rodrigo: we should all be like federico1 when we grow up :) rodrigo: vuntz: we have osc plugins that perform the check, but nothing automatic to prevent it ** munkii wants to be a federico1 when he grows up jpr: anything else? munkii: rodrigo: where can we test nautilus patches? rodrigo: munkii: what do you mean? the patches I reviewed were already in the package, I was just tagging/upstreaming munkii: rodrigo: so they are already upstream? federico1: rodrigo: hahaha, thanks :) rodrigo: munkii: yes munkii: ok, cool rodrigo: in fact, we should follow all what federico1 does munkii: could use some working plugins though rodrigo: which is write the patch, add a comment about all code changes to the top of the patch file rodrigo: file the patch upstream if it needs to rodrigo: and tag the patch rodrigo: then, submit rodrigo: if we do all that from now on, we should have an easier-to-maintain package pool munkii: rodrigo: nobody is THAT perfect :P munkii: i can't even write a patch jpr: munkii: down to 3 problem extensions now, open-terminal, nautilus-share, gnome-mount federico1: yeah - for nautilus it was, I either do that, or I'll go crazy when the time comes to review what patches go where jpr: ok munkii: jpr: and image-converter (or whatever it was called) jpr: munkii: point me at it after the meeting

Started at --> 20:34:06 munkii: jpr: will do, moving along.. jpr: any other questions? munkii: what's everybody's feeling about this bug --> https://bugzilla.novell.com/show_bug.cgi?id=347156 bugbot: openSUSE bug 347156 in openSUSE 11.0 (Patterns) "gcc not distributed on the one CD media" [Enhancement,Resolved: wontfix] rodrigo: well, I guess one CD media is for "normal" users jpr: i'm surprised its on the ubuntu live cd rodrigo: yeah munkii: coolo deemed it unfixable, which i don't think is fair jpr: munkii: what you might want to do is review all the packages on the gnome cd jpr: and see what you would cut :-) munkii: it has nothing to do with what ubuntu has, gcc is need for us munkii: jpr: german translation? vuntz: I'd prefer to have more languages than a compiler on the cd rodrigo: yes vuntz: munkii: I guess if it's needed for you, a custom cd would work ** benJIman would like to have English on the CD :( vuntz: don't know if it's easy to create one, though DimStar: vuntz: the compiler can become pretty fast very important... think NVidia drivers, VMWare tools... jpr: benJIman: en_GB right? :-) benJIman: There is another English? jpr: en_CA hub: en_CA hub: :-) hub: and en_FR jpr: (says the two canadians) rodrigo: spanglish also is an english dialect jpr: DimStar, munkii : what kind of headers and stuff do you need as well? ivanz: there is only one true english hub: zis is ze french vuntz: DimStar: if our users need to compile drivers, we've already lost. If it's only for advanced users, they can install a package jpr: nvidia implies kernel sources jpr: which is big munkii: jpr: read my comments hub: 250MB the kernel-source jpr: i can't read them all right now :-) jpr: other questions? jpr: Thank you all! Meeting ended at --> 20:40:22

• AI: jpr and captain_magnus to collect agenda items on the mailing list by Tuesday
• AI: rodrigo to post install trick on wiki
• AI: federico1 to describe hackweeks in GNOME/Projects on wiki
• AI: federico to plan gtk file chooser hackweek
• AI: suseROCKs to discuss RTM with btimothy
• AI: suseROCKs and others to send RTM tips to the ML
• AI: sreeves post tasky package link
• AI: suseROCKs to see if we can't find tools to amke this possible on wiki
• AI: jpr to setup build service theme meeting