*jpr has changed the topic to: Meeting in progress - Introduction (jpr) | http://en.opensuse.org/GNOME/Meetings/20071025 | http://en.opensuse.org/GNOME jpr: Welcome to the openSUSE GNOME Team Meeting! jpr: This week we are continuing our format experiments by having a theme topic to start the meeting, and we have Stefan Seyfried from the mobile devices team to talk about Bluetooth. There will be Q&A after a brief presentation. seife: Was this my "go"? :-) jpr: so, sit back, relax and lets get started :-)

*jpr has changed the topic to: Meeting in progress - IBluetooth Guest Speaker (seife) | http://en.opensuse.org/GNOME/Meetings/20071025 | http://en.opensuse.org/GNOME seife: Ok, short introduction: seife: I'm Stefan Seyfried, working in the Nürnberg facility in the Mobile devices team and the QA team (50) seife: In Mobile Devices, i am mostly doing suspend and power management related stuff and i am maintainer of the core bluetooth packages. seife: That's it already :-) captain_magnus: seife: How long have you been following bluetooth development on Linux and what's your experience on other os's? *captain_magnus kickstarts the q&a... :-) jpr: well, seife can you give us a brief overview of the current bluetooth state at the low levels? seife: I'm following the BlueZ development since ~2004, and i have seen that somebody plugged a BT USB device into a windows box. seife: ;-) seife: Ok. As many of you might have noticed, lots of stuff in BT-land changed recently. seife: The communication mechanism changed from socket based communication with hcid to dbus seife: in former times there were many smaller daemons (sdpd, hcid, ...), now most of the tasks get pulled into hcid seife: This makes some sense, since many of those services are closely intertwingled, and one "bluetooth super server" seife: will know better and easier about the global system state than lots of small "service daemons" that need to seife: communicate among each other to find out the global state. seife: Consequences of that: seife: - no sdpd anymore (instead hcid gets started with option -s) seife: - no hidd anymore (instead there is the input service that handles input devices in conjunction with hcid) seife: - users can configure (almost) everything via dbus (and thus via a shiny desktop applet) seife: More consequences of that: seife: - you can edit hcid.conf, but it probably will have no effect seife: (if you changed a setting via dbus, then hcid will remember the setting and this setting will take precedence over hcid.conf) seife: - yast2 bluetooth module does not work very well because of this (and *henrix (i=miguel@84.90.24.110) has joined #opensuse-gnome seife: because i missed updating the spec for the yast developers - it is not their fault) captain_magnus: Sounds great... Is all of this in 10.3 already or will that be introduced in 11.0? seife: - many people claim "you cannot configure it from the command line anymore" (well, tough luck) seife: This is all in 10.3 already. seife: Of course it is still work in progress (and progress is going on FAST in BT-land). rodrigo: how does this affect GNOME (or KDE...) apps? rodrigo: what's the interface for those apps? seife: One problem is, that i actually did not expect that we'd get that far for 10.3 (otherwise yast2 bluetooth would be gone already) seife: GUI apps basically must be ported to the new interface. Marcel provides bluez-gnome, which seife: has exactly those features HE needs. He is, however, not rejecting patches and there have been seife: quite some that he applied recently (i was 3 weeks off, so i'm not totally current on the matter :-) jpr: the gnome packages involved are as follows: seife: Basically it should be not too hard, there is a dbus-api.txt file in the source (and i think i also jpr: bluez-gnome jpr: gnome-vfs-obexftp jpr: libbtctl jpr: gnome-bluetooth jpr: gnome-phone-manager seife: package it in the bluez-* packages somewhere) that describes the api. jpr: these were fairly out of date in 10.3 jpr: http://download.opensuse.org/repositories/home:/jproseve/ jpr: has updates jpr: and they have been submitted to factory and will be moved to GNOME:STABLE as well jpr: bluez-gnome provides the pairing applet seife: Yes, and as soon as you package one of those, it will be out of date again :-) As i wrote, progress seife: is going on FAST. jpr: gnome-bluetooth is the obex stuff federico1: captain_magnus: hmmmmmm jpr: and gnome-phone-manager jpr: handles sms send/receive with the phone captain_magnus: Can gnome-phone-manager *actually* send/receive txt messages from/to the phone with the updated packages? seife: But in the end, much of this will be easier to implement. IIUC, the goal is, for example, that you request jpr: captain_magnus: yes, but i can't test, my phone doesn't support it :-)

*jpr has changed the topic to: Meeting in progress - Bluetooth Q&A (seife) | http://en.opensuse.org/GNOME/Meetings/20071025 | http://en.opensuse.org/GNOME seife: via dbus "give me the dialup interface of device 00:... " and you get a filedescriptor in return that you can seife: use directly to start pppd on it. seife: Right now, you need to: seife: - find out the rfcomm channel (sdptool browse) seife: - edit /etc/rfcomm.conf (as root) seife: - rfcomm bind all (root!) seife: - edit the config for dialup seife: - start dialup on rfcomm0 seife: In the future, a dialing program (or something doing SYNCML,...) just says alan_: heh, trying to turn up the brightness fails on my macbook jpr: i should note that there are patches for NetworkManager upstream to support bluetooth jpr: network devices alan_: the brightness thingy that pops up on screen goes up 1 notch, but can't go any further tambet: "hopefully in the future you'll click on nm-applet that does everything alan_: known bug? seife: "give me service $FOO on device $device" and then it will get a channel that can be used for data transmission. jpr: alan_: a) meeting in progress b) yes and update is submitted alan_: whoops, k seife: yes, but bluetooth network devices are actually not toooo interesting (PAN and NAP) tambet: the bluetooth patches for NM are very poorly done and need to be rewritten captain_magnus: Might be a bit naive, but did all this bluetooth progress start recently? Or has that been long in the making but we didn't keep up? seife: And i can't repeat here what Marcel said about those patches. seife: Ah, i see, tambet agrees :-) tambet: heh :) seife: It was long in the making, but there was old compatibility code. seife: Well, you know what happens as long as it does still work _somehow_ :-) seife: recently (around 10.2 timeframe), marcel started to remove the old compatibility code and interfaces. seife: New functions were only offered via dbus. seife: dbus was made mandatory (imagine the cryout from the embedded folks running 2.4.x kernels) seife: So yes, we did not keep up. seife: Nobody did. jpr: Other questions for seife or on bluetooth? seife: So Marcel got pissed and forced everybody to keep up. And in fact he is right (IMHO), since the new infrastructure is better. captain_magnus: How easy will it be... seife: Yes, come on! Ask! captain_magnus: ...to add a bluetooth mouse or headset now when it's all dbus captain_magnus: (From the backend point of view) seife: Very easy actually. seife: ?"backend point of view"? captain_magnus: The backend must know what sort of device it is, right? captain_magnus: And be able to announce it via dbus to whoever asks? captain_magnus: Backend meaning hcid seife: yes, the backend is mostly hcid. That's one reason why it's all pulled into one daemon. seife: Since hcid is the central instance managing the devices, it is not too hard to announce what is seen. seife: For example, it is very easy to do the "bluetooth monitor" that is included in bluez-gnome (and kbluemon in kdebluetooth). captain_magnus: What happens when a new device is brought to the market and hcid does not know what it is... Can a frontend app still make use of it? seife: ok, now i understand. seife: That does not happen. Bluetooth is pretty heavily standardized. Sometimes the kernel driver needs some workarounds, but that's it. seife: If there comes something totally new, with totally new capabilities - well, then it will need to be implemented, that's true. seife: Devices have certain capabilities and "profiles" which are defined by the bluetooth standard. seife: (don't quote me literally on that, i'm not too deep into bluetooth internals) jpr: great jpr: seife: thank you, very interesting jpr: seife: if you could hang out till the end, there might be more questions jpr: i know i have some technical ones :-) seife: ok, no problem. captain_magnus: seife: Thanks heaps! jpr: thanks again to seife for giving us bluetooth insight! jpr: try out the gnome bluetooth packages as well!

*jpr has changed the topic to: Meeting in progress - Bug plan status (federico and rodrigo) | http://en.opensuse.org/GNOME/Meetings/20071025 | http://en.opensuse.org/GNOME jpr: federico1, rodrigo quick update? federico1: sure *rodrigo will test with his nokia cell phone seife: Yes, i will. It is on my agenda for quite some time :-) rodrigo: go ahead federico1 , I haven't done anything since the last meeting about the bug plan federico1: I added the "gnome-*" tags to the Status Whiteboard of a little bunch of bugs federico1: They are linked from the "10.2" and "10.3" sections in http://en.opensuse.org/GNOME/Bugs federico1: the idea is to go through the full buglist, adding those tags as appropriate. Today I'll spend a few hours doing that :) rodrigo: federico1: I already did that on a few bugs, will go through the list also later on federico1: I haven't done that since I was in China... federico1: rodrigo: excellent, thanks :) captain_magnus: I added it to my two bugs today as well... federico1: rodrigo: it's almost night for you, isn't it? do you want to start tomorrow on that, so we don't conflict today? rodrigo: federico1: in last meeting, we asked people to add the gnome- tags for bugs they file captain_magnus: Just too bad you can't add whiteboard stuff when you create the bug rodrigo: federico1: yes, sure suseROCKS: Can someone explain what "adding the gnome-tags" means specifically so I can do that as well? federico1: captain_magnus: yeah, that's a bit inconvenient federico1: suseROCKS: sure *captain_magnus hopes federico1 is typing :-) jpr: federico1: hello? federico1: suseROCKS: start reading at http://en.opensuse.org/GNOME/Bugs#Criteria_for_bugs_to_fix and then see http://en.opensuse.org/GNOME/Bugs#Categories forthe actual stuff you put in the Status Whiteboard suseROCKS: oh thank God! I thought I was disconnected LOL jpr: me too suseROCKS: Thank you Federico jpr: any questions/comments for federico1 ? *alan_ (n=chatzill@ip-83-147-173-111.dub-3rk1.metro.digiweb.ie) has joined #opensuse-gnome jpr: federico1: when will you consider this plan done so we can use it as the basis for our bug fixing? federico1: suseROCKS: the idea is to tag bugs based on what they are: functions that don't work when you use them, or something that is wrong out of the box but that doesn't really prevent you from working. federico1: suseROCKS: and we use the Status Whiteboard field in bugzilla for those tags suseROCKS: Got it federico1: jpr: it's pretty much done; the Bugs page just needs a bit of polishing to remove the "Draft" stuff and old info :) federico1: jpr: I'll take care of it today, since the tags we have are already pretty good jpr: other questions? captain_magnus: federico1: Perhaps create one category... captain_magnus: ...for bugs that have no whiteboard status? rodrigo: federico1: in last meeting it was suggested to add gnome-accessibility captain_magnus: ==> On the bug page rodrigo: federico1: we agreed it was better done as a themed bug/hacking day rodrigo: but since you were not around, what do you think? federico1: captain_magnus: that's a good idea. Note that for some bugs I didn't add any tags, since they didn't match the proposed categories and they didn't seem very important... random/minor enhancement requests, weird special cases, etc. jpr: federico1: good candidates for sending upstream and closing federico1: rodrigo: oh, that's a good idea federico1: rodrigo: I *think* I haven't run into any of those, but can you please add a tag to the Bugs page? captain_magnus: We should have a generic tag for them then perhaps? Otherwise people will keep looking at thoise bugs and try to categorize them... rodrigo: yes rodrigo: you mean you want to use that g-a11y for the whiteboard? jpr: federico1: we have the should_go_upstream keyword presently federico1: jpr: do we need a tag for that apart from should-go-upstream? jpr: i don't know, its your plan :-) jpr: federico1: so your current prediction is that for the next meeting we can wrap up the bug plan and declare it closed? rodrigo: I don't think we need that, apart from having a query to the should_go_upstream GNOME bugs federico1: captain_magnus: in theory we go through the bugs in numerical order (people are of course free to tag new bugs they file, or random bugs they find in bugzilla). So you can assume that anything after the "latest" bug number listed in the Bugs page hasnot been categorized yet, while earlier bugs have been taken care of suseROCKS: Federico... I proposed the a11y idea last week, because I am one of those people.  :-) The only reason why I suggested it was to help make a11y issues stand out apart from general issues. federico1: rodrigo: yes, gnome-accesibility rodrigo: ok rodrigo: AI -> add gnome-accessibility tag to the bugs page (rodrigo) federico1: jpr: let me think about the upstream keyword mw|out: whoa jpr: ok *mw|out is now known as mw suseROCKS: YAY! *mw forgot to nick in, woops federico1: jpr: yeah, for the next meeting it's goingto be fully complete jpr: ok *jpr updates the eta federico1: suseROCKS: sorry I missed the last meeting; I was sleeping after the flight back :) jpr: suseROCKS: helping tag the a11y bugs would be a good way to help out, talk to federico1 and rodrigo after the meeting jpr: ok, lets wrap this one up *jpr has changed the topic to: Meeting in progress - Ancient distro bug squash (mtgordon) | http://en.opensuse.org/GNOME/Meetings/20071025 | http://en.opensuse.org/GNOME jpr: mtgordon is actually ill and has been all week federico1: AI -> federico to finish the bug plan on the Bugs page jpr: he is going to reschedule the ancient bug distro bug squash to Nov 2nd suseROCKS: Thanks JP jpr: hopefully this is not too inconvenient for people jpr: but we aren't prepared for tomorrow jpr: questions on that? captain_magnus: I'm sure it's more inconvinient for mtgordong to be ill than for us at the mement... rodrigo: yeah :)

*jpr has changed the topic to: Meeting in progress - Team Goals (jpr) | http://en.opensuse.org/GNOME/Meetings/20071025 | http://en.opensuse.org/GNOME jpr: i mailed about this to the list: jpr: http://en.opensuse.org/GNOME/Goals jpr: no feedback :-) jpr: does anyone have any comments/suggestions before it gets finalized? jpr: its just a statement of the extra goals of this team captain_magnus: Sounds good to me... Go for it! :-) jpr: its meant to be on top of the broader project goals DimStar: I like the goals... it would be good if people would realize that gnome and kde are equally supported within openSUSE rodrigo: sounds good to me also *wberrier (i=wberrier@nat/novell/x-ba2c44be753b7e87) has joined #opensuse-gnome jpr: anything else? rodrigo: yeah, probably adding 'cooperation with other desktops' suseROCKS: re-reading it now... rodrigo: although 'Contribute to improving openSUSE as whole' might include that jpr: i think so *gothica (n=pavel@87.251.157.6) has joined #opensuse-gnome jpr: AI: Make team goals final (jpr) federico1: jpr: "help solve integration issues between gnome and the rest of the world"? captain_magnus: Haha suseROCKS: What about something like, improving user understanding of use of Gnome? federico1: i.e. the things you never consider when you are a plain upstream developer jpr: suseROCKS: which users? *aka_druid (n=aka_drui@bd2144fc.virtua.com.br) has joined #opensuse-gnome jpr: federico1: "Contribute to upstream GNOME development" ? jpr: federico1: "Attract upstream GNOME developers and users to openSUSE" suseROCKS: general users? or is that not in this scope? jpr: federico1: do those cover that? jpr: suseROCKS: i think that falls out naturally from all of these goals suseROCKS: ok jpr: ok jpr: next

*jpr has changed the topic to: Meeting in progress - Task Review | http://en.opensuse.org/GNOME/Meetings/20071025 | http://en.opensuse.org/GNOME federico1: jpr: hmm, probably jpr: bug plan we discussed already hpj: i think it covers it. the goals are more high-level, in any event jpr: mw, sbrabec status of G:S updates? jpr: hpj: status on where-to-keep-the-code? hpj: want me to go ahead? captain_magnus: hpj: Go! jpr: we also need to get "Fix GNOME/Submitting Bugs page to include more information" hpj: ok sbrabec: jpr: G:S is now released for all distros, but it still needs a help with fixing remaining failures: https://build.opensuse.org/project/monitor?project=GNOME%3ASTABLE sbrabec: Last synced today morning. hpj: so, the issue is: where do we keep projects that are specific to openSUSE and not upstream captain_magnus: forge.novell.com? hpj: we have svn.opensuse.org, which the yast maintainers are using jpr: sbrabec: since that will always be ongoing, can we call the task done now in the wiki? hpj: i've been in touch with the guys managing that repository hpj: and basically they don't want more projects in it, since it lives outside the novell authentication infrastructure *gothica (n=pavel@87.251.157.6) has left #opensuse-gnome hpj: so has to be maintained separately suseROCKS: "Improve our package summaries and descriptions" on the wiki or the descriptions in rpm packages as seen in software management? hpj: we decided to try to use forge.novell.com and see if that suits our needs sbrabec: If we don't care much about 10.1, then yes. 10.2 and 10.3 has only a few failures, but they require further work. rodrigo: :( *munkii has quit (No route to host) jpr: sbrabec: ok hpj: that's where we are now. jpr: ok jpr: rodrigo: "Write (or find one already available) a script to convert irclog output to the wiki format" can we cancel that now that munkii is the man? captain_magnus: hpj: You don't have to create a separate project for each application in forge for this to work right? *munkii (n=munkii@217.54.184.58) has joined #opensuse-gnome hpj: captain_magnus: i don't know hpj: captain_magnus: i was assuming we would create a project for each application mw: i really don't want to use forge rodrigo: jpr: that is not needed now with munkii doing the irclog uploads jpr: rodrigo: ok, please remove it captain_magnus: mw: Why? captain_magnus: hpj: Hmm... That'd be a hell of a lot of projects to maintain... hpj: mw: i'd like some good reasons jpr: mw: "Improve our package summaries and descriptions" was discussed in the project meeting jpr: mw: using an upstream project that is doing that hpj: captain_magnus: do you know how many? jpr: in general, everyone please remember to update the tasks page mw: reasons: new projects require approval, it's unclear how maintained it really is (our internal version isn't) jpr: with ETA and Status captain_magnus: mw: forge is maintained... mw: jpr: what do you mean by an upstream project? jpr: and to volunteer jpr: ! rodrigo: yeah, just tried creating a project and I have to convince the admins, it seems jpr: mw: see project meeting log mw: ok captain_magnus: hpj: No, but rodrigo's osc scripts could probably tell you... suseROCKS: If "summaries and descriptions" has to do with cleaning up the lanaguage, I'd be glad to do it. I have a "period" fetish  :-)

*jpr has changed the topic to: Meeting in progress - Q&A - Non Developer | http://en.opensuse.org/GNOME/Meetings/20071025 | http://en.opensuse.org/GNOME jpr: Q&A! jpr: nothing in the wiki jpr: so i'll open the floor for all questions mw: What is our simplest yet "complete" package? Riggwelter: mw: define complete? mw: Riggwelter: -lang subpackage, uses gconf scriptlets, etc *btimothy pokes jgrant, eward, and jframe to ask their questions here abt. opensuse!  ;) mw: Riggwelter: i want to copy its spec to the wiki and comment and explain the living crap out of it Riggwelter: mw: lol :) jpr: mw, Riggwelter thats coming, we're on Q&A right now captain_magnus: jpr How do we follow up the bluetooth stuff from here? I am installing your updates and will try it, but it'd be no fun if bugzilla is the only place to go from here.... mw: jpr: that was a question! jpr: non-dev Q&A :-) mw: oh mw: oops jpr: captain_magnus: we follow up by testing jpr: and yes, reporting bugs jpr: and potentially doing feature work jpr: there are a few problems jpr: like pairing a keyboard at boot time jpr: that still need solving jpr: other questions this week? captain_magnus: Perhaps we should create a BT experience page then... captain_magnus: ...where people that have updated their packages for 10.3 can comment suseROCKS: I'm noticing problems with themes, notably with Crux, but also others. What is being done to address theme compatibility in GNOME? captain_magnus: And also, if it's valuable, have a separate section for Factory (if it's going to improve immensly for Factory) jpr: suseROCKS: A: not much currently, but it would be a good idea to include a theme audit on http://en.opensuse.org/GNOME/Ideas/11.0 jpr: captain_magnus: yes, we could have GNOME:Bluetooth, or use the bluetooth page abock afonit aka_druid alan_ apokryphos athrun aTypical abock afonit aka_druid alan_ apokryphos athrun aTypical matsakis mauropm metavoid mhutch munkii mw matsakis mauropm metavoid mhutch munkii mw suseROCKS: Yeah, I don't know how I stumbled across and figured out the Crux issue. Other users would have blamed the apps themselves unnecessarily. suseROCKS: I'm sure the themes are causing needless headaches for developers and bugzilla. jpr: aTypical, munkii, DimStar, lejo, psp250, xcasex no questions from the lurkers? aTypical: Sorry, I was afk and haven't been following the meeting. abock afonit aka_druid alan_ apokryphos athrun aTypical jpr: aTypical: is open Q&A time now psp250: jpr: Perhaps one, should bugs already posted upstream be posted on bno again in order to include patches before upstream does? *captain_magnus is going to hug his pillow... l8er! DimStar: not at the moment... they will come later, as always :-) aTypical: Has anyone addressed the issue with update always wanting focus? jpr: psp250: if you want an update against 10.3, definitely mw: psp250: right, what jpr said :) jpr: psp250: if its for 11.0, then maybe/maybe not jpr: aTypical: we have several bugs on that jpr: aTypical: federico1 is looking into aTypical: Has a schedule been set on 11.0? aTypical: Thanks, jpr jpr: not officially jpr: but 11.0 will be in about ~ 7 months

*jpr has changed the topic to: Meeting in progress - Reminders | http://en.opensuse.org/GNOME/Meetings/20071025 | http://en.opensuse.org/GNOME jpr: next meeting will be offset for asia and australia jpr: thats monthly jpr: and also in Nov. we'll slowly start moving to discussing more about 11.0 features Riggwelter: party on! jpr: either here or in focussed hacking meetings suseROCKS: Well I know I'll be on in November  :-) jpr: thats it for non-dev q&a

*jpr has changed the topic to: Meeting in progress - Packaging policy (mw)| http://en.opensuse.org/GNOME/Meetings/20071025 | http://en.opensuse.org/GNOME mw: Yo mw: the packaging polixy page (GNOME/Packaging) is mostly complete mw: i'm sure it could use some clarifications and expansions, but i tihnk it covers most things now mw: one thing i want to add, prob. in a different page, is a sample spec file for a gnome package mw: so i'm wondering what the simplest (yet "complete") package we have is Riggwelter: mw: Been looking for a simple (no frills) spec for you, can't find one in G:C at least :) mw: Riggwelter: neither could i :) Riggwelter: how about the new GNOME template? rodrigo: gnome-screensaver is simple AFAIR, not sure if complete as you like mw: Riggwelter: maybe we should find a small program to package jpr: do we need one example for libraries and one for apps? Riggwelter: rodrigo: does it have -lang and %gconf_foo? mw: jpr: hmmm, that's probably a good idea Riggwelter: mw/jpr: +1 mw: gnome-screensaver should at least have the gconf foo hpj: mw: we could package popomon :) mw: and i'm pretty sure a -lang package too rodrigo: Riggwelter: yes, has both it seems mw: hpj: does it use gconf? hpj: mw: no hpj: mw: it doesn't use much of anything Riggwelter: then gnome-screensaver may be a good one to use mw: hpj: hehe mw: iirc gnome-screensaver's spec is pretty long though jpr: AI: add sample spec files (mw) mw: and it has a number of rpmlint warnings, so i don't want to hold it up as a model to copy just yet :) jpr: it has funny stuff because of the xscreensaver stuff Riggwelter: rpm.org always used a fake one for its docs because no package is ever textbook mw: Riggwelter: we have the hello package for the same or similar purpose mw: we need gnome-hello Riggwelter: Rigg Jr's joined me :) Riggwelter: mw: we do mw: do we? Riggwelter: we need mw: oh, yes. :) btimothy: a fake textbook one would be great! mw: there's a gnome-hello tarball on ftp.gnome.org mw: i'll look at packaging that jpr: yes Riggwelter: a useful test for the template actually :) jpr: i think its ancient mw: last updated in 2003 jpr: mean as a starting base for development Riggwelter: mw: can you create it from the template - kill 2 birds with one stone mw: ok jpr: should we declare this action done? Riggwelter: nod jpr: and add a new action for samples? jpr: assuming that this will always need ongoing updates mw: right jpr: Riggwelter: are you satisfied from the community policy perspective? Riggwelter: very jpr: AI: create sample specs based on packaging policy (mw)

*jpr has changed the topic to: Meeting in progress - GNOME:Community policy status (Riggwelter) | http://en.opensuse.org/GNOME/Meetings/20071025 | http://en.opensuse.org/GNOME jpr: Riggwelter: go for it Riggwelter: Link: http://en.opensuse.org/GNOME/Community_Inclusion_Policy Riggwelter: As listed as an AI last week, we now link to the Packaging policy. Riggwelter: In light of that, I propose we say that this policy is complete (but may be amended in future) Riggwelter: The next step is a call to arms: If you have packages in GNOME:Community, please bring them up to code or, if they are obsolete, remove them. Riggwelter: (I'm in a baaadassss mood today) jpr: and feed the G:C beast! jpr: esp. if you have any packages you want considered for 11.0 proper jpr: AI: review current G:C packages (Riggwelter and other maintainers) jpr: feed Riggwelter and mw questions if there is any ambiguity jpr: thanks to sbrabec too for his old distro info Riggwelter: hear hear

*jpr has changed the topic to: Meeting in progress - Q & A | http://en.opensuse.org/GNOME/Meetings/20071025 | http://en.opensuse.org/GNOME jpr: any other Q&A topics? jpr: s/topics/questions/ jpr: seife: is https://bugzilla.novell.com/show_bug.cgi?id=280354 a won't fix because /etc/bluetooth/hcid.conf will no longer be used? bugbot: openSUSE bug 280354 in openSUSE 11.0 (GNOME) "YaST Bluetooth Configuration "Device Name" not reflected in Bluetooth-Applet "Adapter Name"" [Major,New] seife: without looking at it: yes :-) jpr: seife: ok seife: "will no longer be used" is not totally correct. It will be used, as long as the user does not change anything in the applet (if i understand it correctly). jpr: ok, so its intentional seife: But yes, yast bluetooth will hopefully vanish soon, and then everything will be good :-)= Riggwelter: yay seife: i just want to talk to the maintainer before filing a droprequest, that's better style :-) jpr: seife: and by default it won't exist then since yast2-bluetooth wont jpr: ok seife: hcid.conf will exist, but it will contain a default configuration from the package. jpr: ok seife: And Marcel's default configuration works. seife: It will probably vanish upstream sooner or later, because all users do with it is break their setup :-) jpr: other questions? seife: NEVER TOUCH hcid.conf !!1! Riggwelter: what, never? ;) jpr: seife: i guess the machine name won't be in the default config then? seife: unless you know what you are doing. I don't :-) Riggwelter: lol jpr: LAST CALL FOR QUESTIONS wberrier: :) seife: it is. it is "%h" or something like that. jpr: ok jpr: seife: i think the point of that bug is that it was confusing to change it in the applet (and have it updated) seife: name "BlueZ %h (%d)"; jpr: but not have it written out seife: Yes. That's why Yast bluetooth must die. jpr: but if that file is the set of *defaults* that makes sense seife: It is written out, just in /var/lib/bluetooth/$BADDR/... jpr: ok seife: I will also try to update the comments in hcid.conf.

jpr: THANK YOU ALL THIS MEETING IS DONE LIKE DINNER *jpr has changed the topic to: Meeting over - archives up soon | http://en.opensuse.org/GNOME/Meetings/20071025 | http://en.opensuse.org/GNOME