Started at --> 08:06:16 jpr: Welcome to the openSUSE GNOME Team meeting! federico1: jpr: SEND HOT PIX jpr: Today will be our monthly meeting the moves to 12 UTC to try and better accomodate Asia and Australia. *AvengerMoJo (n=alex@61.14.130.203) has joined #opensuse-gnome jpr: I already see some people from those place: dliang, srag, AvengerMoJo, jony (I think cslcy ) :-) jpr: so welcome srag: thx jpr jpr: hopefully this is a time we can stick to once a month AvengerMoJo: ;) jpr: srag for those who don't know, is the evolution maintainer jpr: so prepare your questions for Q&A :-) AvengerMoJo: ;) srag: sure :) jpr: lets move to the next agenda item

Started at --> 08:08:15 jpr: federico1: take it away on the bug plan federico1: sure federico1: so, the bug plan on http://en.opensuse.org/GNOME/Bugs is practically done federico1: we have some criteria to classify bugs based on whether they prevent you from getting work done, and some categories which we can use to tag bugs as appropriate federico1: then, that page has links to bugzilla queries which we can use to find bugs based on those categories federico1: the next task is to finish going through the bug list, tagging each bug as appropriate federico1: something for boring afternoons :) AvengerMoJo: ;) federico1: we plan on having "bug topic days", where we try to fix bugs around the same topic: all the multiscreen bugs, all the bugs around editing photos from a camera, etc. federico1: but so far only mboman has signed up for the multiscreen bugs... does anyone else use Xinerama? jpr: i will have a dual screen setup in a couple of weeks jpr: maybe sooner jpr: so i will volunteer federico1: jpr: cool *btimothy uses dual screen but by no means do i know how it works...magic? ;) jpr: federico1: anything else you would like to mention about the bug plan? jpr: (i have a few questions after) federico1: oh, one more thing Riggwelter: Sorry guys, I have to rush out, hope maw's able to take our item when it gets to it. federico1: we have a special category for accessibility bugs. So if you find a bug in gnome's accessibility software (there are tons of them!), or an application with accessibility problems, *please* file a bug and tag it with "gnome-accessibility" in the Status Whiteboard jpr: ok jpr: questions on the bug plan? hpj: so it can be assigned to me federico1: accessibility can be as simple as "this stupid app changes its menu's font size along with the rest of the system, but its toolbars remain with tiny text" *mw|out is now known as mw- mw-: morning federico1: hpj: :) jpr: federico1: why is showstopper 3rd in priority jpr: ? jpr: or is that just the query order federico1: jpr: huh? jpr: under " Bugs in openSUSE 10.3" jpr: federico1: maybe those should be listed in priority order? federico1: oh, yeah, that's wrong federico1: the "fixing bugs" section has them in the right order :) jpr: federico1: and for priority, does severity play into it at all? *federico1 fixes jpr: like can a critical function does not work jpr: rather federico1: jpr: yeah, within each category I'd like to fix things in order of severity jpr: ok jpr: but each category completely jpr: before the next? jpr: so all showstoppers federico1: or something like that... a Critical bug in wrong-out-of-the-box is probablymore important than a Minor in gnome-function-does-not-work jpr: then all wrong out of the box jpr: ok jpr: federico1: and how does voting influence things? federico1: oh yes, voting! federico1: so *mw- is now known as mw federico1: we want to use the voting feature in bugzilla to help find bugs which people care about. Something may be super-annoying to some people; we want to find those bugs by having them vote for them. *btimothy wishes the voting UI in bugzilla was more visible hpj: voting for bugs is fun! dliang: hehe federico1: for example, there are 13 votes for a way to disable beagle during installation... hpj: which makes you wonder if beagle shouldn't be disabled by default, perhaps captain_magnus: Beagle is good for some of us hpj: yeah, digression mw: beagle makes emotions run high :) jpr: federico1: so how do the votes overlap with the other priorities captain_magnus: Just because some people votes against it, doesnt mean that everyone wants it disabled... jpr: federico1: are they their own category, do they influence prioritization? captain_magnus: hpj: As long as we dont vote for "for and against" we can not make those decicions... federico1: jpr: I'd like them to influence prioritization jpr: ok jpr: maybe we should indicate that on the page? federico1: jpr: there's a highly-voted bug for opensuse 10.2 where something doesn't work on audacity... I would never have thought so many people did audio editing (podcasters?) hpj: captain_magnus: it was just an idle speculation, i shouldn't have said it federico1: jpr: yeah, let me put that in captain_magnus: hpj: Heh... Didnt mean to shut you up... Just saying... No offence... :-) jpr: ok jpr: any other bug plan questions? hpj: captain_magnus: some bugs are better fixed not in the way the submitter suggests (though maybe not that one) jpr: federico1: i have one - how does prioritization of 10.2/10.3/11.0 and features work? hpj: captain_magnus: which was my point, mostly *Panzerboy (n=gigi@unaffiliated/panzerboy) has joined #opensuse-gnome captain_magnus: hpj: I agree with you... *captain_magnus laughs as jpr puts federico1 in the hot seat... Panzerboy: hi all jpr: hi Panzerboy federico1: jpr: that's not completely clear from the page... I think we should fix 10.3 bugs first, then find a way to push those fixes to 11.0 so we don't forget, then go with 10.2 bugs captain_magnus: Hey Panzerboy... Meeting in progress... jpr: federico1: and over time focus more on 11.0 ? federico1: jpr: yeah, when betas start becoming available captain_magnus: Betas or Alphas? jpr: federico1: i think it needs to be well before that captain_magnus: Once we are in Betas, it is almost to late...? jpr: waiting to betas is what causes all the problems jpr: and allows us to get very little upstream federico1: are alphas publically accessible_ federico1: ? jpr: yes federico1: ok jpr: and in factory factory is available right now :-) jpr: Ok, I think this is a great bug plan, we just need to be careful about balancing votes vs priorities, cleaning up whole groups of bugs and 11.0/10.3/10.2 jpr: When should we move to using it? Right now we are working off severity only for 10.3 jpr: and that was planned to continue until Nov 9 jpr: should we finish that off and then move to the bug plan? federico1: jpr: I really want to finish tagging the bugs for 10.3; that along with severities should give us a good idea of the order in which to fix things jpr: along with some new feature/integration work? captain_magnus: jpr: federico1Ö Question for you... captain_magnus: Why do we not introduce a new version captain_magnus: or fix an issue in products that are (apparently) making some stuff unusable captain_magnus: Is that all up to the PM for 10.3, or do you have any say? jpr: captain_magnus: that is a distro wide policy, you will have to take it up with coolo and the board jpr: we have a little influence captain_magnus: jpr: Would you agree that it is sometime a problem? jpr: but not that much :-) jpr: yes, sometimes it is *Panzerboy has quit ("leaving") *btimothy doesn't favor the policy jpr: and we do make exceptions occasionaly jpr: like firefox captain_magnus: Ok, great... So is anyone willing to work with me to change that policy somehow? captain_magnus: Especially when there is a huge problem or a big demand? federico1: captain_magnus: that's something the bug plan is supposed to handle already... cyberorg: captain_magnus, there is a danger that every maintainer would want the latest versions of their packages pushed jpr: captain_magnus: alberto is i think federico1: captain_magnus: oh, you mean actually publishing a newer version of a program for an old version of opensuse? btimothy: captain_magnus: yeah, how do you draw the line and say enough is enough? captain_magnus: jpr: I am thining of him when I ask this! :-) *Panzerboy (n=gigi@unaffiliated/panzerboy) has joined #opensuse-gnome cyberorg: i would like to see current compiz git pushed in updates as it fixes many bugs :) captain_magnus: I dont know how you draw the line... jpr: what really needs to happen is a clearer policy jpr: on when it can and can't happen jpr: it can't turn into a free for all captain_magnus: I know that we have people in our community that needs a new version for whatever reason captain_magnus: or we need to push a new version to make a feature work btimothy: i'm guessing it will be better next time around since we're a bit more involved now btimothy: (early on) jpr: captain_magnus: if you take this up, I would suggest you push/propose a policy for when its acceptable jpr: also true what btimothy said jpr: some of the gnome stuff could have been fixed if we'd worked on it a couple months earlier captain_magnus: jpr: btimothy: Ok... I am happy with that... To bad albertop isnt here :-( jpr: ok jpr: lets close this out jpr: actions for federico jpr: AI finishing tagging bugs (and people who want to help him) Nov 9 ETA jpr: AI Add 11.0 categorizations jpr: anything else? jpr: ok

Started at --> 08:39:51 jpr: mark is not here today jpr: however jpr: http://en.opensuse.org/GNOME/BugDays/20071102 federico1: ok jpr: will have a lot more info for the ancient distro bug squash day tomorrow jpr: federico1: great job by you and rodrigo btw btimothy: would be good to send out a mail abt. that to the list captain_magnus: jpr: Isnt that a surprise... Was that announced and I missed it? (The bug day) jpr: yes jpr: i've been waiting for some more info on the page jpr: like how to get involved jpr: hopefully mark will put that up today btimothy: will mtgordon be here tomorrow? jpr: and we'll continue jpr: yes, he's supposed to be btimothy: k jpr: although he's been ill :-/ btimothy: bummer jpr: so maybe one of us will have to pick it up

Started at --> 08:42:19 *btimothy wakes up...breaks out the "get 'er done" whip... btimothy: alright ... btimothy: first of all, if you haven't taken the chance to look at the tasks page recently ... btimothy: i'd encourage you to do so right now and first off, look for your name btimothy: http://en.opensuse.org/GNOME/Tasks btimothy: :) captain_magnus: http://en.opensuse.org/GNOME/Tasks btimothy: and, if you find your name, please make sure that 1) there's an ETA of when we can all expect to see your good work done captain_magnus: btimothy: Your name is all over the place :-) btimothy: 2) update the status *btimothy hides btimothy: i need to review the list just as much as anyone else btimothy: this is why i suggest for everyone to conciously review the page today hpj: btimothy: "The Code page" is the list of people/expert areas, right? btimothy: not entirely sure btimothy: hpj: can you offer insight to the first item? hpj: btimothy: the "Add yourself to the team page" task for me - I did that ages ago :) hpj: btimothy: so that can be closed btimothy: hpj: ah, cool. you can move it off the page or down to the bottom section :) hpj: btimothy: ok *AlbertoP (n=AlbertoP@host37-75-dynamic.11-79-r.retail.telecomitalia.it) has joined #opensuse-gnome captain_magnus: Ok, as a spokes person for myself, jpr and cyberorg... We are waiting for "God"... We can not do to much with the feature requests at the moment... :-( btimothy: riggwelter ... GNOME Community Repo INclusion Polkicy Page? btimothy: ah, guess he left, right? :( hpj: btimothy: if "the Code page" is what I think it is, it's a list of people and what kind of questions they can generally answer about development btimothy: hpj: ah, right! hpj: btimothy: like "hpj: did a bunch of GNOME a11y stuff" jpr: captain_magnus: i did see some test info go by internally, i think its close btimothy: hpj: how 'bout setting a deadline and starting the page off? then poke the appropriate people, send out an emailt/etc. jpr: hpj: actually its not, but that AI should go up there too hpj: btimothy: yeah, hopefully i can get to it start of next week btimothy: doh! jpr: hpj: its a where code-for-our-modules-should-go jpr: page jpr: but we need to do both hpj: jpr: there's also a " Determine where to keep openSUSE specific GNOME code" item btimothy: in any case, we shouldn't really have tasks listed on the page without an ETA hpj: jpr: so they're both part of the same task? jpr: oh jpr: maybe jpr: hpj: at any rate, need some clarification hpj: yeah *jpr agrees with btimothy btimothy: just update the task descriptions btimothy: i think the Tasks page suffers from neglect (and i haven't helped that situation) btimothy: federico1: looks like as of today the Bug Plan is gonna be entirely done? btimothy: federico1: if not, can you update the ETA on that one? btimothy: sbrabec: how's merging 10.3 packages -> gnome:stable? on time? btimothy: jpr: update on feature request submissions? i don't see an ETA there either? federico1: btimothy: yeah, I'm editing it... just got a mid-air collision :) jpr: btimothy: it will add it dliang: I think voting is much more useful in feature requests than in bugzilla jpr: currently its blocked sbrabec: btimothy: jpr: Running simple script. Manually (because it often needs fixes), about once daily. Including pending submitted pacakges. jpr: sbrabec: are we ok on 10.2 now? sbrabec: jpr: 10.2 nearly yes. 10.1 no. hpj: dliang: which is actually an interesting argument for using bugzilla for feature tracking :) jpr: dliang: yes, but voting on bugs does help people show just how annoying the bug is :-) sbrabec: jpr: see https://build.opensuse.org/project/monitor?project=GNOME%3ASTABLE jpr: sbrabec: will you continue to maintain G:S? jpr: sbrabec: if so, will you push GNOME 2.20.1 there? jpr: since in STABLE we will move to gnome 2.21.x shortly? btimothy: jpr: sbrabec: can each of you (when the changes settle down on the page) update the status column in your tasks? jpr: yes btimothy: thanks btimothy: i poked the bug abt. getting email notification ... a few minutes ago jpr: sbrabec: also, this is really impressive btimothy: captain_magnus: glossary? sbrabec: btimothy: jpr: Yes, I will maintain G:S. Please, anybody: If you will start to move to 2.21, please let me know before it. jpr: mw: ^^ jpr: sbrabec: thank you btimothy: captain_magnus: not started, no ETA, should the glossary task be up for grabs? captain_magnus: Oh shit... Nothing... :-( I will talk to rodrigo_out as soon as I can btimothy: captain_magnus: ...and update the tasks page with your plan ;) captain_magnus: I will btimothy: jpr: boxed openSUSE ... update ETA/status btimothy: captain_magnus: thanks sbrabec: jpr: When Factory will start to move to 2.21, I'll stop syncing. Feel free to ping me to sync particular package or package subset. dliang: hpj: Is there any way besides bugzilla that I can do the feature request and get noticed by the developer? btimothy: captain_magnus: meeting items still need to be there? jpr: sbrabec: ok captain_magnus: Dont know... We all need to decide if we are happy with the way the meetings are conducted... jpr: btimothy: yes, they will all be done in hte discussion right ofter this btimothy: captain_magnus: experimenting with the meetings thing is still kind of ongoing i guess? btimothy: captain_magnus: maybe change the ETA to ongoing? captain_magnus: Will do... *gothica (n=pavel@87.251.157.6) has joined #opensuse-gnome btimothy: and perhaps we ought to organize the tasks page to split out the sections? btimothy: AI -> boyd -> organize the tasks page hpj: jpr: see dliang's question above btimothy: munkii not here? btimothy: mw: eta on kde team packaging policy? jpr: dliang: right now its a bit messy, we are trying to sort out as a project how to get that handled cyberorg: dliang, hopefully we will have something soon *btimothy whips self to add ETAs *mw has to think about that jpr: dliang: for now try fate internally or bugzilla.novell.com enhancement jpr: dliang: if its just an idea for gnome jpr: http://en.opensuse.org/GNOME/Ideas/11.0 btimothy: rodrigo_out: ah, not here ... you've got a couple items near the bottom of the list that were done a few days ago? ;) btimothy: mw: you posted the sample package already...mark this task as done? jpr: dliang: that a place holder while we get things sorted out jpr: btimothy: holiday in spain *captain_magnus thinks we need AlbertoP to be responsble for a task... sbrabec: jpr: I want to mention progress with my pkg-buildrequires: jpr: sbrabec: please do btimothy: holiday/schmoliday! ;) *AlbertoP reads back ^^ captain_magnus: AlbertoP: http://en.opensuse.org/GNOME/Tasks mw: btimothy: no, not yet, 'cause i want to post a sample library package too sbrabec: pkg-buildrequires sbrabec: This package provides a way to automatically maintain RPM BuildRequires sbrabec: introduced by pkg-config dependencies. sbrabec: Because it is not possible to update BuildRequires from build log sbrabec: directly, it must be done in two passes: sbrabec: 1) Run configure and analyze results. btimothy: mw: ah, please update that info in the task sbrabec: Compare requirements results with requirements actually uses. sbrabec: Fail if it does not equal. sbrabec: 2) Update BuildRequires of spec file. mw: btimothy: i already did sbrabec: Run build again. sbrabec: Sources: sbrabec: http://pack.suse.cz/sbrabec/pkg-buildrequires/ sbrabec: OBS: sbrabec: https://build.opensuse.org/package/show?project=home%3Asbrabec&package=pkg-buildrequires sbrabec: RPMs (noarch): sbrabec: http://download.opensuse.org/repositories/home:/sbrabec/ btimothy: mw: ah ha! during the meeting. ;) jpr: sbrabec: ok, i have some q's, but I'll save that for the developer section later :-) btimothy: mw: still no ETA? jpr: btimothy: ok, ready to finish up the whipping? btimothy: mw: i.e., when should we bug you abt. it again btimothy: yeah. done btimothy: AI -> boyd ... *jpr has changed the topic to: Meeting in progress - Q&A - Non Developer | http://en.opensuse.org/GNOME/Meetings/20071101 | http://en.opensuse.org/GNOME mw: let's say before next mtg jpr: Q&A captain_magnus: btimothy: Good work! btimothy: send out mail after finished reorganizing tasks jpr: questions from anyone jpr: anyone at all captain_magnus: jpr: Q&A from the meeting page? *jpr notes btimothy is a much better irc whipper than i am AlbertoP: captain_magnus: hmm you mean the "review the wishlist" ;-) btimothy: hah! jpr: Q: Can we please review/comment/approve/deny http://en.opensuse.org/Wishlist_Gnome in one of these meetings jpr: A: Yes, i scheduled it for today, but i think we may need to punt until next week captain_magnus: jpr: Can we make AlbertoP in charge of that one? :-) jpr: sure jpr: AlbertoP: ? AlbertoP: yup captain_magnus: Awesome... jpr: ok, other questions? AlbertoP: two :-) jpr: go AlbertoP: the first one is about our GNOME: repositories captain_magnus: Who attended this meeting today, that could not (due to time) otherwise? captain_magnus: Me :-) AlbertoP: for what I unserstand KDE has :BACKPORTS, which is somewhat similar to :STABLE, but they found it on the existing distribution AlbertoP: why don't we do something similar? mw: what's the difference between :BACKPORTS and STABLE? sbrabec: I also have a question on GNOME:STABLE for 10.1: Is it important enough to spend days by fixing it? jpr: AlbertoP: we build stable on 10.2 and 10.3 and 10.1 is in progress thanks to sbrabec captain_magnus: sbrabec: I vote NO mw: sbrabec: i'd say no jpr: although maybe we won't do 10.1 :-) AlbertoP: backport should be a set of new apps packaged on the released distribution, while stable is packaged on a newer set of libs/gnome stuff I think cyberorg: 10.1 is of interest to many due to being a same code base as sle jpr: AlbertoP: ah mw: maybe those could go in G:C? AlbertoP: jpr: well, this is a sort of intepretation, better we ask to some K guy before AlbertoP: benJIman: ? captain_magnus: Guys, If you like this time for the meeting, speak up, or we will have to scrap it... jpr: yes, its just apps jpr: AvengerMoJo, dliang, jony, srag would you be here with out this meeting time? AlbertoP: second question, is the patch policy jpr and me shortly discussed on ML: it would be a good thing to have essential only patches even if not security related (read evo with backup stuff, anjuta, ...) :-) jpr: AlbertoP: so i think the answer to your question is - we've never thought about it srag: jpr, We would love to, but it becomes difficult as the other timing is too late in the night jpr: AlbertoP: please propose on #opensuse-gnome if you want dliang: I like the time. I'm fine if you change it. jpr: srag: right, so this time change once a month would help you attend AlbertoP: jpr: ML? mw: what time is it in straya right now? jpr: AlbertoP: err, yes srag: jpr, yep captain_magnus: mw: Just after midnight jpr: AlbertoP: yes, discussed earlier, captain_magnus would like to work with you to proposal a formal policy on version updates for the project captain_magnus: I really enjoyd not having to sit up until 2-3 in the morning to participate... jpr: Any other questions? AlbertoP: jpr: ok, thanks captain_magnus: AlbertoP: Guess it is up to you and me to try to get a good policy in place :-)

Started at --> 09:11:45 jpr: ok AlbertoP: captain_magnus: I have very little hope, but we must try :-) jpr: so we've experimented with our meetings over the last 3 weeks jpr: and we have a few questions to answer jpr: 1) Does splitting up in dev/non-dev work captain_magnus: AlbertoP: Be positive... Read through what we said throughout the meeing jpr: 2) Do timings work jpr: 3) Do themes work? If so how often do we have them? AlbertoP: captain_magnus: I'm positive, the problem is not there ;-) jpr: 4) Is shifting the time once a month good captain_magnus: jpr: I think 1) Really good... 2) Really good... 3) Really good... 4) Really good.. jpr: 5) Is adding urls to the action items good captain_magnus: So.. +1 +1 +1 +1 = 4 jpr: 6) Agenda items in irc topic captain_magnus: Not sure about 5 since noone seems to ready the agenda jpr: 7) Task review FunkyPenguin: the time shift is definately a good idea jpr: lets start at the top :-) jpr: 1) ? jpr: what do people think? hpj: jpr: I think 1) should be answered by non-devs captain_magnus: I loved btimothys work on 7! captain_magnus: +1 FunkyPenguin: 1) works for me btimothy: yeah, i like the non-dev/dev separation for the mtg. btimothy: +1 jpr: AlbertoP, captain_magnus ? jpr: others? FunkyPenguin: jpr: what do you think? captain_magnus: 1) +1 AlbertoP: I agree with captain_magnus jpr: ok jpr: lets keep it jpr: 2) jpr: i must say I'm guilty of not enforcing these hpj: definite +1 from me, although we need better enforcing jpr: because I'm loathe to cut off a good discussion jpr: the biggest side tracker jpr: has been the bug plan discussion AlbertoP: it seems ok for me mw: i think it's better to let good discussion go than to cut it off captain_magnus: Timings do not really work, but I am really happy that we dont stress to push on as they do in the openSUSE status meetings jpr: but that is really critical to our success dliang: 2) +1 for me. btimothy: i think it's good to have the time limits, but ... i tried to quickly go through _all_ of the tasks and ... it went for over double the allotted time? *FunkyPenguin agrees with mw jpr: maybe we should keep them a relative guidelines? captain_magnus: jpr: If its critical, then I can not agree that we have a 1 hour meeting... jpr: and pressure on the moderator to keep the focus in the channel :-) captain_magnus: We never managed to keep it *metavoid has quit (Read error: 110 (Connection timed out)) captain_magnus: And by the looks of it, we will only stress it if we do captain_magnus: How about 1 1/2 instead hpj: as long as people don't start dropping out of the meeting towards the end jpr: i'd still like to try an hour btimothy: i think if anything, the times help us to flesh out an agenda btimothy: keeping the meeting at an hour target is good ... jpr: it definitely narrows the agenda week to week jpr: i propose this then: jpr: a) keep the timings btimothy: i think we will get better each time (hopefully)? jpr: b) be lax on enforcement jpr: yay/nay? btimothy: +1 btimothy: if it gets extremely out of hand, we can always readjust later jpr: any objections? captain_magnus: jpr: *try* to go for 1 hour? If so, +1... But dont enforce it mw: sounds good FunkyPenguin: snaye from jpr: captain_magnus: yes jpr: FunkyPenguin: ? FunkyPenguin: um that should be an aye from here jpr: ok :-) hpj: yeah, let's try for an hour jpr: 3) themes and how often? jpr: i personally liked the theme hpj: and let people internalize the enforcement jpr: especially getting other people outside gnome involved jpr: i could see having an evo theme Dec 6 for instance FunkyPenguin: definately jpr: with srag *btimothy likes themes when appropriate, but doesn't have to be every meeting FunkyPenguin: once a month would be good hpj: i liked the theme dliang: 1 hour is a little short for me, I need to warm up before the meeting.. captain_magnus: I think themes shoud only be once a month... captain_magnus: Reason is that we want experts to join us srag: jpr, sure. jpr: dliang: hehe captain_magnus: If we have it more often, then it could be hard to get those experts jpr: ok jpr: sounds lie yes jpr: and once a month jpr: 4) time shift once monthly jpr: (thank you to hpj, federico1 and btimothy who got up *really* early) btimothy: 5a might be pushing it when that time comes, btw btimothy: ;) *AvengerMoJo has quit (Connection timed out) mw: the times are always convenient to people in europe srag: :) captain_magnus: +1 for time shifting federico1: np dliang: 4) +1 mw: down with the eurocentricism!! ;) hpj: damn europe for being in the center jpr: i think we got hurt a little by india being on holiday jpr: but we should do this at least a couple more times jpr: any opposed? *AlbertoP feels in the centre of the centre ^^ btimothy: jpr: can i answer you this afternoon? ;) srag: :) jpr: btimothy: hehe *btimothy should be good for another couple tries jpr: 5) Urls jpr: +1 from me captain_magnus: +1 jpr: seems like a no-brainer btimothy: yup. next. jpr: 6) Agenda in #topic jpr: seems like another no brainer mw: +1, obvious :) hpj: +1 on 6) jpr: i think btimothy had that brainstrom captain_magnus: +1 jpr: so good job btimothy: heh, i was watching another irc meeeting the other day ... btimothy: and they didn't have that ... jpr: 7) Task review in the meeting btimothy: how confusing ;) captain_magnus: AlbertoP: I dont see any -1... Whats going on? :-) captain_magnus: 7) +1 hpj: 7) +1 AlbertoP: captain_magnus: I'm positive :-) captain_magnus: AlbertoP: Not positive enough to say +1? :-) jpr: +1 with the caveat that btimothy should a) take this over b) prod people the day before the meeting to update btimothy: uh oh btimothy: ;) btimothy: i should have stayed in bed ;) 09 <jpr: spread the love 09 <AlbertoP: captain_magnus: if you don't see -, don't worry about my vote :-P btimothy: i think we can definitely cut down the time it takes with a little planning ahead of time btimothy: and reorganizing the page a bit btimothy: so +1 jpr: AI Magnus to write up these decisions on http://en.opensuse.org/GNOME/Meetings jpr: to flesh out our meeting policy a little more jpr: go captain meeting jpr: with that I move that since we really don't have the right people for the next to items jpr: we have final Q&A and wrap up jpr: (and its been an extra long meeting) jpr: (those up so early are typing slowly) federico1: btw, I just noticed that the main GNOME page didn't have an updated meeting time jpr: oops jpr: my bad

Started at --> 09:29:38 jpr: any other questions/comments/concerns? *jony has quit (Connection timed out) jpr: ok, thanks everyone! AlbertoP: just one clarification on my tast with wishlist: what should I do? AlbertoP: :)

jpr: this meeting is over! Meeting ended at --> 09:30:44