Speaker: jpr (06:03:41) jpr has changed the topic to: Meeting in progress - Introduction (jpr) jpr: welcome to the opensuse gnome team meeting! jpr: excitement is in the air! jpr: 11.0 is out +++suseROCKs hijacks the meeting to hoot "Three Cheersf or JPRa ndh is band of wily GNOMIES!!!!" jpr: bug reports are coming in (relatively few so far) jpr: things are looking good jpr: three cheers for everyone involved in fact hpj: cheers Repsa_Jih left the room (quit: Read error: 104 (Connection reset by peer)). vuntz: yay! suseROCKs: hey rodrigo_ what do I need to put in gobby for session password? rodrigo_: gnome suseROCKs: ok rodrigo_: please add the log, I'm onthe phone rodrigo_: bb in a second

Speaker: suseROCKs (06:07:01) jpr has changed the topic to: Meeting in progress - Helping Hands Update (suseROCKs) jpr: hobbsc: ... hobbsc: jpr: ? jpr: err jpr: suseROCKs: ... suseROCKs: hobbsc?!? suseROCKs: Why I never! +++hobbsc pushes suseROCKs out of the way suseROCKs: Ok I've been rounding up Helping Hands experts and hope to decide who will do what over the next three weeks in the next day or so. suseROCKs: Lakhil and Abharath will do Evolution suseROCKs: Thorsten and Rodo will do openOffice suseROCKs: hpj will do GDM suseROCKs: Is there anything you guys feel should particularly be the first or second session for our new users? mauropm [n=mauro@nat/novell/x-8e05a206bd55ba55] entered the room. jpr: maybe first setup tasks? jpr: printing? other usual config stuff? jpr: conduit for syncing? suseROCKs: does any of that fit in with GDM? jpr: i don't think so suseROCKs: ok jpr: many new users might not even see gdm jpr: because autologin is on by default suseROCKs: alright suseROCKs: How about this... suseROCKs: For the first session, a number of us show up for the purpose of talking about setup. jpr: (bluetooth, 3g cards, too) suseROCKs: As its likely to have alot of questions, and spreading the load would be easier. You all game? jpr: +1 jpr: (assuming the date/time is good) suseROCKs: that's the next subject. suseROCKs: So far, looking at stats, seems that Friday has the highest peak of visitors here. hpj: we could explain some of the neat stuff in control-center. i'd be all for that suseROCKs: Also, generally talking to volunteers, 14:30 UTC seems good for them. hpj: "get the most from your openSUSE" like suseROCKs: However, I am not going to hold fast to a 14:30 time each week. It all depends on the presenter's schedule. suseROCKs: can't ask a presenter to show up at 14:30 if its 3 a.m. local time. rodrigo_: why not? :) suseROCKs: But for next Friday. How about, we do an extended 2 hour Helping Hands Grand opening, covering miscellaneous getting started topics. rodrigo_: sounds good alphad left the room (quit: Remote closed the connection). alphad2 left the room (quit: Remote closed the connection). suseROCKs: Beginning at 14:30, which would be 9:30 a.m. for most of the US Gnomies here. suseROCKs: looks like no oppositions, so we'll proceed forth with that plan and I'llg et it announced. jpr: cool

Speaker: suseROCKs (06:15:59) jpr has changed the topic to: Meeting in progress - Wiki Cleanup (suseROCKs) suseROCKs: Next topic :-) jpr: suseROCKs: ... suseROCKs: short and sweet... SUSEhelp suseROCKs suseROCKs: I started to do some cleanup on the wiki, but realized how much daunting it was. suseROCKs: I'd like to ask for volunteers to join me sometime soon and we'll set out blocks of pages for each person to review and reorganize. jbrockmeier [n=jzb@12.45.241.98] entered the room. suseROCKs: Make it a Wiki day.  :-) rodrigo_: :) vuntz: makes sense suseROCKs: ok I'll send out an email next week announcing a day and those who show up get given a block. suseROCKs: Topic ends

Speaker: vuntz (06:19:43) jpr has changed the topic to: Meeting in progress - 11.1 Features (vuntz) jpr: vuntz: jpr: ... vuntz: http://en.opensuse.org/GNOME/Ideas/11.1 vuntz: we had a few people adding things there vuntz: we should probably put a deadline to propose new ideas and then start seeing who is interested in implementing what jpr: +1 jpr: testing/developing/documenting jpr: etc vuntz: yeah suseROCKs: well how far in advance would you consider a deadline to be effective? vuntz: when is the feature deadline for 11.1? Sometime in september? jpr: i'd like to see us emphasize continued polishing and improvements in 11.0 features jpr: at least prioritize though vuntz: jpr: +1 jpr: submission deadline sept 12 jpr: (esp pulse, multiscreen and packagekit) vuntz: suseROCKs: I was considering one more week or end of june for deadline for new ideas and then give us a week or two to organize ourselves suseROCKs: june?? suseROCKs: that's too soon imho hpj: suseROCKs: we need time to implement too hpj: suseROCKs: likely far more of it suseROCKs: But its already june 19th. jpr: only 3 months to deadline :-) vuntz: suseROCKs: you don't know what new thing you'd like to see in 11.1 yet? KevinYo: Mid-July would probably be better... like July 19th. 1 month rodrigo_: well, almost 2 weeks to decide on features, so that we can start in early july jpr: oh, that pulse ui is nice suseROCKs: give users a chance to use 11.0 and say "Hmm... you know what? We could use (insert here)" rodrigo_: jpr: yes :) hpj: i could agree on july 4th hpj: a friday suseROCKs: America's Birthday?? Sacrilege! suseROCKs: :-) KevinYo: I could agree on July 4th hpj: oh, yes it is hpj: easy to remember then suseROCKs: But yeah, I think that gives more reasonable time for us to submit ideas. rodrigo_: ok, July 4th is ok vuntz: then let's go for july 4th suseROCKs: off point but relevant ... is there a reason 11.1 is so soon on the heels of 11.0? +++jpr thinks we should finally get printing sorting out to jpr: (the configuration part) vuntz: jpr: yeah. Did you see the screenshots of system-config-printer from the soc student? jpr: yes jpr: i'm working on compiling it jpr: but i'm happy to hand it off so it actually gets one jpr: gets done jpr: for testing jpr: we tried it for 11.0 jpr: but i had too many concerns to change it vuntz: I'm sure captain_magnus would like to help here. He likes to be volunteered when he's not here ;-) jpr: hehe +++suseROCKs is excited to be migrating to a larger machine to do more testing this time around for the team. rodrigo_: :) vuntz: so I'll make some noise about getting new ideas until july 4th vuntz: can we consider that in one week, we'll be able to assign people to ideas? jpr: and getting support for features too +++vuntz is a bit concerned that the week after july 4th is guadec suseROCKs: moving along... jpr: Bug triage (jpr) jpr: http://en.opensuse.org/User:Jproseve/TriageProposal jpr: i floated this proposal last week jpr: you will see priorities assigned to bugs more and more in the future Iznogood [n=Iznogood@unaffiliated/iznogood] entered the room. jpr: so be aware that will drive the bug fixing order jpr: more and more jpr: comments on the page are welcome

Speaker: jpr (06:32:00) jpr has changed the topic to: Meeting in progress - AI Master Update (jpr)) suseROCKs: how are the feedbacks so far? Positive? jpr: i only checked from hobbsc so far jpr: and that was good jpr: ok rodrigo_: hmm, is captain_magnus aware of his new duty? haven't heard anything in response to my mail :) jpr: well, and novell devs like federico, rodrigo jpr: etc suseROCKs: he's aware rodrigo_: ok, good :) jpr: ok, i don't know what this topic is :-) vuntz: rodrigo_: he hit me hard for this, so he knows about it jpr: isn't suseROCKs the task master? suseROCKs: nuh uh. we voted captain_magnus the Task Master via bugzilla. jpr: aha suseROCKs: and rodrigo_ was supposed to get that set up on bugzilla. DID HE?!!? jpr: ok, will skip till we can hear from him SUSEhelp suseROCKs varadhan left the room (quit: "Ex-Chat").

Speaker: mw (06:33:50) jpr has changed the topic to: Meeting in progress - Build Service Repo (mw) jpr: mw: ... rodrigo_: suseROCKs: I mailed the people for that, but didn't get any answer suseROCKs: no no no no. Don't let rodrigo_ slip under the radar.  :-) mw: ahoy mw: so, i assume you have seen the mail i sent to opensuse-gnome@ about the future of repos mw: right now, GNOME:STABLE is empty, but i plan to repopulate it with gnome packages from 11.0 mw: (i figured better empty than obsolete) DimStar [n=dominiqu@videolan/contributor/dimstar] entered the room. mw: more interestingly is that we'll be moving to GNOME:Factory (not :UNSTABLE!) for ongoing gnome packaging/development mw: this time there's better support from the build service guys, so i do believe that we can make it go +++Iznogood thinks stuff like that should be mailed to announse ++ plain opensuse@ and even opensuse news, those of us following the gnome list and this irc chan is a too exclusive club mw: that's all i have to say, barring any questions mw: Iznogood: hmm, good point mw: Iznogood: kde will be making some similar changes, so we'll probably announce at the same time landonab: Hi all. can anyone tell me if there is any way to change the GNOME Computer Icon for SLAB to something else (custom icon)? I do not want to change the actual menu, just the 'computer' icon. landonab: I have dug through gconf-editor and what I have tried did not work. suseROCKs: A perfect question for our upcoming Helping Hands session  :-)

Speaker: suseROCKs/casualprogrammer (06:40:17) jpr has changed the topic to: Meeting in progress - How to set up a process of performance measurement (suseROCKs/casualprogrammer) suseROCKs: Unfortunately, we're in a meeting at the moment, so can you save that for the Q&A section coming up sorhtly landonab? jpr: landonab: there is no config setting for that, it uses a stock icon jpr: suseROCKs: ... suseROCKs: alright, this topic is really casual's and kinda got dumped on me this morning with no warning :-) suseROCKs: So I'll fill you in as much as I can. suseROCKs: Casual expressed an interest, and I support it, in developing coprehensive wiki pages for benchmarking/debugging/performance steps we can give our users so they can offer up more sound information on issues landonab: sorry for interrupting - thanks jpr suseROCKs: one tool we've come up with so far is bootchart. Very nice simple tool to install for users, but it only gives the performance info. suseROCKs: I'm reviewing a document written by federico lucifredi on such tools. rodrigo_: oh, I have a lot of ideas for debugging from mmeeks AlbertoP: suseROCKs, you see? He sounds italian! suseROCKs: But perhaps you all have ideas on good, easy to use tools, that users can use to provide you with more info on problems? rodrigo_: well, not for performance really suseROCKs: AlbertoP: he's Bostonian.  :-P AlbertoP: (no idea if he's :P) jpr: there was an opensuse-performance list at one point suseROCKs: or let me rephrase the question to you guys... jpr: it got shut down :-/ srinidhi [n=srinidhi@59.92.177.198] entered the room. suseROCKs: when a user comes in here or submits a bug with "I got a problem..." whats the one thing you really wish they would include? jpr: regular boot charting would be good suseROCKs: maybe write up a page on gdb? (looks at hpj) SUSEhelp suseROCKs jpr: we have a spot for that already right? jpr: Bugs:GNOME rodrigo_: suseROCKs: there is some info in GNOME:Bugs suseROCKs: rodrigo_: ok I'll take a look at that. dashua_ left the room (quit: Read error: 104 (Connection reset by peer)). vuntz left the room (quit: "leaving"). hpj: it'd be cool to have a script like the one the kernel guys use to collect information for bug submission hpj: we could have one that collects GNOME settings hpj: and related logs rodrigo_: yes suseROCKs: yeah, something users can easily set up. dashua_ [n=dashua@pool-71-169-77-183.cmdnnj.east.verizon.net] entered the room. hpj: like .xsession-errors and gdm messages from /var/log/ jpr: we had a tool that dumped gconf settings hpj: .gconf tree of course hpj: etc. jpr: and other information jpr: never sure what to do with it federico1 [n=federico@opensuse/member/Federico-Mena] entered the room. rodrigo_: submit to bugzilla, like bug-buddy? hpj: for starters, we could have another script to analyze the gconf dump hpj: which does a diff against the default gconf tree for a new user hpj: or something like that suseROCKs: and would all this be useful for you guys? suseROCKs: We figure, the more info you have, the more you can work on issues rather than querying users. hpj: yeah, it needs hacking investment, though KevinY1 [n=KevinYo@adsl-230-199-4.btr.bellsouth.net] entered the room. rodrigo_: yes, not always all the info would be, but it would be useful in most cases Swimnurd [n=Swimnurd@cpe-24-210-214-183.woh.res.rr.com] entered the room. hpj: the script is something we could push with 11.1, i guess suseROCKs: ok so where should we go from this point? Think about it a couple of weeks? add it to 11.1 ideas? come up with plans by next week? hpj: for 11.0 i guess we'll just need to educate users suseROCKs: ok rodrigo_: add it to 11.1 ideas under infrastructure sounds good to me suseROCKs: I just think that now's a good time to come up with some solution because now's about the time you'll get the new user-has issues period with the 11.0 release federico1: hmmmm, is this the right time to revive the idea of having a performance-monitoring mode, where apps would write some logs of what they are doing to analyze them later? suseROCKs: and AlbertoP ALWAYS finds something.  :-) rodrigo_: federico1: yes AlbertoP: suseROCKs, ? suseROCKs: I'm sure you guys all know Lucifredi, right? KevinYo left the room. suseROCKs: ok awkward pause here federico1: rodrigo_: ok :) I've always wanted to do that federico1: suseROCKs: yes - he has a beautiful name suseROCKs: hehe federico1: he runs a low-traffic mailing list about performance issues suseROCKs: well he wrote an amazingly beautiful document last year for LinuxWorld. You need to ping him to get that document. suseROCKs: ok next topic? suseROCKs: jpr went awol? KevinY1 left the room. jpr: crap jpr: sorry

Speaker: casualprogrammer (06:58:22) jpr has changed the topic to: Meeting in progress - Agenda for upcoming meeting (casualprogrammer) jpr: 11.1 features obviously jpr: other agenda items? federico1: suseROCKs: pinged! suseROCKs: HH update jpr: other stuff? jpr: federico1: multiscreen update by then? federico1: jpr: sure federico1: hmm

Speaker: jpr/All (06:59:23) jpr has changed the topic to: Meeting in progress - Q&A ok jpr: err suseROCKs: oh yeah... federico1 doesn't know it yet, but he's been drafted to be a multiscreen Helping Hands Expert. jpr: rodrigo_: pulse update? dashua [n=dashua@pool-71-169-77-183.cmdnnj.east.verizon.net] entered the room. federico1: suseROCKs: hehe, no problem :) rodrigo_: well, a new bug came in today, about pulseaudio being run by yast and borking the user's daemon rodrigo_: I'm investigating that rodrigo_: apart from that, it should be working rodrigo_: anyone has seen any problem? jpr: rodrigo_: i meant next week - on glitch free and stuff jpr: ok rodrigo_: ah :) jpr: QUESTIONS jpr: go go go suseROCKs: So what is this 11.0 thing I keep hearing about? jpr: :-) jpr: ok jony: i would like to know how to get a package into gnome:community repo .. quick google didn't turn up any page :) jpr: if everyone has any time to join #suse it would be great to help out newbies Riggwelter: jony: you have to give me money +++rodrigo_ didn't pay Riggwelter to get python-nautilus in :) rodrigo_: oh, amybe I should shut up... Riggwelter: rodrigo_: Invoice is in the post :) rodrigo_: grr jony: hehe ... suseROCKs: Later guys! Iznogood: well I tried emailing Riggwelter some cash a while ago, still didn't get my package in :P Riggwelter: Iznogood: Package? Iznogood: evolution-rss +++Riggwelter has 2 mins before bathing Rigg Jr rodrigo_: jony: there's an inclusion policy, see GNOME page on the wiki Riggwelter: Iznogood: It's there isn't it? (I don't recall an email about it) jpr: Riggwelter: you can use the new BS foo jony: rodrigo_: ah k .. /me google on the wiki .. Riggwelter: jpr que? Iznogood: :) think I emailed both you and mw about it jpr: Riggwelter: the submitreq stuff jony: i just started using guake .. looks nice .. would be great to be in repo .. Riggwelter: Iznogood: I suspect GMail may have munched it mw: jony: not yet mw: err, jpr: not yet hpj: jony: the GNOME page is http://en.opensuse.org/GNOME/ Riggwelter: jpr I'll look into it - thx hpj: but the wiki appears to be slashdotted mw: jpr: you can't submitreq a package when it doesn't exist in the target repo mw: jpr: but it's a known issue and they're working oni t jpr: ah Iznogood: Riggwelter: you can check it out at /home:zaitor jpr: darn jpr: last call for questions! Riggwelter: Iznogood: I think it's already been imported but ok Iznogood: Riggwelter: I'll have a look to see if its there now Iznogood left the room (quit: Remote closed the connection). Iznogood [n=Iznogood@unaffiliated/iznogood] entered the room. Iznogood: could be me making a fuzz about nothing + I have a pidgin bug to report Riggwelter: Iznogood: Nope, not there, thanks for the heads-up jpr: thanks all! see you next week!