/srv/irclogs.ubuntu.com/2010/11/23/#ubuntu-meeting.txt

=== Amaranth_ is now known as Amaranth
=== Craig_Dem_ is now known as Craig_Dem
=== virtuald is now known as leagris
=== leagris is now known as virtuald
lifelessdo we have a asia pac meeting tonight08:02
nigelbthere wasn't one last week, so I'd assume yes08:04
=== azul_ is now known as jodh
rodrigo_diwic: is the meeting now?11:08
diwicrodrigo_, yes, but we seem to be the only ones present11:09
rodrigo_:)11:09
diwicrodrigo_, I pinged awolfson and TheMuso, I'll give them a minute or two and see if they show up11:11
diwicawolfson's on the channel, can't see ronoc anywhere11:11
diwicok, let's start11:11
diwic#startmeeting11:11
MootBotMeeting started at 05:11. The chair is diwic.11:11
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]11:11
diwicFirst; anybody want a topic to add, something we should discuss?11:12
TheMusoSo I assume we don't have an agenda...11:12
diwic[LINK] https://wiki.ubuntu.com/Audio/MeetingAgenda11:13
MootBotLINK received:  https://wiki.ubuntu.com/Audio/MeetingAgenda11:13
diwic[TOPIC] Anything in particular we want to discuss11:13
MootBotNew Topic:  Anything in particular we want to discuss11:13
diwicSo; a few days ago I found bug #579300, about OSS emulation removal and a few angry users having their features removed.11:14
ubottuLaunchpad bug 579300 in linux (Ubuntu) "Please disable CONFIG_SOUND_OSS* and CONFIG_SND_*OSS*" [Wishlist,Fix committed] https://launchpad.net/bugs/57930011:14
diwicI still think it's the right thing to do but I would like some arguments :-)11:15
diwicTheMuso, do you know more than I do?11:16
TheMusono11:16
diwicok; so basically, this was Daniel's decision and we trust him?11:16
TheMusoWe both made the decision, as Fedora and other distros have disabled it as well. We meant to get ossproxy packaged for maverick, but that didn't happen.11:17
rodrigo_so, this is to make oss apps use pulseaudio?11:17
TheMusoYes11:18
rodrigo_then yes, +1 :-)11:18
diwicTheMuso, so let's add an action item to package ossproxy for Natty, if we think that'll help11:19
diwicAny volunteers?11:19
TheMusoIt will help.11:19
TheMusoIf its trivial, I could probably get it packaged when I have a few spare cycles.11:19
TheMusoBut if someone wants experience in packaging, them feel free to take it, and I am happy to review it.11:19
rodrigo_same here, if it's too complicated, I might need help11:19
rodrigo_TheMuso, ok, I'll take it, and ask you for help if I can't, ok?11:20
TheMusoSounds good.11:20
diwic[AGREED] rodrigo_ to package ossproxy for Natty (with assistance from TheMuso if necessary)11:20
MootBotAGREED received:  rodrigo_ to package ossproxy for Natty (with assistance from TheMuso if necessary)11:20
diwicOr was that "Action"? Who knows :-)11:21
TheMusoI think action is what you want.11:21
diwic[ACTION] rodrigo_ to package ossproxy for Natty (with assistance from TheMuso if necessary)11:21
MootBotACTION received:  rodrigo_ to package ossproxy for Natty (with assistance from TheMuso if necessary)11:21
diwicOk, anything else?11:22
diwicLet's move on11:23
diwic[TOPIC] Any bugs we should look into in particular?11:23
MootBotNew Topic:  Any bugs we should look into in particular?11:23
diwicWhat's pestering you the most currently?11:23
rodrigo_not much, audio working quite good, even on natty :)11:24
diwicfantastic :-)11:24
diwicI'm currently trying to make upstream ALSA understand the need for consistent volume control naming11:24
rodrigo_there's still the GTK3 bugs for indicator, bit the desktop team has plans to coordinate that with unity11:25
rodrigo_so, no pestering there11:25
diwicThe "Front" volume control or switch sometimes control front line-out only, and sometimes headphones and/or internal speakers as well11:26
rodrigo_nice :)11:26
diwicFront as in the channel (i e not C/LFE/surround), not as in location11:26
diwicwith the result that we can't code PulseAudio in a way that'll work everywhere11:27
diwicI discovered that we have a PA patch that adds "Master Front", and we let that mean something controlling HP and Speakers as well, and let "Front" control the line-out only11:27
diwicBut upstream doesn't like the "Master Front" and want to change the other name instead11:28
diwic*sigh*11:30
diwicso now that I've finished moaning, let's move on11:30
rodrigo_:)11:30
diwic [TOPIC] Anything in particular we've been working on the previous week11:30
diwic[TOPIC] Anything in particular we've been working on the previous week11:30
MootBotNew Topic:  Anything in particular we've been working on the previous week11:30
diwicWell, I've actually started a little on the audio apport symptom11:31
diwicI wrote a "Jack" parser from the codec file, see http://pastebin.ubuntu.com/535499/11:32
diwicDo you think it looks good?11:32
TheMusoCool.11:32
rodrigo_looks ok, but too complex for basic users, I think11:33
rodrigo_but looks ok for someone really knowing what is it11:34
diwicrodrigo_, hmm? It was based on the suggestion on the UDS session that normal users want to relate to the Jacks rather than the card name11:34
rodrigo_ah, ok11:34
TheMusoSince I am on rotatino, I just did a little reading of bug mail, and merged packages from Debian, mainly jack stuff.11:34
diwicrodrigo_, but I'm open for suggestions11:35
diwicTheMuso, so anything interesting coming in from Debian at this point?11:35
rodrigo_on my part, since we now have libcanberra-gtk3 in natty, started working on packaging stuff that use it, like gnome-media11:35
rodrigo_diwic, not sure what to suggest, so I'll shut up for now :-)11:35
diwicrodrigo_, ok, let me know if you have improvement ideas11:36
rodrigo_yes, I will11:36
TheMusonot that I know of.11:36
TheMusonothing jack wise anyway.11:36
rodrigo_although I guess we could accompany that in the UI with a nice picture of the jacks11:36
rodrigo_that should make it user-friendly11:36
rodrigo_can we do that in the apport stuff?11:37
TheMusoOh rtkit is now synced with Debian, so rtkit is not maintained in pkg-multimedia repos in debian.11:37
rodrigo_that is, add an image to the dialog?11:37
TheMusos/not/now/11:37
diwicTheMuso, do you have upload rights for those things in Debian?11:37
TheMusoNo.11:37
TheMusoBut I have git commit access, so if we need something urgently, I can always temporarily create an Ubuntu branch, make an Ubuntu package, and merge the changes into debian's branch, and an upload to debian will straighten things out.11:38
diwicrodrigo_, it's going to be hard for the cli version ;-)11:39
rodrigo_diwic, well, average users would probably always use the GUI version, right?11:39
persiaThere's a fair few folk active in Ubuntu with upload access for pkg-multimedia stuff, so it's not typically hard to get an upload there.11:39
diwicrodrigo_, but for gtk, it should be possible, I think that'll require a little more knowledge in apport than I currently have11:40
rodrigo_diwic, ok, I'll have a look11:40
diwicrodrigo_, are you familiar with apport/python?11:40
rodrigo_not much with apport, but a little bit, so will look at it11:41
diwicok11:42
diwicrodrigo_, lets chat a little about that after the meeting if you like11:43
rodrigo_ok11:43
diwicOther than that, I've been quite busy with HWE work these weeks, so there hasn't been that much time to do other things11:44
rodrigo_HWE?11:44
diwicHWE = HardWare Enablement, i e what I'm hired for :-)11:45
rodrigo_ah, ok :)11:45
diwicAnything else?11:45
diwiclet's move on11:46
diwic[TOPIC] Anything in particular we plan to do the coming week?11:46
MootBotNew Topic:  Anything in particular we plan to do the coming week?11:46
rodrigo_for me, packaging ossproxy and look at the apport stuff, apart from packaging more stuff that uses the libcanberra-gtk3 thing11:46
diwicI'll hope I have some time to continue on the apport symptom, perhaps also start on some of the pro-audio-secured stuff.11:47
TheMusoMe, nothing on the audio front, unless I am prodded by someone to review/upload audio related packages. :)11:47
diwicAs for these meetings, I think every 14 days will suffice, rather than once a week, or what do you think?11:48
TheMusoSeconded.11:49
diwicBtw, do any of you have gmail accounts?11:49
TheMusoNo, but I do have a canonical calendar hosted on Google.11:50
TheMusoi.e a canonical.com google calendar.11:50
diwicTheMuso, the same goes for me, and it might cause problems with the fridge calendar11:51
diwicBut I'll struggle with it to next meeting :-)11:51
TheMusoheh11:51
rodrigo_diwic, yes, rodrmoya@gmail.com11:52
diwicrodrigo_, would you mind following https://wiki.ubuntu.com/Fridge/Calendar instructions and try to set up a meeting dec 7?11:53
diwicrodrigo_, and see if it works better for you?11:54
rodrigo_ok11:54
diwic[AGREED] Meeting interval is every 14 days, next meeting is Dec 7.11:55
MootBotAGREED received:  Meeting interval is every 14 days, next meeting is Dec 7.11:55
awolfsonhello11:55
TheMusoIs there anything else that I need to be present for? Its getting late here...11:55
diwicTheMuso, I was about to end the meeting unless awolfson or someone else has anything to add?11:56
rodrigo_so, Dec 7 at 12PM CET, right?11:56
diwicrodrigo_, right11:56
TheMusodiwic: sounds good.11:56
diwicok, let's end the meeting then11:57
diwic#endmeeting11:57
MootBotMeeting finished at 05:57.11:57
diwicthanks for attending11:57
TheMusothanks folks.11:57
diwicawolfson, a little late perhaps :-)11:58
awolfsonwhen meeting starts? i thought 7:00 EST?12:00
rodrigo_diwic, ok, seems it worked12:00
awolfsonooo, looks like 6:00 EST, because of day saving12:01
rodrigo_ugh, I removed it12:02
diwicawolfson, hmm, hope I didn't calculate things wrong for you12:02
diwicawolfson, sorry :-(12:02
awolfsondiwic, so it is 6:00 my time ?12:03
diwicawolfson, I'm afraid so, thought you were at UTC-412:04
awolfsonit is 7:04 here now12:04
awolfsonI guess it is daylight saving change12:04
diwicawolfson, maybe12:06
=== BlackZ_ is now known as BlackZ
=== yofel_ is now known as yofel
NCommander#startmeeting12:59
MootBotMeeting started at 06:59. The chair is NCommander.12:59
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]12:59
* NCommander notes the laptop clock is a bit fast12:59
NCommanderwho's here?12:59
NCommanderdavidm_: GrueMaster_: ogra: ping?13:01
NCommanderpersia: ?13:01
ogramoo13:02
GrueMaster_me13:02
NCommanderoh good, signs of life13:02
=== GrueMaster_ is now known as GrueMaster
ogradavid is on vacation13:02
ograas well as ricardo13:02
GrueMasterno life here13:02
NCommander[link] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010112313:03
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010112313:03
* NCommander feels hidious so wishes to make this a short meeting13:03
* ogra fixes the bugtasks link13:03
NCommander[topic] Action Item Review13:03
MootBotNew Topic:  Action Item Review13:03
NCommanderskipping non-president people's items13:04
ograricardos item is done13:04
NCommander[topic] ogra_ac and rsalveti to talk to davidm on proper approach to fix Qt13:04
MootBotNew Topic:  ogra_ac and rsalveti to talk to davidm on proper approach to fix Qt13:04
ograwe did that during the meeting iirc13:04
NCommanderoh13:04
NCommander[topic] GrueMaster to fix assigned bugs list13:04
MootBotNew Topic:  GrueMaster to fix assigned bugs list13:04
ograafter you made it an action13:04
GrueMasterogra fixed it before I could.13:05
ograsorry :)13:05
NCommander[topic] ogra_ac to follow omap3 kernel situation13:05
MootBotNew Topic:  ogra_ac to follow omap3 kernel situation13:05
ograstill in progress13:05
ograand i looked at ebay13:05
ograunder which name is that soul offered ?13:05
* ogra couldnt find anything13:06
NCommanderogra: discovered that eBaying one's soul is against the Terms of Service13:06
ograpfft13:06
ograjust name it differently :)13:06
NCommander/dev/life?13:06
ograso how is that mono stuff going forward ?13:07
NCommanderMade some progress, discovered we're not building mono with VFP, and have some test cases13:07
ogracool !13:07
NCommanderGot sidetracked by being patch pilot and high priority stuff from davidm plus the fact that my lungs are full of uninvited guests13:08
ograwell, patch politing is fun :)13:08
NCommanderAlso discovered that cars beside my own are prone to having their doors freeze shut and I'm going to probably be spending part of tomorrow trying to fix that.13:08
ograput graphite on the gasket13:09
* NCommander notes its a *very* cold day in Portland13:09
NCommanderogra: not my car. Wish it was, I won't be afraid I was going to pull off a handle or something13:09
NCommanderAnyway13:09
NCommander[topic] Standing Items13:09
MootBotNew Topic:  Standing Items13:09
ograheh, rather the gasket13:09
NCommander[link] http://people.canonical.com/~pitti/workitems/natty/canonical-arm.html13:09
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/natty/canonical-arm.html13:09
NCommander[link] http://people.canonical.com/~pitti/workitems/natty/canonical-arm-natty-alpha-1.html13:10
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/natty/canonical-arm-natty-alpha-1.html13:10
ograwe're getting terribly close to the trend line13:10
NCommanderhrm13:10
ogradont forget A1 in dec. 2nd13:10
NCommandermy specs are STILL not there13:10
NCommander*grumble*13:10
NCommanderoh wait13:10
ograthey are13:10
NCommanderyes they are, I already did my workitems for this cycle13:10
NCommanderer13:10
NCommandermilestone13:10
NCommander*/half dead*13:11
NCommanderI thikn I forgot to strike it off my TODO list ...13:11
NCommander[link] http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html13:11
MootBotLINK received:  http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html13:11
ograwrong link13:11
ogra!!13:11
* NCommander refreshs13:11
* ogra fixed it on the wiki13:11
NCommander[link] http://qa.ubuntu.com/reports/team-assigned/canonical-arm-assigned-bug-tasks.html13:12
MootBotLINK received:  http://qa.ubuntu.com/reports/team-assigned/canonical-arm-assigned-bug-tasks.html13:12
GrueMastershould be [link] http://reports.qa.ubuntu.com/reports/team-assigned/canonical-arm-assigned-bug-tasks.html13:12
NCommanderer no13:12
ograshows that persia is a slacker :)13:12
NCommanderI didn it wrong twice >.<13:12
* NCommander notes it would be nice if he attended our meetings ...13:12
ograyes, it would13:12
NCommanderFinally confirmed bug #62674913:12
ubottuLaunchpad bug 626749 in flash-kernel (Ubuntu Maverick) "flash-kernel tries to use MTD devices on OMAP4 when no flash-kernel.conf exists" [Medium,Confirmed] https://launchpad.net/bugs/62674913:12
* NCommander coughs13:12
ograbut the time is bad for him13:12
NCommanderThere's no actual bug here13:12
persiaUm, you folk have a funny definition of "attendance"13:12
NCommanderCause the code is doing exactly what its supposed to13:13
ograheh13:13
ograNCommander, its not13:13
ograobviously it doesnt use a method the HW can deal with13:13
NCommanderogra: I wrote the code to intentionally try to write to NAND if it was on a Beagle Board13:13
NCommanderBeagle XM says its a Beagleboard13:13
ograyes13:13
NCommanderI therefore say its a hardware bug, and we need ot fix it software :-)13:13
NCommanderThus I'm not at fault13:13
ograyou are13:13
NCommander:-P13:13
GrueMasterbeagleXM is omap313:13
ograsince you added that code13:14
ogramake it work or remove it13:14
NCommanderogra: the cirmstances which the code is being run changed :-P13:14
persiaIt7s generally better to do things like try to detect if there *is* MTD, rather than depending on detection.  Such work is likely to be much more applicable in the future.13:14
NCommanderbut I plan on fixing it anyway13:14
NCommandersince I have an XM now13:14
ograright13:15
ogramore checks please :)13:15
=== rodrigo__ is now known as rodrigo_
NCommanderpreferable with five figures on them :-)13:15
NCommander*preferably13:15
ograthat should be possible independently from the board type13:15
NCommanderogra: yeah, I plan to add something look for the mtd device and maybe even check for u-boot or something in flash13:15
ograalso for a vfat containing uImage etc etc13:16
ograyou need to cover all possible cases to make it proper and generic13:16
NCommanderogra: right that code is there and is known to work13:16
persiaWell, kinda.  It works sometimes, for some hardware.13:16
ogra.oO(tell that to Neko)13:16
NCommanderWhat isn't working is that the code assumes that a board saying its a Beagle has NAND13:16
NCommanderThat assumption proved to be incorrect13:17
ograthe bug as about a blaze iirc13:17
persiaMTD detection, partitioning management, etc. is kinda funny, in several annoying ways.13:17
ograwhich has only eMMC13:17
NCommanderd-i has a lot of ugly code dealing with it :-/13:17
ografor which we have no solution yet afaik13:17
ograbut your code needs to take that into account too13:17
NCommanderindeed13:17
NCommander[topic] Kernel Status (cooloney)13:17
MootBotNew Topic:  Kernel Status (cooloney)13:17
ogranot around13:18
GrueMasterUntil I get an upgraded blaze, we have no way of testing it.13:18
ograi have an upgrade card13:18
ograjust not in the balze atm13:18
ogra*blaze13:18
NCommander[topic] QA Status (GrueMaster)13:19
MootBotNew Topic:  QA Status (GrueMaster)13:19
GrueMasterCurrently working on test for QT neon.13:19
ograi thought you can only do that next week ?13:20
GrueMasterFriday's omap4 image fails to boot after 2nd reboot.  Not sure if it is X related.  Kernel segfaults.13:20
ogradid you dig deeper into why the omap4 images dont work ?13:20
ograah13:20
GrueMasterNot yet.13:20
ogramight be a toolcahin issue13:21
ogra*toolchain13:21
GrueMasterI have a pastebin of the console log.13:21
ograhttps://blueprints.launchpad.net/ubuntu/+spec/none-kernel-n-misc has a workitem for us13:21
ogracould you take an onap4 image and replace the kernel with the linaro omap3 one ?13:21
ograand see how that works13:22
ogra*omap13:22
ogracool, file a bug13:22
GrueMasterWill it work on omap4?  I only have a panda.13:22
GrueMasterI'll file a bug when I can narrow down the segfault.13:23
ograoh, you dont have your XM with you13:23
ografile the bug asap probably someone can tell something about it13:23
GrueMasterI only have my panda.  Thisis a holiday week and I had only planned on working on my blueprints this week.13:24
GrueMasterWill do.13:24
ogramight be because the kernel wasnt recompiled with the new toolchain or so13:24
GrueMasterIt boots up to mounting rootfs.13:24
GrueMasterjasper boot sequence runs fine.13:25
ograoh13:25
ograthats different indeed13:25
GrueMasterexactly.13:25
ogramust be userspace then13:25
GrueMastersee http://paste.ubuntu.com/535244/13:25
GrueMasterI have limited resources, but will try to narrow it down.13:26
NCommandercan I mov eon?13:26
GrueMastergo13:26
ograchvt: can't open console13:27
ograthats your main issue13:27
NCommander[topic] ARM Porting/FTBFS status (NCommander)13:28
MootBotNew Topic:  ARM Porting/FTBFS status (NCommander)13:28
NCommandermostly mono work13:28
ograany idea how KDE is progressing ?13:28
ogradid you talk to ScottK13:28
* ogra is still waiting for the QT mail from asa13:28
ograc13:28
NCommanderogra: didn't have a chance yet13:29
NCommanderwill do so13:29
ogragiven that he wanted to discuss with thiago at meego conf13:29
NCommander[action] NCommander to speak with ScottK on KDE progress13:29
MootBotACTION received:  NCommander to speak with ScottK on KDE progress13:29
ograi see him going wild on the different ARM channels13:29
ograwhich is awseome :)13:29
NCommander[topic] ARM Image Status (ogra, NCommander)13:29
MootBotNew Topic:  ARM Image Status (ogra, NCommander)13:29
GrueMasterNot working.13:30
ograU1 acts up today13:30
ograu-n-d-s was fixed13:30
ograi hope if U1 is in sync we will have images again13:31
ogranothing more about image status13:31
NCommander[topic] abo13:33
MootBotNew Topic:  abo13:33
NCommanderer13:33
NCommander[topic] AOB13:33
MootBotNew Topic:  AOB13:33
ograBOA ?13:33
ogranothing here ... i guess meeting time has to wait until we are complete again13:34
ograpersia, anything from you ?13:35
ograi.e. about ubuntu-armel and work items ?13:35
ograi.e. reveal your plans to a wider audience13:36
persiaHrm?  Oh, yeah, I want there to be an Ubuntu ARM team, rather than just Canonical ARM.13:37
persiaI'm not sure how much there is to say about that: it's in part up to you to want to do that :)13:37
ograwhich is there, but mainly used for bug triage atm13:37
ograwell, its trivial to add another WI tracker, i just thought you wanted to elaborate a bit on it13:38
ograi.e. do you want its status covered in this meeting etc13:38
persiaDunno how much to elaborate.  I know of several things happening with ARM by people who don't much attend this meeting, so my other encouragemetns to you are mostly about being inclusive.13:39
ograand make sure NCommander invites the people from that team to attend it13:39
ograjust having a tracker if nobody watches it doesnt seem to make much sense to me13:40
persiaWell, if there is a meeting that tracks some ARM stuff, I'd rather track all ARM stuff, and encourage more participants.  I think it's up to individual folk whether they want to participate, to some degree, but I think it would be worthwhile to have an overview of everything happening in ARM.13:40
ograso it would need additional actions around that13:40
persiaAdditional actions?13:40
ograi.e. invites from NCommander and a note in the meeting announcement etc13:40
ograNCommander, oh, btw, the meeting announcement ... we're the ARM team ;(13:41
ogra;)13:41
ograand we should mobve to a new namespace on the wiki13:41
* GrueMaster never saw one this week.13:41
persiaThe meeting announcement needs help anyway.  Fixing it one way or the other is probably the same work.13:41
ograNCommander, can you handle that ?13:41
ograGrueMaster, it goes to ubuntu-devel now, since thats our new mailing list13:42
GrueMasterargh13:42
ograGrueMaster, make sure to be subscribed to it and probably u-d-discuss13:42
ograwe talked about it before13:42
ograu-mobile is essentially dead13:42
ogra(not sure david removed it completely yet, but that will happen soon)13:43
NCommanderanything else, or can I close it out?13:44
* NCommander is feeling pretty close to death ATM13:44
* ogra waits for answers from NCommander 13:44
ogra(and probably some actions)13:44
ograbut after that you can happily close :P13:45
persiaogra, So, you poked me to talk about a wider team definition.  Do you have an opinion on that?13:45
NCommanderogra: which answers?13:45
ograwell, as long as the team is included and invited13:45
ogra<ogra> NCommander, oh, btw, the meeting announcement ... we're the ARM team13:46
ogra<ogra> and we should mobve to a new namespace on the wiki13:46
ogra<ogra> NCommander, can you handle that ?13:46
persiaogra, The point of inclusiveness is that *everyone* is invited :)  I very much don't want to exclude you (or anyone else).13:46
ograpersia, no, but the team members need to know about it13:46
persiaI'm even happy to create a teamspace on the wiki for an ARM team, if there is to be an open ARM team.13:46
ograso if the announcement needs rephrasing in that direction and the agenda needs points for that, they need to be added13:47
ograi.e. have a ARM Community topic13:47
persiaNCommander, Give me actions for those, and when you're feeling better, I'll feed you text :)13:47
ScottKNCommander and ogra: Qt/KDE is blocked on a gcc fix. The gcc patch was posted upstream for review yesterday, so hopefully we'll see something soon.13:47
ograand point out that everyone is invited in the meeting announcement13:47
NCommander[action] persia to handle namespace renaming13:48
MootBotACTION received:  persia to handle namespace renaming13:48
persiaogra, You can do something about the WI tracker and bug list?13:48
ograwhy the bug list ?13:48
ograi can add another team to the tracker, yes13:48
persiaSame rationale as the WI tracker, really.13:48
ograyou need to give me a mail address for the responsible person for broken tracker entries13:48
* ogra doesnt understand13:49
ograwe never subscribe ubuntu-armel to any bugs13:49
ograbut we use it to subscribe the whole team to it13:49
persiaSure, but members are assigned bugs.13:49
ograpersia, ping bdmurray about that, he can help13:50
persiaSure.  I'll do that.13:50
ograNCommander, [action] persia and NCommander to work out new meeting announcement text13:50
ograNCommander,  [action] persia to make the bugsquad create a bug overview page for ubuntu-armel13:51
ogra(though the latter will highly overlap with our team list i think)13:51
ograNCommander, add these two actions and close the meeting (then back to bed with you !)13:52
persiaogra, I expect lots of overlap between Ubuntu ARM and Canonical ARM, which I consider a good thing :)13:53
ograpersia, you are aware that no other team does such a distinction ?13:53
NCommander[action] persia to make the bugsquad create a  bug overview page for ubuntu-armel13:53
MootBotACTION received:  persia to make the bugsquad create a  bug overview page for ubuntu-armel13:53
NCommander[action] persia and NCommander to work out new  meeting announcement text13:53
MootBotACTION received:  persia and NCommander to work out new  meeting announcement text13:53
NCommander#endmeeting13:53
MootBotMeeting finished at 07:53.13:53
ograNCommander, thanks13:53
=== nhandler_ is now known as nhandler
zulhello16:00
JamesPageo/16:00
zulttx stop stalking :)16:00
ttxo/16:00
hallyn\o16:00
JamesPagewho's in the seat this week?16:03
hallynis Daviey around?16:04
hallynhe missed his turn last week, poor sod16:04
hallynotherwise i'ts you, JamesPage :)16:05
hallynthough, do we think we have a quorum?16:06
Davieyeek, sorry16:06
JamesPagesaved by the bell (or Daviey in this case...)16:07
DavieyWho do we have?16:07
JamesPageo/16:08
Davieynobody else!?16:08
hallyno/16:08
ttxo/16:08
smb\o16:08
* Daviey glares at SpamapS 16:09
* SpamapS beams at Daviey16:09
Davieysmoser / kirkland / hggdh ?16:09
smosero/16:09
SpamapSI had a screaming baby to deal with.. dunno what their excuses are. ;)16:09
Daviey#startmeeting16:10
MootBotMeeting started at 10:10. The chair is Daviey.16:10
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]16:10
Daviey[TOPIC] Review ACTION points from previous meeting16:10
MootBotNew Topic:  Review ACTION points from previous meeting16:10
DavieyALL: please check the SRU tracker https://wiki.ubuntu.com/ServerTeam/SRUTracker and help out with verification16:10
smoser(excuse: i am actually on vacation )16:10
DavieyDid anybody have a chance to look?16:10
SpamapSsmoser: well then go away. ;)16:10
Davieysmoser: Vaca? er what?  What is this?16:11
SpamapSDaviey: I did and helped out where I could. I think we should carry that one over to next meeting.16:11
DavieyAgreed16:11
Daviey[ACTION] please check the SRU tracker https://wiki.ubuntu.com/ServerTeam/SRUTracker and help out with verification (carried over)16:11
MootBotACTION received:  please check the SRU tracker https://wiki.ubuntu.com/ServerTeam/SRUTracker and help out with verification (carried over)16:11
SpamapSat least until I complete my action to send a proposal out to ubuntu-devel ;)16:11
Davieyrobbiew to review /ServerTeam wiki16:11
Davieynot here... so carry over16:11
Daviey[ACTION} robbiew to review /ServerTeam wiki16:11
MootBotACTION received: [ACTION} robbiew to review /ServerTeam wiki16:11
DavieySpamapS to email a concrete proposal for addressing SRU verification backlog16:12
SpamapSnot done, carry to next week16:12
Daviey[ACTION] SpamapS to email a concrete proposal for addressing SRU verification backlog (carried over)16:12
MootBotACTION received:  SpamapS to email a concrete proposal for addressing SRU verification backlog (carried over)16:12
Daviey[TOPIC] Natty Development16:12
MootBotNew Topic:  Natty Development16:12
SpamapSHas anyone else run into FTBFS's due to the linker/compiler changes?16:13
DavieyFirstly, I think we are still polishing blueprints and creating work items16:13
DavieyIs anyone blocked on any of these parts?16:13
DavieySuper!16:13
* SpamapS predicts the shortest meeting evar ;)16:14
DavieySpamapS: I came across a similar bug to you, regarding DSO :)16:14
Davieylibssl DSO'ing libcrypto16:14
DavieyAnyone have anything else for Natty devel ?16:14
Davieyok, moving on16:15
SpamapSDaviey: yeah thats pretty common I think because almost nobody uses libssl w/o touching libcrypto in some way16:15
DavieyYup.. so we possibly have more FTBFS's at the moment16:15
Daviey.... normally just requires adding -lcrypto to the linker line16:16
Daviey[TOPIC] Weekly Updates & Questions for the QA Team (hggdh)16:16
MootBotNew Topic:  Weekly Updates & Questions for the QA Team (hggdh)16:16
Davieyhggdh: are you here?16:16
Davieymoving on..16:17
Daviey[TOPIC] Weekly Updates & Questions for the Kernel Team (smb)16:17
MootBotNew Topic:  Weekly Updates & Questions for the Kernel Team (smb)16:17
smbThere is not so much updates this week16:17
Davieysmb: sadly smoser isn't here to ask about EC2 kernel...16:17
Daviey... but it looks fixed, right?16:17
smbMostly trying to find out why natty does not boot that well on i38616:17
smoseryeah, that will result in a boring conversation. without me, there wont be any kernel bugs.16:18
smbBut as, when it fails, there are no messages at all, most of the time, I am currently trying to get a local env together based on centos16:18
Davieysmoser: life is a boring conversation without you16:18
Davieysmoser: get back to drinking sangria on the beach.16:18
smbApart from that, if there are questions... :)16:18
smb..16:18
SpamapSsmoser: not true! I brought an NFS bug16:19
SpamapSbug 66129416:19
ubottuLaunchpad bug 661294 in linux (Ubuntu) "System lock-up when receiving large files (big data amount) from NFS server" [Medium,Confirmed] https://launchpad.net/bugs/66129416:19
Davieysmb: Okay... so you are working on this at the moment with smoser?16:19
smbCurrently without smoser because he is on vacation16:19
smbBut otherwise yep16:19
SpamapSsmb: there seems to be a patch linked to in the comments that directly addresses this issue.. wondering how likely it is that it will be applied in natty16:20
Daviey[ACTION] Follow up on EC2 status16:20
MootBotACTION received:  Follow up on EC2 status16:20
Davieysmb: SpamapS's question ?16:20
smbSpamapS, As this is the first time I seem to see that bug mentioned, it is hard to tell a lot16:20
Davieysmb: Understood... putting you on the spot a lttle... not essential for a response now16:21
SpamapSsmb: thats fine, I just wanted to get it on your radar.16:21
smbSpamapS, Success16:21
Davieybut can you get someone from your team to update the bug before next week please? :)16:21
smbI put it on the list16:22
Daviey[ACTION] Kernel team to follow up on bug #https://launchpad.net/bugs/66129416:22
MootBotACTION received:  Kernel team to follow up on bug #https://launchpad.net/bugs/66129416:22
Davieymoving on?16:22
* SpamapS does a fist bump w/ smb and then gets nostalgic for mathiaz.. <sniff>16:22
Daviey(thanks smb)16:23
Daviey[TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)16:23
MootBotNew Topic:  Weekly Updates & Questions for the Documentation Team (sommer)16:23
Davieyhe isn't here :(16:23
Daviey[TOPIC] Weekly Updates & Questions for the Ubuntu Community Team (kim0)16:23
MootBotNew Topic:  Weekly Updates & Questions for the Ubuntu Community Team (kim0)16:23
Davieyhe isn't here :(16:23
Daviey[TOPIC] Open Discussion16:24
MootBotNew Topic:  Open Discussion16:24
Davieynothing here..16:24
Davieyanyone?16:24
SpamapSI was thinking one thing..16:24
SpamapSwhich is just that the WI tracker seems very incomplete..16:24
DavieySpamapS: is it family friendly?16:24
DavieySpamapS: it would be, the WI's aren't complete yet16:25
zulSpamapS: because some of us are blocked on somethings16:25
Davieyaddionally, does the WI pull in non-approved specs?16:25
SpamapSright, I just was going to ask when its supposed to be?16:25
SpamapSDaviey: no it does not16:25
SpamapSSo thats probably why it seems so low16:25
DavieyI imagine this week, robbiew will be doing a final pass16:25
Davieyjumping on people to get them complete16:25
SpamapSAlso I wonder if here is the place to discuss the ubuntu-server package set?16:26
SpamapSI think we should actually discuss it next week...16:26
DavieySpamapS: I'm not sure we have a wide enough audience tbg16:26
SpamapSlight crew today16:26
Davieytbh*16:26
zulprobably...but what has been done and put it on the agenda for next week :)16:26
Davieymoving on?16:26
Daviey[TOPIC] Announce next meeting date and time16:27
MootBotNew Topic:  Announce next meeting date and time16:27
zulyeah i just have one question16:27
zulwhy is there a seperate "cloud community meeting"16:27
SpamapSOh yeah good point zul16:27
DavieyGooooooood question!16:27
SpamapSespecially since we have a community member who never shows up to these meetings.16:27
ttxwho ?16:28
SpamapSs/community/community team/16:28
Davieyzul: Do you want to take the action of speaking with kim0 to find out what it is about?16:28
zuli was going to bug jono about it16:28
Daviey... and find out if it might be better to unify the meeting16:28
ScottKActually I think it'd be kind of nice to split all the cloud stuff into it's own meeting.16:28
Davieyzul: I would speak with kim0 first.16:28
zulDaviey: ack16:29
SpamapSScottK: I think thats worthy of a discussion here definitely.16:29
DavieyScottK: Well yes... but our community isn't wide enough to split yet :)16:29
DavieyNext meeting, Tuesday 2010-11-23 at 1600 UTC - #ubuntu-meeting16:29
DavieyBe there, or be square!16:30
ScottKDaviey: I think the emphasis on cloud stuff depresses community involvement from those who haven't signed up for the right drugs.16:30
DavieyScottK: ack.. the whole team know this.... but until the team becomes large enough, and a critical mass.... we can then talk about seperating16:30
DavieyScottK: Considering many of the Ubuntu Server team are working on cloud stuff... this meeting would be even more lonely :)16:31
SpamapSIts worth having the discussion here at some point soon16:31
Daviey#endmeeting16:31
MootBotMeeting finished at 10:31.16:31
ScottKDaviey: On the other hand, I think the server community will keep getting smaller until you make the split.16:31
SpamapSDaviey: thanks!16:31
DavieyScottK: Do you want to add it to next weeks agenda?16:31
SpamapSScottK: that seems a bit extreme. The server product is essential to the cloud, the overlap is *huge*16:32
ScottKDaviey: I'm not usually available at this time, so I'm not the best one for it.16:32
DavieyScottK: Well that is a challenge :(16:32
ScottKSpamapS: That's an interesting theory that doesn't seem to be matched by Canonical's messaging on the subject.16:32
DavieyScottK: you are the most vocal about this concern, so I think you are a required participant of that discussion16:32
DavieyScottK: Can you add it to the agenda for a meeting you can attend?16:33
ScottKDaviey: I'm only rarely available on Tuesdays (only here now because a meeting got cancelled today).16:33
ScottKI have no way of knowing when that would be.16:33
Daviey:(16:33
DavieyScottK: Is there someone you can load as a proxy?16:34
ScottKNot really.16:35
bjf#17:00
bjf# lets "get 'er done"!17:00
bjf#17:00
JFowoo!17:00
bjf#startmeeting17:00
MootBotMeeting started at 11:00. The chair is bjf.17:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]17:00
apwo/17:01
ckingo/17:01
jjohanseno/17:01
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting17:01
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick17:01
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting17:01
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick17:01
bjf#17:01
bjf# NOTE: '..' indicates that you are finished with your input.17:01
bjf#17:01
bjf[TOPIC] ARM Status (bjf)17:01
bjf * Marvel (mvl-dove)17:01
bjf   * Marvell's latest LSP, 5.3.6 has been integrated into our tree and uploaded.17:01
bjf * Freescale (fsl-imx51)17:01
bjf   * Nothing new this week17:01
MootBotNew Topic:  ARM Status (bjf)17:01
bjf * Texas Instruments (ti-omap)17:01
bjf   * Bug #666267 - Added DKMS package to this bug and asked for help from Mario. TI is17:01
bjf     still based on the 2.6.35 kernel. It is unlikely that we will be cherry-picking17:01
ubottuLaunchpad bug 666267 in linux-ti-omap4 (Ubuntu) "Cross compiled headers package breaks DKMS compilation" [Medium,New] https://launchpad.net/bugs/66626717:01
bjf     patches due to their proliferation all over the tree. They (TI) may move to 2.6.3817:01
bjf     next year.17:01
bjf..17:01
bjf[TOPIC] Release Metrics (JFo)17:02
MootBotNew Topic:  Release Metrics (JFo)17:02
JFoRelease Meeting Bugs (6 bugs, 13 Blueprints)17:02
JFo==== Alpha 1 Milestoned Bugs (13 across all packages (down 1)) ====17:02
JFo * 0 linux kernel bugs (no change)17:02
JFo * 0 linux-ti-omap bugs (no change)17:02
JFo * 0 linux-meta-ti-omap bug (no change)17:02
JFo==== Release Targeted Bugs (95 across all packages (up 9)) ====17:02
JFo * 3 linux kernel bugs (no change)17:02
JFo * 0 linux-ti-omap bugs (no change)17:02
JFo * 0 linux-meta-ti-omap bug (no change)17:02
JFo==== Milestoned Features ====17:02
JFo * 1 blueprints (Including HWE Blueprints)17:02
JFo==== Bugs with Patches Attached:140 (up 2) ====17:02
JFo * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]]17:02
JFo * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]]17:02
JFo..17:02
bjf[TOPIC] Blueprints: Natty Bug Handling (JFo)17:03
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling17:03
MootBotNew Topic:  Blueprints: Natty Bug Handling (JFo)17:03
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling17:03
JFonothing to report this week17:03
bjf[TOPIC] Blueprints: Kernel Configuration Review (apw)17:03
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-config-review17:03
MootBotNew Topic:  Blueprints: Kernel Configuration Review (apw)17:03
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-config-review17:03
apwAll configuration changes from the UDS review session are now applied and uploaded.  Also the AGP drivers of interest have been identified and moved built-in.  Only two items remain, neither critical for natty-alpha-1.  These items are still on track for natty-alpha-1 completion.17:03
apw..17:03
bjf[TOPIC] Blueprints: Enhancements to the firmware test suite (cking)17:03
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-firmware-test-suite-enhancements17:03
MootBotNew Topic:  Blueprints: Enhancements to the firmware test suite (cking)17:03
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-firmware-test-suite-enhancements17:03
ckingChanges to fwts (natty development branch):17:03
cking * Add in methods tests - 69 new tests to exercise AML Methods17:03
cking * Added error checking with CMOS reads17:03
cking * Improved FACS 32/64 pointer mismatch checks in FADT17:03
cking * Check for \_SB_._OSC buffer overflows17:03
cking..17:04
bjf[TOPIC] Blueprints: Handling of Deviations from Standard Kernels (smb)17:04
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-frankenkernel-maintenance17:04
MootBotNew Topic:  Blueprints: Handling of Deviations from Standard Kernels (smb)17:04
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-frankenkernel-maintenance17:04
smbJust sent out some rfc for the in-tree documentation17:04
smbSuggestion was for json format but making it simpler for a script seems not a good reason for changing the format for now17:05
smbSo I would still go with the maintainers format for now17:06
smb..17:06
bjf[TOPIC] Blueprints: Review of the Stable Maintenance Process (sconklin / bjf)17:06
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-process-review17:06
MootBotNew Topic:  Blueprints: Review of the Stable Maintenance Process (sconklin / bjf)17:06
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-process-review17:06
bjfWe've successfully wrapped up our first trial of the new stable kernel process. Lucid and Maverick17:06
bjfkernels currently in -proposed are being promoted to -updates today. Everyone involved in the new17:06
bjfprocess have identified areas they will be working to improve for the next cycle. Current thinking17:06
bjfis the next cycle will start with an upload on Dec. 9.17:06
bjf..17:06
=== pleia2_ is now known as pleia2
bjf[TOPIC] Blueprints: Ubuntu Kernel Delta Review (apw)17:07
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-ubuntu-delta-review17:07
MootBotNew Topic:  Blueprints: Ubuntu Kernel Delta Review (apw)17:07
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-ubuntu-delta-review17:07
apwaufs2 updated to official 2.6.37-rcN release from upstream. LIRC patches dropped to clean up the delta. 6 of the 21 personal patch reviews are now done. Some of these are likely to miss the natty-alpha-1 deadline, but none are release critical for the milestone.17:07
apw..17:07
bjf[TOPIC] Blueprints: Kernel Version and Flavours (apw)17:07
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-version-and-flavours17:07
MootBotNew Topic:  Blueprints: Kernel Version and Flavours (apw)17:07
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-version-and-flavours17:07
apwDiscussions are ongoing as to the kernels to use for omap3, this centres around whether the Linaro kernel is fully featured enough and what levels of support we are able to provide for it.  Discussions continue but we are currently waiting on testing of the Linaro kernel against the current userspace.  This will not become critical until natty-alpha-2.17:08
apw..17:08
bjf[TOPIC] Status: Natty (apw)17:08
MootBotNew Topic:  Status: Natty (apw)17:08
apwThe distro kernels are now rebased onto v2.6.37-rc3 and uploaded.  This latest kernel includes a further update to aufs bringing it in line with upstream.  It also carries the bulk of the configuration changes identified at UDS, harmonising a number of options; where those options are there to fix FTBS those are now documented.  It also carries a preview of the latest version of the "200 line" miracle automatic scheduler group patch, any feedback on t17:08
apwhis kernel appreciated.  Testing generally remains good.17:08
apw..17:08
bjf[TOPIC] Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf)17:09
MootBotNew Topic:  Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf)17:09
bjf||                         || Upd./Sec.     || Proposed      || TiP || Verified    ||17:09
bjf|| Dapper: Kernel          || 2.6.15-55.89  ||               ||     ||             ||17:09
bjf|| Hardy:  Kernel          || 2.6.24-28.80  ||               ||     ||             ||17:09
bjf|| =       LRM             || 2.6.24.18-28.7||               ||     ||             ||17:09
bjf|| Karmic: Kernel          || 2.6.31-22.68  ||               ||     ||             ||17:09
bjf|| =       mvl-dove        || 2.6.31-214.30 || 2.6.31-214.32 ||     ||             ||17:09
bjf|| =       ec2             || 2.6.31-307.21 ||               ||     ||             ||17:09
bjf|| Lucid:  Kernel          || 2.6.32-26.47  ||               ||     ||             ||17:09
bjf|| =       LBM             || 2.6.32-25.24  || 2.6.32-26.25  ||     ||             ||17:09
bjf|| =       mvl-dove        || 2.6.32-209.25 || 2.6.32-211.27 ||     ||             ||17:09
bjf|| =       fsl-imx51       || 2.6.31-608.19 || 2.6.31-608.20 ||     ||             ||17:09
bjf|| =       ec2             || 2.6.32-309.18 ||               ||     ||             ||17:09
bjf|| = lts-backport-maverick || 2.6.35.22.34  ||               ||     ||             ||17:09
bjf|| Maverick: Kernel        || 2.6.35-23.40  ||               ||     ||             ||17:09
bjf|| =       mvl-dove        || 2.6.32-410.27 ||               ||     ||             ||17:09
bjf|| =       ti-omap4        || 2.6.35-903.18 ||               ||     ||             ||17:09
bjf* Lucid and Maverick -proposed kernels promoted to -updates.17:09
bjf* Call for further testing of ec2 and ARM -proposed kernels for Lucid and Maverick.17:09
bjf  I've pinged Tobin Davis for ARM.17:10
bjf..17:10
bjf[TOPIC] Incoming Bugs: Regressions (JFo)17:10
MootBotNew Topic:  Incoming Bugs: Regressions (JFo)17:10
JFoIncoming Bugs17:10
JFo19 Natty Bugs (up 7)17:10
JFo1062 Maverick Bugs (up 37)17:10
JFo1088 Lucid Bugs (up 6)17:10
JFoCurrent regression stats (broken down by release):17:10
JFo==== regression-potential ====17:10
JFoAs this tag is deprecated, this listing is only to ensure that I keep it on my radar until17:10
JFochanges to the apport hooks and my processing of the currently tagged bugs is completed.17:10
JFo  * 3 natty bugs17:10
smbbjf, You should ping me for ec217:10
JFo  * 396 maverick bugs (up 32 since the final maverick meeting)17:10
JFo  * 177 lucid bugs (up 14 since the final maverick meeting)17:10
JFo==== regression-update ====17:10
JFo  * 20 maverick bugs (no change)17:10
JFo  * 78 lucid bugs (up 1)17:10
JFo  * 6 karmic bugs (no change)17:10
JFo  * 0 hardy bugs (no change)17:10
JFo==== regression-release ====17:10
JFo  * 156 maverick bugs (up 9)17:10
JFo  * 192 lucid bugs (down 1)17:10
JFo  * 40 karmic bugs (no change)17:10
JFo  * 2 hardy bugs (no change)17:10
JFo==== regression-proposed ====17:10
JFo  * 13 maverick bugs (no change)17:11
JFo  * 6 lucid bugs (down 1)17:11
JFo  * 1 karmic bug (no change)17:11
JFo..17:11
bjf[TOPIC] Incoming Bugs: Bug day report (JFo)17:11
MootBotNew Topic:  Incoming Bugs: Bug day report (JFo)17:11
JFoToday is the Bug Day. It is focusing on Bugs with patches so that I can focus17:11
JFoon getting the particular process I must use to address these bugs organized.17:11
JFoI will likely be pinging several of you with questions over the next week as17:11
JFoI work to finalize these steps and get them documented.17:11
JFoThe next bug day will on December 7th. I will define the scope of that bug day in my e-mail17:11
JFoto the list so that I can take some time to determine what the best use of that17:11
JFoday will be.17:11
JFo..17:11
bjf[TOPIC] Triage Status (JFo)17:12
MootBotNew Topic:  Triage Status (JFo)17:12
JFoSpoke this week with Tapas Mishra who is interested in helping out. We had a great conversation on where to start. This conversation had been preceeded by someone providing several key links to wiki documentation that provided a first step toward Tapas' desire to work on wireless issues. My recommendation was to look at current wireless bugs that have been filed and use those issues to gain an understanding of the type of issues we see with wirele17:12
JFoss drivers. Unforunately, due to the modular, and sometimes closed corporate nature of wireless drivers, we don't have a way to help someone who is interested in beginning coding on wireless drivers, but I am hopeful that the information I was able to provide and the recommendations smb and I made will be helpful.17:12
JFo..17:12
bjf[TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/)17:13
MootBotNew Topic:  Open Discussion or Questions: Raise your hand to be recognized (o/)17:13
smb\o17:13
apwo/17:13
bjfsmb, go17:13
smbJust a question how comfortable those with upload rights are with the patch piloting17:13
smbAnd whether they would know what to do.17:13
smb..17:13
* apw has no clue17:14
apwthere are some links in the original email which are intended to help one17:14
smbhttp://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews17:14
MootBotLINK received:  http://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews17:14
apwknow what the heck to do.  probabally its going to be a shambles17:14
apw:)17:14
apw..17:14
smbOk, so as much knowledge there as I have17:15
smb..17:15
=== oubiwann is now known as oubiwann-away
bjfapw, go17:15
apwjust a heads up that alpha1 is coming up.  get your changes in17:16
apw..17:16
bjfif there is nothing else ...17:16
bjfthanks everyone17:17
bjf#endmeeting17:17
MootBotMeeting finished at 11:17.17:17
ckingthanks bjf17:17
jjohansenthanks bjf17:17
smbthanks bjf17:17
hggdhsorry, was on an appointment17:17
JFothanks bjf17:17
=== oubiwann-away is now known as oubiwann
=== maxb_ is now known as maxb
=== bazhang_ is now known as bazhang

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!