GNOME/Meetings/20080522/transcript
From openSUSE
Introduction
Speaker: jpr
(06:01:53 PM) jpr has changed the topic to: Meeting in Progress - Introduction (jpr) jpr: Welcome to the openSUSE GNOME meeting! uberChick: Thanks, I just wanted to mention it depending on randomness like... um... wheeling to lil girls room. suseROCKs: FunkyPenguin: I'm not feeling any love here! jpr: the march to RC1 is almost complete FunkyPenguin: :x jpr: 27 days to go +++uberChick *hugs* suseROCKs & FunkyPenguin hobbsc: alright suseROCKs: I knew having uberChick here would be a good thing. jpr: Then on to the bigger and sure to be better 11.1! hobbsc: we hope jpr: which has an alpha0 like two weeks after 11.0 :-) suseROCKs: That soon? jpr: so within a couple of weeks we are sure to be talking about 11.1 features hobbsc: rapid development KevinYo: I presume 11.1 will be coming out very soon after 11.0 then hobbsc: december, right? uberChick: *sqwee* how I love my openSuSE jpr: the is the plan i heard at least
Factory Testing Discussion
Speaker: All
(06:04:07 PM) jpr has changed the topic to: Meeting in Progress - Factory testing discussion (everyone) jpr: so jpr: the kernel bug is a real f***** srinidhi left the room. rodrigo1: yeah, it is snorp: kb bug too :) casualprogrammer: casualprogrammer: not the first accident I should say hpj: i'm a bit disappointed in the other system components, they show serious breakage so close to release hpj: well, the kernel jpr: hpj: example? jpr: :-) hpj: but has had some hiccups too hpj: zypper rodrigo1: we should really have the option to install new kernels without removing the old one, for these cases jpr: yes, keyboard bug is a bit worrying but vuntz is on the case hobbsc: link to keyboard bug? snorp: hpj: the zypp situation is at least 50 times better than 10.3 at least :) uberChick: hpj ? ditto's huh, I've not had any keyboard issues. hobbsc: and which kernel is in question here? hpj: snorp: yeah rodrigo1: hpj: I don't see problems with zypper vuntz: err, "vuntz tries to be on the case" would be more correct since I still have no real clue (but I'm starting to have a few hints) jpr: https://bugzilla.novell.com/show_bug.cgi?id=369263 bugbot: openSUSE bug 369263 in openSUSE 11.0 (GNOME) "first-time login / extraordinary k/b problems ..." [Critical,New] hobbsc: 2.6.25.3-2? hpj: rodrigo1: there were the pattern bugs hpj: rodrigo1: i dunno if you ran into those rodrigo1: hpj: no, didn't thoenig [n=thoenig@nat/suse/x-5875489fe2372eda] entered the room. jpr: other stuff? snorp: jpr: the ACPI breakage(s) are kind of bad too snorp: IMO snorp: https://bugzilla.novell.com/show_bug.cgi?id=392683 bugbot: openSUSE bug 392683 in openSUSE 11.0 (Kernel) "power button not working on T60p" [Normal,New] hobbsc: my only unresolved issue at this point is the .dmrc bug, but it's minor and has been assigned already jpr: yah, there are a bunch of thinkpad hotkey issues rodrigo1: snorp: isn't that part of the broken kernel ? jpr: causing the OSD problems snorp: rodrigo1: I don't know snorp: jpr: the hotkey thing was a separate bug snorp: jpr: and fixed, at least for me casualprogrammer: well, I think the issue is how to reduce bugs in the first place, and then get rid of them from factory if they become known, see Bug 371745 bugbot: openSUSE bug 371745 in openSUSE.org (BuildService) "block / remove packages that are broken from repositories" [Enhancement,New] https://bugzilla.novell.com/371745 srinidhi [n=srinidhi@59.96.35.26] entered the room. snorp: jpr: thoenig says there were a lot of acpi changes in the kernel, so not really surprising casualprogrammer: see also my last comment on Bug 391845 bugbot: openSUSE bug 391845 in openSUSE 11.0 (Kernel) "Post-Beta3 ACPI regression" [Critical,Resolved: fixed] https://bugzilla.novell.com/391845 jpr: aha jpr: good segue again i guess...
Under Prioritized Bugs
Speaker: jpr
(06:10:21 PM) jpr has changed the topic to: Meeting in Progress - Under prioritized Bugs (jpr) jpr: Today is openSUSE bug voting day jpr: hobbsc was kind enough to provide queries at: http://en.opensuse.org/GNOME/Bugs suseROCKs: I vote that we don't have bugts. hobbsc: suseROCKs: quit generating them jpr: that link to bug voting opensuse wide jpr: so vote, vote, vote jpr: the highest voted feature is one i would quite like myself uberChick: APCI is a conostant kernel issue, depending on brands software ram hd, so many components. Linux a.k.a. "The Linux Kernel" handles APCI more elegantly than even OSX does(in many cases) but APCI's never gonna be 100% unless all mother board manufactures adopt Linux BIOS. Hey we can dream. +++suseROCKs adds AI to everyone: Vote for bugs jpr: are there any GNOME/NetworkManager/Firefox/Banshee/Compiz bugs KevinYo: jpr: Yes. jpr: that are under-appreciated shall we say? KevinYo: :-) jpr: ie not getting the attention they deserver jpr: now is the time to bring them up :-) suseROCKs: uberChick: does that mean if possible, we should convert our motherboard bios to Linux bios? kangaroo: I'd like some love on the ath5k bug :) KevinYo: kangaroo: Which bug is this? jpr: kangaroo: #? kangaroo: bug 373098 bugbot: openSUSE bug 373098 in openSUSE 11.0 (Kernel) "ath5k failure with AR242x" [Normal,New] https://bugzilla.novell.com/373098 kangaroo: its more than just AR242x kangaroo: partially its the fact that ath5k doens't support all new cards yet kangaroo: but its affecting my new pc from bridge KevinYo: yes! I'm bit by that bug too! Voting... kangaroo: unfortunately it looks like we'd need a newer kernel pull jpr: oh kangaroo: which is probably a little late in the game jpr: this looks familiar hobbsc: updating bios to the linux bios sounds kind of scary jpr: is this with zypper upgrades? hobbsc: i'd rather not brick a machine doing that jpr: of a 10.3 box? kangaroo: jpr: I just did a fresh install on my new HP from bridge of 11b3 kangaroo: and got it jpr: ok FunkyPenguin: there is also https://bugzilla.novell.com/show_bug.cgi?id=382784 which is a real pita if you ask me bugbot: openSUSE bug 382784 in openSUSE 11.0 (Network) "NM don't react on WLAN button and don't set kill switch status correctly" [Enhancement,New] jpr: not the same i guess suseROCKs: hobbsc: Actually it sounds fun and challenging. :-) kangaroo: jpr: I'm just reinstalling from dvd right now, so I'll get more details in a hour or so jpr: tambeti: ^^ any comments on 382784? hobbsc: suseROCKs: yeah, if you're a sadist kangaroo: jpr: The unfortunate thing is it LOOKS (from a user perspective) like opensuse just sucks tambeti: jpr: there's a lot of comments there :) suseROCKs: I'm here, aren't I? kangaroo: because NM shows the APs, but cannot connect to any of them kangaroo: so the user experience is sub-par FunkyPenguin: jpr: it basically looks like we have to come up with hacks to make the spec work :( uberChick: suseROCKs: I'd highly recommend it. I have &have noticed drastic improvements on multiple levels, not just APCI. &Instant on to diagnosis, fscking, etc. Or even just adding a quick not to my /Art_n_Dev/IDEAS. &Tons more. kangaroo: would be better if we just blacklisted the not-working cards or something imo jpr: ok
Schedule 10.3 Bug Squash
Speaker: jpr
(06:18:23 PM) jpr has changed the topic to: Meeting in Progress - Schedule 10.3 bug squash (jpr) hobbsc: will the bug squash be held in this channel? hobbsc: or factory>? tambeti: jpr: FunkyPenguin: if it's not handled by hal, it'll have to be handled by both NM and ifup, but since ifup doesn't even have a daemon, it can never handle it jpr: so tambeti: which leaves us only hal kangaroo: hrmm; fresh install from b3 dvd also just gave me a desktop without window decorations :) jpr: in the past, http://en.opensuse.org/GNOME/BugDays suseROCKs: hobbsc: gnome-related bug squashes are usually held here uberChick: kangaroo: I wouldn't agree w/that on any level jpr: we reviews all 10.2 and older bugs hobbsc: roger that. mw: older? isn't 10.1 at EOL, or will it be soon? uberChick: kangaroo: PEBKAC install? jpr: i think its time to do it for 10.3 hobbsc: i thought 10.1 was part of SLE* jpr: so jpr: we basically need volunteers to setup the page jpr: find a date jpr: and run the squash FunkyPenguin: hobbsc: nope, SLE used 10.1 code base mw: hobbsc: sle10 was based on 10.1, but they're somewhat different hobbsc: jpr: i can assist with that if you tell me what needs to be on the page jpr: hobbsc: the other pages are good examples hobbsc: i can follow formats, too afonit [n=afonit@72.243.23.170] entered the room. hobbsc: toss me a link and i'll be happy to assist jpr: hobbsc: http://en.opensuse.org/GNOME/BugDays jpr: in terms of dates jpr: what do people think? kangaroo: uberChick: Uh.. no +++jpr thinks before 11.0 release so people know what they get by upgrade hobbsc: i'm open for most any time outside of next weekend. major work to do next weekend rodrigo1: Wed next week ? uberChick: jpr: "setting up the page"? As in adding a WIKI page, something more, article, or like a press release? hobbsc: i can do wed next week jpr: uberChick: setting up the wiki page, then publicizing it a bit jpr: proposal: wed May 28 anrich left the room ("Ex-Chat"). jpr: +1 hobbsc: +1 suseROCKs: ok what's the AI for May 28th? I missed it jpr: AI: create GNOME 10.3 bug day wiki page jpr: AI: send mail to opensuse-gnome about 10.3 bug day hobbsc: i can do that if you like jpr: AI: run bug day hobbsc: the page and/or announcement suseROCKs: and they all fall on hobbsc? hobbsc: i don't know if i can run bug day jpr: sounds like he volunteered for the first two :-) hobbsc: unless i take that day off hobbsc: which is entirely possible hobbsc: can't say i've ever ran one, though hobbsc: so i don't know protocol rodrigo1: it should be easy, just make sure we have a list of bugs, that people review them in order, etc jpr: yes hobbsc: i can try jpr: mostly just need to hang around in the channel hobbsc: i can do that, too jpr: hobbsc: sounds good - my guess is captain_magnus would help too :-) jpr: excellent hobbsc: outstanding suseROCKs: hobbsc: we know you're so committed here that even if you take a day off you'll go out and buy a wireless card to IRC anywhere. hobbsc: suseROCKs: already have one rodrigo1: :)
Community Outreach/Clinic/HowTo
Speaker: suseROCKS / captain_magnus
(06:26:28 PM) jpr has changed the topic to: Meeting in Progress - Community outreach/clinic/howto ( suseROCKS/captain_magnus ) suseROCKs: See? +++hobbsc ducks jpr: suseROCKs, captain_magnus ...
bugbot: New openSUSE 11.0 (GNOME) bug 393643 filed by mmeeks@novell.com.
bugbot: Bug https://bugzilla.novell.com/show_bug.cgi?id=393643 Major, P5 - None, NEW, multi-second busy-loop on login ... suseROCKs: Okay, I briefly brought up this topic last week... suseROCKs: Basically, captain_magnus and I were discussing about how to increase community involvement/awareness/et al here without umm... scaring them off with all this "dev talk" :-) suseROCKs: So, we decided that we would propose that we have weekly meetings here in the channel covering various topics of interest to users. suseROCKs: One hour, how to use the GNOME desktop suseROCKs: One hour, how to use CHEESE +++FunkyPenguin votes for winning lottery numbers :) suseROCKs: etc. etc. uberChick: I'm starting an openSuSE podcast, please(literally please) just give me a deadline I'll give you a debut &publicise the page, release &project. uberChick: But I'll be honest I've got so much coding, blogging, recording, open audio editing, &more coding &blogging on my plate to even pretend I could do much more than publicise the page, along with the project... plus everything else openSuSE related in my bloggings &podcasts. suseROCKs: And we would bring in people who know their stuff about a particular app and such. In other words, we need you all to get behind this. rodrigo1: suseROCKs: that would be great if after every meeting a HOWTO is written covering what te meeting was about suseROCKs: Good Idea rodrigo1 suseROCKs: I also think that the meeting should be held twice weekly to accommodate different time zones. suseROCKs: We should launch this new project beginning as soon as 11.0 is released, as that's when the newbies are most likely to come around. FunkyPenguin: +1 rodrigo1: yes, or even a bit before, so that the debut is under a smaller audience :-) AlbertoP: the meeting should be held twice <<--- isn't it too much? jpr: that sounds like a lot jpr: to me as well jpr: but changing times is good suseROCKs: AlbertoP: yes and no. Reason being the meeting is about educating users. Not all users can show up at this hour. AlbertoP: I mean, the main goal is to _WRITE_ something FunkyPenguin: so if need be the second meeting could be a re-cap and summary? suseROCKs: no, writing should ALWAYS happen regardless of this project. AlbertoP: meetings are a good idea, but information is lost uberChick: suseROCKs: ditto on twice weekly. &I do a lot of web dev &multimedia design &production &would happily cover those apps(!(kde) e.g. kdenlive) of course. suseROCKs: The main goal is to make new users feel welcome to join in suseROCKs: where they can actually talk to someone and ask questions and feel a sense of relationship casualprogrammer: AlbertoP: there could be a transcript be published.. hobbsc: suseROCKs: i suggest some kool-aid AlbertoP: suseROCKs, I agree, but it's a huge effort for a few users...and we already have a huge lack of information on wiki hobbsc: *special* kool-aid AlbertoP: casualprogrammer, ok suseROCKs: "few users"? AlbertoP: suseROCKs, experience says that we don't notice a huge increase of the number of users in IRC channels after a release suseROCKs: I came here after 10.3 release :-) AlbertoP: the trend is < 300 -> slightly > 300 for some time, than back to < 300 on #suse suseROCKs: of course, jpr bamboozled me here hehe pygi: suseROCKs, I think you might want to change the style of communication to the users suseROCKs: pygi: yes I'll behave :-) hobbsc: had i known these channels existed, i'd have shown up long ago pygi: rather then having "meetings" with users, where one folks "knows it all", make it more a collaborative effort federico2: uberChick: where do you intend to release the podcast? are you doing interviews or something like that? hobbsc: i only knew about this channel when jzb mentioned the last meeting on his twitter pygi: get lots of users in, set a topic for that day, and let them talk ... and do involve one facilitator in the discussion hobbsc: perhaps publishing the channels along with a release would be useful? suseROCKs: pygi: yes I haven't come up with a good name for what we'll call this. Meeting isn't right. Presentation? HowTo? Clinic? hobbsc: maybe in the release notes? AlbertoP: hobbsc, support channels are shown on opensuse greeter :D casualprogrammer: couldn't it be some kind of forum extended by live discussions ? I think most newbies go to forae at first. suseROCKs: AlbertoP: true, but who reads greeters? I don't. :-) hobbsc: AlbertoP: who reads that stuff anyway? :D hobbsc: suseROCKs: jinx! AlbertoP: hum AlbertoP: laaazy AlbertoP: :D AlbertoP: they're also on the suse page you access clicking on "suse" icon pygi: suseROCKs, The chameleon days suseROCKs: Well let's see how we do after a month or so. I'm convinced this is a good way to make new users feel welcome. AlbertoP: yes I agree suseROCKs: But before we do, can we get a commitment from everyone here on the team to be able to volunteer from time to time to cover a topic? AlbertoP: I just would love the info on the wiki :D +++hobbsc <- not on the team pygi: suseROCKs, why not take the approach I suggested, and just get someone to volunteer as facilitator? suseROCKs: AlbertoP: never said it wasn't going on the wiki. All this is is an extra way to embrace our users. rodrigo1: suseROCKs: +1 from me AlbertoP: ok pygi: hey rodrigo1 ^_^ captain_magnus: suseROCKs: +3 :-) AlbertoP: count me in casualprogrammer: suseROCKs: +1 from me too suseROCKs: oh sure, captain_magnus shows up after everyone bashes me... :-) rodrigo1: hey pygi +++AlbertoP thinks captain_magnus is bigger, so he counts for three :P suseROCKs: Alrighty... AI to me and captain_magnus to get the ball rolling on this next week. End of topic jpr: suseROCKs: so are you and captain_magnus going to come back with a plan next week jpr: with specifc about timelines and such? jpr: oh :-)
PulseAudio Update
Speaker: rodrigo
(06:39:31 PM) jpr has changed the topic to: Meeting in Progress - PulseAudio (rodrigo) suseROCKs: jpr you need to hit enter faster than me next time. jpr: rodrigo1: ... +++vuntz will leave soon AlbertoP: pulseaudio -> 1 comment: it glitches badly everytime you listen music and do something else :-) rodrigo1: ok, so I've patched gnome-applets to run PA volume control from the volume applet, and now this is the default we have rodrigo1: AlbertoP: with all the latest updates ? uberChick: suseROCKs: I feel my podcast will help make new users feel welcome &have easy entry into our community. I'm open to hearing suggestions, opinions, or any one who wants to participate. suseROCKs: uberChick: podcasting sounds great. Although for Deaf guys like me, we would hope there's a transcript available. :-) AlbertoP: rodrigo1, in beta 3 AlbertoP: I didn't upgrade...waiting for rc rodrigo1: ok rodrigo1: in beta 3 it's not working out of the box, I saw it this morning on a fresh beta3 install AlbertoP: hum, it seems to work here AlbertoP: I mean, I hear sound ^^ kangaroo: there we go jpr: other pulseaudio stuff? rodrigo1: only that please have a look at the thread in opensuse-gnome about what to do with padevchooser uberChick: I intend to draw attention to our wonderful community resources. Not to create just a community around the podcast but to our entire community. My podcast just being another aspect. uberChick: From openSuSE.us(we're gonna need more free emails) to IRC, our WIKI, &forum. I'm also interviewing users &contributors on all levels to openSuSE always trying to focus on 'us' not becoming 'them'. I've always loved the complete lack of 1-up man-ship here. From SuSE to openSuSE.
PackageKit Update
Speaker: sreeves
(06:46:55 PM) jpr has changed the topic to: Meeting in Progress - PackageKit (sreeves) sreeves: thanks to everyone for the testing on the updater suseROCKs: careful uberChick. You're talking exciting stuff and captain_magnus hasn't had his coffee yet. hobbsc: s/coffee/beer sreeves: there were a couple of good bugs entered and I am working on those for the friday checkin sreeves: no additional features so thats about it rodrigo1: sreeves: hmm, now that I see on this beta3 system, the pk-icon thing is not running rodrigo1: sreeves: maybe it's missing in some pattern ? AlbertoP: sreeves, did translations went upstream? :) AlbertoP: go* sreeves: rodrigo1: is it not running or is there just no updates available sreeves: rodrigo1: look for the gpk-update-icon process rodrigo1: seems it's running, but zypper shows lots of updates sreeves: rodrigo1: hmm, run gpk-update-viewer, does it show you the available updates ? FunkyPenguin: rodrigo1: it could be a zypper issue - i had it say that there were update, but if i went and ran up nothing rodrigo1: sreeves: right, oit needed refreshing it seems rodrigo1: FunkyPenguin: yeah, right, saw that too +++casualprogrammer types gpk-update-viewer and gets ** ERROR **: Could not connect to system DBUS. pygi: casualprogrammer, dont run it as root +++FunkyPenguin just had gpk-update-viewer crash when starting up casualprogrammer: pygi: thanks FunkyPenguin: sreeves: do bugs for pk go under gnome or something else? sreeves: FunkyPenguin: yeah gnome, just assign them to me jpr: FunkyPenguin: under GNOME jpr: add packagekit-devel to the whiteboard if you can +++casualprogrammer follows pygi's advice and gets "There are no updates available", still asks himself why it should crash when run as root uberChick: suseROCKs: I'm def not able to transcript it though as I'm disabled, I live w/a neuro-muscular disease called Generalized Dystonia. Which has left me not only wheel chair bound but bed ridden. &W/only one functional hand, which degrades w/use. Sorry for my & ws and / I just imagined how they must come across w/orca which I do use &love. My short hand writing is one way I'm trying to adapt to life w/Generalized Dyston uberChick: ia, I abbriviate it to GD. @least I use these until I have the equipment I need. *almost done, just one more peripheral to purchase, *gulp* $200, but still I 'feel like I'm almost done. I'm only $110 short. uberChick: *wow*
Multi Head Wrap Up
Speaker: federico
(06:55:22 PM) jpr has changed the topic to: Meeting in Progress - Multi Head wrap up (federico) (08:55:30 PM) jpr: federico2: ... +++uberChick apologizes for huge off topic babble dump suseROCKs: uberChick: well it should be a team effort. Not one person doing all the work on a podcast/transcribing. :-) +++uberChick apologizes but isn't /sorry/ *wink* jpr: federico2: ahem
Theme Meetings
Speaker: jpr / suseROCKS
(06:57:07 PM) jpr has changed the topic to: Meeting in Progress - Theme Meetings ( jpr / suseROCKS ) berChick: suseROCKs: Thnx for understanding. jpr: theme meetings jpr: we need to get back on track with these suseROCKs: Hmm... this is my topic too? :-) jpr: what kind of technical topics would we like to cover coming up? suseROCKs: jpr is there anything new and exciting being developed currently? jpr: always :-) jpr: we never had the X guys come to talk captain_magnus: Is the HardwareKit thing part of PackageKit or separate? Be nice to know more about that and if we'll see it in 11.1 suseROCKs: We have X-Men? jpr: its DeviceKit bugbot: New openSUSE 11.0 (GNOME) bug 393677 filed by awafaa@opensuse.org. jpr: its possible it will be in 11.1 bugbot: Bug https://bugzilla.novell.com/show_bug.cgi?id=393677 Normal, P5 - None, NEW, gpk-update-viewer crash on startup jpr: but unlkeily captain_magnus: jpr: Why unlikely? suseROCKs: confound FunkyPenguin for inserting a bug in the middle of meeting and distracting us :-) jpr: because it won't be ready in to afaik jpr: kay would know more FunkyPenguin: sreeves: im not sure the output is of much use suseROCKs: jpr since you know what exciting stuff is on the horizon, throw out a few topics and let us pick what sounds cool to us. jpr: hmm :-) FunkyPenguin: winning lottery numbers? rodrigo1: I would like to see a effects in apps brainstorming / meeting / or whatever rodrigo1: to decide how we could use desktop effects and / or clutter in apps ? suseROCKs: rodrigo1: what does that mean? captain_magnus: suseROCKs: 3d stuff/compiz effects rodrigo1: we can have effects in apps, for specific events/notifications jpr: thats not really a cross team technical topic imho rodrigo1: we need to decide what / where to use them rodrigo1: yeah, probably suseROCKs: rodrigo1: I see definite a11y uses for that. casualprogrammer: jpr: how about the kiwi tools ? rodrigo1: suseROCKs: yeah, for instance +++AlbertoP thinks: effects -> disabled ^^ uberChick: So what about testing meeting, page, &publicizing them? When should we really start pushing this? So I know what level of priority to assign to the community openSuSE podcast. Esp. so I'll have a more solid target date for its debut release. Which btw every one; I've titled it "Pronounced: openSuSE" uberChick: brb federico2: ah captain_magnus: federico2: Nice of you to pop in :-) federico2: so, multihead wrap-up jpr: federico2: hold on please, we moved on federico2: ok jpr: i'll come back to it jpr: so, in short it sounds like we don't have a lot of good cross team ideas atm? jpr: kiwi was good suseROCKs: rodrigo1: I'd love it if we have a separate meeting to talk effects stuff. Plan on one! casualprogrammer: jpr: :-) jpr: but nothing else? rodrigo1: suseROCKs: ok, thanks for volunteering for running it :-) jpr: AI: jpr to see about kiwi theme meeting
Multi Head Wrap Up
Speaker: federico
(07:05:08 PM) jpr has changed the topic to: Meeting in Progress - Multi Head wrap up ( federico ) suseROCKs: "Plan on one" was directed at rodrigo1. How do these things get twisted around?!? rodrigo1: jpr: some joint KDE / GNOME thing would be a good idea, I guess, to decide on x-desktop things jpr: federico2: now :-) +++AlbertoP sends beagle to find federico2
Agenda For Upcoming Meeting
Speaker: jpr / All
(07:06:56 PM) jpr has changed the topic to: Meeting in Progress - genda for upcoming meeting (casualprogrammer) jpr: ok federico2: ok jpr: agenda items
Multi Head Wrap Up
Speaker: federico
(07:07:22 PM) jpr has changed the topic to: Meeting in Progress - Multi Head wrap up ( federico ) federico2: we can't get rid of resapplet for 11.0, as right now it's the only way we have to do rotation easily for tablets federico2: e.g. you can't expect a tablet user to find gnome-display-properties buried in the menus just to rotate his tablet captain_magnus: federico2: What's other distros doing? federico2: also, X drivers are a totall mess *and* SaX doesn't help with setting up an xorg.conf that is friendly to doing RANDR changes dynamically federico2: captain_magnus: they don't use resapplet casualprogrammer: federico2: couldn't that be solved by tapping in certain places ( corners ) for tablet ? casualprogrammer: federico2: much like dragging the panel around ? federico2: for example, by default SaX sets up laptops to have a cloned display, but then (since it's in xorg.conf) it can't be changed by gnome-display-properties federico2: casualprogrammer: yes, but we don't have code for that :) suseROCKs: AI: casualprogrammer to create tapping code for tablets federico2: casualprogrammer: it's perfectly doable; it just needs to be written federico2: so for now the recommendation is: captain_magnus: federico2: and sax2 doesn't set it up because it requires more memory right? How much memory are we actually talking about federico2: * use gnome-display-properties to set up your multihead setup, *after* reading the caveats in the wiki (http://en.opensuse.org/GNOME/Multiscreen) federico2: * use resapplet just to rotate if you are on a tablet federico2: captain_magnus: hmmmm, I don't think it's a memory issue; it's just that the default is a quick hack to get projectors working more or less out of the box captain_magnus: federico2: Ok... I was sure that I read something about the extra memory requirements as a reason but... Fair enough AlbertoP: federico2, did this change for 11? In 10.3 sax doesn't set any dual mode and you've to select it in the config dialog :-? federico2: AlbertoP: both set up cloned mode by default, I think AlbertoP: ok federico2: for 11.0 I'm pretty sure; for 10.3 I'm almost sure it did :) AlbertoP: hmm, 10.3 I had to do it manually :-? AlbertoP: I mean: open sax and activate the check box ^^ casualprogrammer: suseROCKs: not a thing to be programmed casually :-) AlbertoP: but probably it's due to nvidia :-? federico2: AlbertoP: no idea - drivers are a mess federico2: for example: federico2: on old radeon cards we use the "radeon" driver, which is an old version that doesn't let apps see when new monitors are plugged in. The new driver that supports that is "radeonrandr12", but our X people didn't think it was stable enough to use by default... AlbertoP: yup federico2: I'm going to germany in June, so I'll have a chance to discuss this :) captain_magnus: dum de dum... :-) suseROCKs: federico2: will you bring back souveneirs? jpr: ok jpr: lets wrap up :-)
Agenda For Upcoming Meeting
Speaker: jpr / All
(07:18:34 PM) jpr has changed the topic to: Meeting in Progress - Agenda for upcoming meeting (casualprogrammer) suseROCKs: yes we need to move on. uberChick has a topic to add in a moment. jpr: would like under prioritized bugs on the list again federico2: suseROCKs: yes! jpr: do we need pulseaudio or multihead on the list next week? rodrigo1: I think pulseaudio can be dropped, we're just in bug fixing mode now rodrigo1: so if there's any big bug, it should show up on the factory testing part casualprogrammer: casualprogrammer: you probably can't hear it anymore, but I would like a _real_ discussion about Bug 371745 bugbot: openSUSE bug 371745 in openSUSE.org (BuildService) "block / remove packages that are broken from repositories" [Enhancement,New] https://bugzilla.novell.com/371745 suseROCKs: why does casualprogrammer keep talking to himself? jpr: casualprogrammer: wrong audience really captain_magnus: casualprogrammer: You need to discuss that on the -factory ml +++casualprogrammer is asking himself the same question...
Questions & Answers
Speaker: jpr / All
(07:21:08 PM) jpr has changed the topic to: Meeting in Progress - Q&A jpr: uberChick: you had something to bring up? hobbsc: i've got questions re: the bug squash as well casualprogrammer: captain_magnus: will do, thanks federico2: jpr: there should just be bugfixes to multihead next week, so nothing major +++suseROCKs should swap drives in his tablet and check out this stuff federico2 talks about hobbsc: questions/update kallepersson left the room (quit: "Lämnar"). jpr: LAST CALL for Questions hobbsc: jpr: did we decide on the 28th? jpr: hobbsc: yes hobbsc: what time? hobbsc: i got approval to get that day off hobbsc: so i can sit in the channel and assist hobbsc: i'll also update the page, so i'll need to know what bugs will be covered jpr: hobbsc: we've done it sort of 9am EST to evning EST hpj: i think leio had a question before jpr: that catches most timezones at least a bit hpj: er, lejo jpr: he did
hpj: i read the scrollback
hpj: and yes, i'm looking into that problem hpj: submitted a patch upstream and to our packages yesterday +++uberChick 's back hobbsc: jpr: great, i'll create the page and be here to help run the meeting hpj: but i just learned that it's not the whole fix jpr: hobbsc: sweet hpj: so i'm looking into it today too hobbsc: i'll make the announcement, too suseROCKs: hpj: what was the question? hpj: suseROCKs: "gvfs fuse mount in .gvfs is broken after logging out and back in" hpj: suseROCKs: "is there a bug for this?" hpj: suseROCKs: short answer: yes +++FunkyPenguin splits for a bit hpj: uberChick: said she's back captain_magnus: hpj: Picking up meeting management skills are you? :-) hobbsc: jpr: you going to set the topic for the channel, etc. on the 28th? jpr: sure jpr: or give you rights to do it hobbsc: either way hpj: captain_magnus: just wondering if she had something to add, i guess she's busy though suseROCKs: jpr: hobbsc is from Arkansas. You want to be careful how much rights you give to someone from that place. ivanz [n=i-nZ@92.11.124.140] entered the room. casualprogrammer: who would be the contact for bots in irc ? hobbsc: har har jpr: casualprogrammer: benJIman jpr: iirc uberChick: jpr: What are the plans for adoption / inclusion of GNOME's Online-Desktop. Which is obviously the future of GNOME &honestly as I slowly get the pieces together it all makes sense. The module nature is wonderful, its amazingly &easily extensible. Though JHBuild makes compiling it easy enough just hella time consuming. casualprogrammer: jpr: thanks jpr: uberChick: there are no current plans to adopt GOD as a key piece of the 11.1 cycle jpr: though i would like to get the mugshot packages in G:C jpr: from justin suseROCKs: "no plans to adopt GOD" that just sounds sooo blasphemous. rodrigo1: uberChick: I would really like to understand what it would improve for users like me, with several computers at home jpr: uberChick: if you have specific ideas of what you'd like to see integrated, please propose them jpr: or wiki-fy them :-) rodrigo1: uberChick: that is, I see it a good thing for corporations, universities, online services, etc uberChick: jpr: any plans of making it an option? +++captain_magnus just noticed that g-m-m does not pickup the network connection if it's "GSM"... <== federico2 :-) hpj: i think the whole GOD thing is a bit nebulous jpr: uberChick: not now, but we're open to anything for 11.0 hub: is it still even maintained? hub: since hp has left RH jpr: yes, RH still has a couple of people at least part time on it snorp: yeah I sort of thought it was dead jpr: owen, marco and someone else captain_magnus: hub: Oh? Where did he go? hub: captain_magnus: litl jpr: it will be presented at guadec again this year uberChick: aside from the fact that I'll be dropping it in builf build service once I'm done, which won't be until openSuSE 11.0's released. federico2: captain_magnus: probably a bug in that big scary "figure out the network status" function :) jpr: uberChick: its packaged in the BS already jpr: justin haygood i think +++hub will have a suse laptop at guadec this year at least :-) jpr: (at least the mugshot bit) captain_magnus: federico2: Heh, not a bug... Just a missing feature... Would it make it to 11.0 if "someone" were to create a patch for it? jpr: Thanks all! (07:32:09 PM) jpr has changed the topic to: http://en.opensuse.org/GNOME/ | Testing needed: http://en.opensuse.org/GNOME/11.0/Testing

