[10:01]  * persia peers about
[10:01]  * Hobbsee throws rotten tomatoes at persia
[10:01] <Hobbsee> GOTCHA!
[10:02]  * persia applies the handy uncursed towel (P)
[10:03] <Hobbsee> er, what are you actually peering about for?
[10:04] <persia> There was a rumor that the AsiaOceania RMB might meet now, when there might be quorum about.  Given the lack of others, I'm guessing the rumour was unfounded.
[10:04] <persia> As a result, I expect the meeting will be held later, and don't know if we'll get quorum, as it will be late in Australia.
[10:07] <MaWaLe> persia: the meeting is planned fot the 15UTC (on the wiki page)
[10:08] <persia> MaWaLe, Indeed, that's what the wiki page says.  As I said, it was an apparently unfounded rumour.  So, 5 hours from now, I'll peer about again :)
[10:09] <MaWaLe> hope that it'll be a quorum this time
[10:59] <Technoviking> morning all
[10:59] <dholbach> hello
[11:00] <dholbach> mdke and Burgundavia are not around and I guess mako is not up yet
[11:01] <dholbach> #startmeeting
[11:01] <MootBot> Meeting started at 06:01. The chair is dholbach.
[11:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[11:02] <dholbach> it seems we have one agenda item today: https://wiki.ubuntu.com/CommunityCouncilAgenda
[11:02] <dholbach> [TOPIC] Forums Council Re-Elections and New Members
[11:02] <MootBot> New Topic:  Forums Council Re-Elections and New Members
[11:02]  * dholbach needs a minute or two to get on top of the discussion :)
[11:04] <sabdfl> arrgh, south african bandwidth
[11:05] <ubuntugeek> :)
[11:05] <dholbach> so https://wiki.ubuntu.com/CommunityCouncil/Delegation only applies partly, there's no real "team" connected to the "Forums Community"
[11:05] <Technoviking> sabdfl: lagging here too, never heard of St. Patick day lag before:)
[11:06] <sabdfl> usually, post-St Patrick's day lag :-)
[11:07] <jussi01> *g*
[11:07] <sabdfl> dholbach: i thought we agreed to create such a team?
[11:08] <dholbach> sabdfl: there's https://launchpad.net/~forum-council/+members but there's no "members through Forum's participation" - I think I recall us saying that we revisit the decision in a few months of time again
[11:08] <dholbach> sabdfl: IIRC the IRC and the Forums community did not like the idea much
[11:08] <dholbach> Technoviking would know better than I do :)
[11:09] <sabdfl> right
[11:09] <sabdfl> i keep thinking we agreed it, because it's what i wanted, but that's not always true :-)
[11:09]  * dholbach hugs sabdfl :)
[11:10] <Technoviking> are you talk about a team for all forums members?
[11:10] <dholbach> Technoviking: ubuntumembers through forums activity
[11:10] <dholbach> so in the absence of such a team right now, it'd make sense for all CC members to review the nominations and cast a vote
[11:11] <persia> Could perhaps the polity be all ubuntumembers?  Those inactive in the forums would likely abstain.
[11:11] <sabdfl1> i.e., a team of folks who have made significant and sustained contributions to Ubuntu  *in the forums*
[11:12] <nhandler> persia: That vote wouldn't be able to take place via IRC it would need to be on LP
[11:12] <sabdfl1> i don't think there's a *requirement* for voting on LP
[11:12] <sabdfl1> if there's an agreed, fair and safe voting mechanism in the forums, or the IRC world, communities can use that
[11:13] <sabdfl1> for votes inside that domain, where people are comfortable with those tools
[11:13] <nhandler> sabdfl: But if we allow all ubuntumembers to vote, it would be difficult to do it on irc (especially to enforce that only members vote)
[11:13] <persia> And the polity needn't necessarily even vote, as long as the right polity is identified/
[11:13] <sabdfl1> it's cross-team things that usually need LP
[11:14] <sabdfl> sorry, with all the dropping off and reconnecting, i fear i'm not keeping up with the conversation
[11:14] <nhandler> You didn't miss anything sabdfl
[11:16] <dholbach> for now I think we should decouple the ubuntumembers-through-forums-activity from the new FC members discussion
[11:17] <elmo> I agree
[11:19] <Technoviking> I guess first thing is, is the CC ok with the Forums Council expanding to 7 members?
[11:20] <elmo> I am
[11:21] <dholbach> me too, it is a big responsibility and the FC will definitely benefit from more trusted Forums leader to be on board
[11:22] <dholbach> sabdfl?
[11:23] <Technoviking> must have dropped again
[11:26] <dholbach> if we don't come to a conclusion in this meeting I'd suggest starting a new thread with all the voting options to the CC and set a cut-off date in 1-2 weeks so everybody has enough time to send in their vote
[11:26] <dholbach> the FC election organisation thread got fairly long already and maybe it wasn't sufficiently clear what was expected of each member
[11:26] <Technoviking> dholbach: sounds good
[11:27] <dholbach> elmo, sabdfl: does that sound fair to you?
[11:27] <elmo> dholbach: sounds good to me
[11:27] <Technoviking> I will prepare it
[11:27] <dholbach> thanks a lot Technoviking
[11:28] <dholbach> [TOPIC] Any other business?
[11:28] <MootBot> New Topic:  Any other business?
[11:29] <persia> I'd just like to thank the CC for continuing the meeting schedule reliably over the past many months, regardless of DST changes, inconveniences of personal schedules, or other matters.
[11:29] <dholbach> thanks persia, I'd like to give credit to Claire Newman who reminded me of the meeting dates when I did not think of them. :-)
[11:30] <dholbach> ok seems we have no other business - thanks everybody
[11:30] <dholbach> #endmeeting
[11:30] <MootBot> Meeting finished at 06:30.
[11:30]  * dholbach will update the Team Report
[11:31] <Technoviking> thanks dholbach
[11:31] <dholbach> Technoviking: thank YOU
[11:41] <sabdfl> argh. ftr, +1
[11:41] <sabdfl> dholbach: ^ sorry for the lag
[11:42] <dholbach> sabdfl: no worries - I think it's good if we get all votes of the CC for such an important decision
[11:42] <sabdfl> me too
[14:54]  * persia peers about
[14:56]  * MaWaLe hoping that there'll be a quorum
[14:56] <aamachu> hi
[14:56] <hito_jp> hi
[14:56] <Belutz> amachu, sorry for my long absence
[14:56] <MaWaLe> hi amachu
[14:56] <persia> hey Belutz
[14:57] <Belutz> hi persia
[14:57] <Belutz> persia, how things going?
[14:57] <persia> Alright.  For you?
[14:57] <Belutz> I'm alright too, thanks :)
[14:57] <Belutz> just a lot of work to do
[14:58] <Belutz> and i'm still in the office at 10pm now :D
[14:59] <nijaba> @paris
[14:59] <sommer> hey all
[14:59] <persia> nijaba, The bot can't process the google calendar, and so doesn't track the schedule.  Checkhttp://fridge.ubuntu.com/calendar
[14:59] <persia> Server Team meeting is at 16:00 UTC, which is in an hour
[14:59] <nijaba> oki, ta persia
[14:59] <aamachu> Belutz: you there :-)
[14:59] <aamachu> great the time change worked?
[15:00] <Belutz> amachu, i'm here :D
[15:00] <aamachu> persia: yes.
[15:00] <aamachu> so let me check for one more person
[15:00] <aamachu> elky: Hey are you there?
[15:00] <Belutz> amachu, maybe it's not working for our friend in australia
[15:01] <Belutz> it's probably 2am in there
[15:01] <aamachu> lifeless: ?
[15:01] <aamachu> Belutz: Yes. persia had commented with his concerns on that
[15:02] <b0i_kut3^^> hello
[15:02] <aamachu> Belutz: got to know about zakame?
[15:02] <Belutz> amachu, no i'm not
[15:03] <aamachu> persia: we still need one.
[15:03] <persia> aamachu, Indeed.  If zakame doesn't join us, I think we won't reach quorum.
[15:04] <mathiaz> Hello all - for those attending the Ubuntu Server Team we'll move to #ubuntu-server
[15:04] <nealmcb> hmmm - the fridge says 16:00 UTC for server team meeting, but Mathias said we'd changed to 15:00
[15:04] <khanh_coltech> can i become Ubuntu member?
[15:04] <persia> nealmcb, It seems to be related to some confusion based on some governments insistence that there should be changes to the hours on clocks.
[15:05] <nealmcb> indeed....
[15:05] <persia> khanh_coltech, Possibly.  If we can get one more of our board members to arrive in the next 10 minutes or so, we'll process the applications in the order they appear on the wiki page.
[15:06] <persia> khanh_coltech, If not, we'll try to reschedule the next meeting to assure a sufficient number of people will be present, and review them then.
[15:06] <khanh_coltech> persia: thanks, i will wait :)
[15:07] <hito_jp> khanh_coltech: please fix your wikipages link, I think that it needs "s/k/K/'.
[15:08] <aamachu> persia: while we wait lets decide on concerns you had raised on your comments while editing the wiki page
[15:09] <khanh_coltech> hito_jp: ok, it fixed
[15:09] <aamachu> yes. I too agree 2 AM is difficult for Aussies
[15:09] <persia> I'm just not convinced we can reach quorum at 15:00, and think we oughtn't schedule any meetings then until we are assured of quorum, as it's unfair to those who attend.
[15:09] <aamachu> persia: yes. And it getting repeated for quite a number of time
[15:10] <aamachu> and themuso ?
[15:10] <persia> is in Australia
[15:11] <PmDematagoda> persia: has the meeting been held before?
[15:11] <Belutz> aamachu, actually, the previous time is fine with me, but sometimes works in the way
[15:11] <persia> PmDematagoda, Several times, but we have yet to reach quorum this evening.
[15:11] <PmDematagoda> persia: Ive been having trouble attending any meeting all this time, most of the time I was caught up in something, my apologies for that
[15:11] <aamachu> Belutz: you mean the 11.00 UTC or 9.00 UTC?
[15:12] <Belutz> too many different time zones for asia & oceania :D
[15:12] <Belutz> aamachu, both, but at both time i will be still at the office
[15:12] <persia> Belutz, Can you meet from the office?
[15:12] <aamachu> its office time here in India too..
[15:13] <Belutz> persia, yes, if there's no meeting :)
[15:13] <aamachu> but I can manage
[15:13] <persia> To avoid colliding with the CC, let's do 10:00
[15:13] <aamachu> persia: you mean to say consistently for all four weeks?
[15:14] <Belutz> and because sometimes i travel out of town, it's sometimes hard for me to get a connection
[15:14] <aamachu> on tuesdays?
[15:14] <persia> aamachu, Or even just every other week.  We didn't do so well with every week, but I think we'd do better with every other week.
[15:14] <persia> I do like Tuesdays.
[15:15] <aamachu> persia: as long as we could meet it I am Ok. So the first and the third or the second and the fourth?
[15:15] <aamachu> Belutz: what do you say?
[15:16] <persia> second and fourth is better for me, but only marginally.
[15:16] <Belutz> aamachu, ok, let's try that
[15:17] <MaWaLe> so there will not be a meeting today?
[15:17] <Belutz> aamachu, could you please set up a google calendar, so I could subscribe to the meeting schedule and get sms notification for that? :D
[15:17] <persia> MaWaLe, We haven't reached quorum, and we're 15 minutes in, so likely no.
[15:17] <persia> aamachu, Just be sure to invite the fridge when you do :)
[15:18]  * MaWaLe is so sad
[15:18] <aamachu> yes
[15:18] <aamachu> Belutz: and for you?
[15:19] <Belutz> yes, it's ok with me
[15:19] <MaWaLe> can i ask a question please
[15:19] <Belutz> i hope the candidate won't be to dissapointed :)
[15:19] <aamachu> persia: : I do update fridge these days
[15:19] <persia> MaWaLe, Go ahead.
[15:19] <aamachu> MaWaLe: has been waiting for so long :-)
[15:19] <MaWaLe> how do you (RBM) calculate the needed quorum?
[15:20] <persia> The RMB is 7 members, so it requires at least 4 to make a binding decision.
[15:20] <aamachu> MaWaLe: We are seven on the board - > 50% is four
[15:20] <MaWaLe> i think that waiting was a good experience for me to have more activities and knowing more people (like amachu and persia)
[15:20] <MaWaLe> but now it's taking to much to wait all this time
[15:21] <aamachu> MaWaLe: I suggest you also apply to other Boards
[15:21] <aamachu> yes I agree its taking long here
[15:21] <MaWaLe> amachu: but like mentioned on the edward's rule : for the next and the third time when there's no quorum for an official meeting, the quorum needed is no more 50%
[15:21] <aamachu> but without quorum we can't proceed. Hope you understand
[15:22] <MaWaLe> amachu: actually i didn't have an internet connection at home so i can't attend to toher RB
[15:22] <MaWaLe> this one fit perfectly with mu job time
[15:22] <MaWaLe> i understand perfectly
[15:23] <aamachu> MaWaLe: Thanks for that.
[15:23] <MaWaLe> thanks for all of you
[15:23] <MaWaLe> it was a pleasure and thank you for the reply amachu
[15:25] <aamachu> The fourth Tuesday comes next week, and I will schedule the meeting at 10.00 UTC
[15:25] <aamachu> will that be fine persia, Belutz?
[15:25] <persia> Good for me.  Please also send out an announcement to our Australian colleagues, so that we have a good chance of quorum.
[15:25] <Belutz> fine with me
[15:25] <aamachu> persia: yes.
[15:26] <persia> Excellent then.  Good night.
[15:26] <MaWaLe> good night
[15:26] <aamachu> fine. lets wind up for the day.
[15:26] <aamachu> persia: Belutz: look out for your nominations for Board Member
[15:26] <aamachu> :-)
[15:27] <aamachu> Thank you everyone for participating
[15:27] <Belutz> aamachu, thanks :)
[15:27] <MaWaLe> thanks
[15:27] <Belutz> persia, thanks :)
[15:27] <Belutz> for all candidates, thanks for your understanding :)
[15:27] <zaafouri> =)
[15:28] <MaWaLe> Belutz: I'm a regularI'm a regular now :p
[15:28] <Belutz> :D
[15:29] <MaWaLe> Belutz: can i speak to you in private please
[15:30] <Belutz> MaWaLe, feel free to pm me :)
[15:30] <MaWaLe> thx
[16:58]  * manjo waves
[16:59] <cooloney> cooloney, waves
[16:59]  * smb_tp waves back
[17:00]  * amitk waves
[17:00] <pgraner> Its about time for the Weekly Kernel Team IRC meeting
[17:00] <pgraner> #startmeeting
[17:00] <MootBot> Meeting started at 12:00. The chair is pgraner.
[17:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:00]  * apw hovers at the edge of your vision
[17:01] <pgraner> [TOPIC] Open Items from last week
[17:01] <MootBot> New Topic:  Open Items from last week
[17:01] <Riddell> ** Kubuntu meeting in #kubuntu-devel incase anyone is in here for it
[17:01] <pgraner> * sconklin, bring up archiving of Hardy/Intrepid OEM LPIA trees after the sprint
[17:02]  * smb_tp remembers he still has to add some calendar entries
[17:02] <pgraner> * sconklin, coordinate testing by the OEM team for Hardy and Jaunty lpia
[17:02] <rtg> pgraner: sconklin is out today
[17:02] <pgraner> rtg: Understand, just for completeness.
[17:03] <pgraner> awe: the OEM team testing and news?
[17:03]  * pgraner look at awe
[17:03] <awe> no news...working on testing this week
[17:03] <pgraner> awe: thanks can you send an email to kernel-team letting us know how it goes?
[17:04] <awe> i'm bringing the hpmini up to the latest abi / oem-kernel first
[17:04] <awe> will send an email when i've finished testing
[17:04] <pgraner> [ACTION] awe to report back to kernel-team on LPIA testing status
[17:04] <MootBot> ACTION received:  awe to report back to kernel-team on LPIA testing status
[17:04] <pgraner> * ogasawara, handle another call for testing for A6
[17:04] <cking> awe: so no pushing new commits then?
[17:04] <ogasawara> pgraner: sent email, although I'm concerned about the fact that Beta should have users testing via check box but that wasn't available for the A6 cft
[17:04] <apw> yes the upload i expected to occur tue last week did not occur
[17:05] <pgraner> ogasawara: yea, I found out about that yesterday, rtg is pushing the package, so we should send out a revised CFT
[17:05] <apw> seems it needed some FF exception and so it being requested now
[17:05] <rtg> rt will puch the package as soon as apw delivers it
[17:05] <pgraner> ogasawara: once the checkbox pkgs is uploaded
[17:05] <awe> cking: correct
[17:05] <ogasawara> pgraner: ok good.  I'll send another pre-beta cft when it's ready.
[17:06] <pgraner> apw: can you let ogasawara know when to fire the CFT out since you working it behind the scenes?
[17:06] <apw> yep
[17:06] <pgraner> [ACTION] apw to inform ogasawara when revised CFT can go out
[17:06] <MootBot> ACTION received:  apw to inform ogasawara when revised CFT can go out
[17:06] <pgraner> * apw and smb, look through the bugs ogasawara mentioned .... hows it going?
[17:06] <apw> ack
[17:07] <smb_tp> We have one which is a bit tricky (the crash)
[17:07] <smb_tp> One is fixed by now
[17:07] <smb_tp> And one could go to manjo (he just isn't aware of it yet)
[17:08] <manjo> smb_tp, send it my way
[17:08] <smb_tp> ack
[17:08] <ogasawara> pgraner: from my end they look to be getting the proper attention
[17:08] <smb_tp> manjo, Its another Dell server hardware issue on Hardy
[17:08] <manjo> ok
[17:09] <pgraner> [ACTION] smb to send manjo bug on Dell server hw issue on Hardy
[17:09] <MootBot> ACTION received:  smb to send manjo bug on Dell server hw issue on Hardy
[17:09] <manjo> is that the hibernate problem ?
[17:09] <pgraner> ogasawara: thanks for the update
[17:09] <smb_tp> manjo, No some sort of sata3 disk
[17:09] <manjo> k
[17:09] <pgraner> * apw, confirm the ack requirements for jaunty...  not sure what this one is about
[17:10] <apw> that one was done, in the last meeting and can be closed
[17:10] <pgraner> apw: nice
[17:10]  * pgraner likes closed actions
[17:10] <apw> just confirming we need one ACK for commit to Jaunty currently
[17:10] <pgraner> [TOPIC] Security & bugfix kernels - Hardy - Intrepid
[17:10] <MootBot> New Topic:  Security & bugfix kernels - Hardy - Intrepid
[17:10]  * rtg has been slacking on that a bit
[17:10] <smb_tp> Hardy: Upload planned for tomorrow including
[17:10] <smb_tp> • rt: Updated PREEMPT_RT support to rt27
[17:10] <smb_tp> • fix apparmor memory leak on deleted file ops
[17:10] <smb_tp> • KVM: MMU: Add locking around kvm_mmu_slot_remove_write_access()
[17:10] <smb_tp> • serial: 8250: fix shared interrupts issues with SMP and RT kernels
[17:10] <smb_tp> • 8250.c: port.lock is irq-safe
[17:11] <smb_tp> • ACPI: Clear WAK_STS on resume
[17:11] <smb_tp> Intrepid: Upload has been done, linux-meta needs to get through
[17:11] <smb_tp> CVE updates are currently being triaged and processed
[17:11] <smb_tp> Thats basically it
[17:11]  * pgraner is impressed with smb_tp cut n paste ability :-)
[17:11] <smb_tp> :-P
[17:11] <pgraner> [TOPIC] Jaunty Status
[17:11] <MootBot> New Topic:  Jaunty Status
[17:11] <pgraner> rtg: how we a lookin'?
[17:12] <rtg> an ABI bumper is coming today.
[17:12] <rtg> it contains ATI r6/r7 bits
[17:12] <rtg> 2.6.28.8
[17:12] <rtg> and some other stuff
[17:12] <rtg> oh, and built in EHCI/UHCI/OHCI
[17:12] <IntuitiveNipple> ha!
[17:13] <amitk> rtg: OHCI too?
[17:13] <rtg> I think its looking pretty good. no serious problems that I know of.
[17:13] <pgraner> rtg: any expected fall out from EHCI and friends?
[17:13] <rtg> actually, it ought to clear up some issues with USB transfer speeds.
[17:13] <IntuitiveNipple> As long as the link order is correct :)
[17:13] <rtg> essentially, its the same solution in the kernel that folks have employed in initramfs
[17:14] <IntuitiveNipple> That one will solve a lot of USB speed complaints
[17:14] <rtg> I think the biggest issues with Jaunty are ARM related at this point
[17:14]  * cking is encouraged by this 
[17:14] <amitk> how widely is OHCI used?
[17:14] <pgraner> rtg: will hit arm in a few min
[17:14] <rtg> AA and aufs do play well together
[17:15] <rtg> don't
[17:15] <rtg> ok, full stop
[17:15] <pgraner> Jaunty Alpha 6 ... ogasawara how does it look from your standpoint?
[17:16] <pgraner> will come back to that...
[17:16] <ogasawara> pgraner: looking good here, but seem to be getting more suspend resume bugs
[17:16] <pgraner> ah
[17:16] <pgraner> ogasawara: what type? hangs?
[17:17] <apw> i get the feeling suspend/resume has not been that great ever and we are now
[17:17] <apw> seeing the badness via the incoming bug stream as people switch over
[17:17] <ogasawara> pgraner: the ususal, failure to resume.  and I think the increased bug reporting is because of the apport hooks
[17:17] <apw> to jaunty.
[17:18] <IntuitiveNipple> From my experience the suspend/resume code in many drivers was an after-thought to catch up with the API
[17:18] <pgraner> ogasawara: any way to tell if they are false positive? For example I have shut the lid (with it set to suspend) and then opened it immediately and I get the apport notification... anything like that?
[17:18] <rtg> IntuitiveNipple: I think most drivers have caught up wrt to suspend.
[17:18] <ogasawara> pgraner: I do see what seem to be false positives coming in too.  I've tried to tag them "false-report" so we can investigate.
[17:19] <pgraner> ogasawara: great...
[17:19] <apw> ogasawara, yeah i have a couple of thoughts on that one
[17:19] <IntuitiveNipple> We have a few false positives based on the TEST_SUSPEND_SECONDS = 5 and I'm investigating what would be a sesnsible higher value to set that based on a collection of kern.log reports ogasawara collected from launchpad
[17:19] <apw> if they are false we can start dup'ing them onto matt's original false one
[17:19] <IntuitiveNipple> It looks like increasing it to 9 or 10 would solve alot of those false positives
[17:20] <ogasawara> apw: sounds good
[17:20] <pgraner> Well that lead us into the Suspend/Resume topic... which we just covered
[17:20] <pgraner> [TOPIC] ARM
[17:20] <MootBot> New Topic:  ARM
[17:21] <pgraner> amitk: what say you?
[17:21] <amitk> as rtg mentioned aufs and apparmor don't like each other
[17:21] <bradF> the AA and aufs issue that rtg was referring to ... https://bugs.launchpad.net/ubuntu/+source/linux/+bug/344370
[17:21] <amitk> or rather AA doesn't like imx51
[17:22] <amitk> bradF is looking at the problem
[17:22] <pgraner> amitk: ok, any other show stoppers out there for ARM?
[17:22] <rtg> I'm concerned that the problem is something systemic.
[17:22] <amitk> I am working on finalising the imx51 configs for mobile team
[17:23] <pgraner> amitk: thanks
[17:23] <amitk> pgraner: we have dying ttys on the babbage boards. That seems to be the major showstopper right now
[17:23] <pgraner> amitk: I guess that keeps the end user experience short huh?
[17:23] <apw> physical or virtual dying?
[17:24] <pgraner> amitk: any theories on why/how etc...?
[17:24] <amitk> pgraner: yeah, a bit
[17:24] <amitk> compiling in AA causes problems, w/o it things are somewhat better
[17:24] <cking> just somewhat?
[17:25] <pgraner> amitk: have we reached out to upstream to see what they think?
[17:25] <amitk> cking: we don't know the next problem we'll encounter after that :)
[17:25] <amitk> pgraner: I've talked to John Johansen
[17:25] <rtg> pgraner: or the Freescale dudes?
[17:25] <amitk> he seemed to think it shouldn't happen
[17:26] <pgraner> amitk: let me know if you need to talk to Freescale and I'll get some one on the line for you.
[17:26] <amitk> honestly, given our time constraints, we don't have the experience to track down the AA issue
[17:26] <rtg> John's explanation made it sound like it could be a fundamental problem.
[17:26] <amitk> so I am trying to bypass it for now
[17:26] <amitk> pgraner: thanks
[17:27] <pgraner> amitk: ok, sounds like a solid plan forward for now
[17:27] <pgraner> Since sconklin is not here we'll skip the lpia for this week, if there are no objections....
[17:28]  * rtg has no objections
[17:28] <cking> nope
[17:28] <pgraner> [TOPIC] Incoming Bugs
[17:28] <MootBot> New Topic:  Incoming Bugs
[17:28] <pgraner> ogasawara: your time to shine :-)
[17:28] <ogasawara> pgraner:  I only have 2 to bring up and both seem to be getting looked at
[17:28] <ogasawara> bug 343556 - regression-potential but apw looks to be investigating
[17:28] <ogasawara> bug 212485 - hardy SRU that smb_tp looks to already be taking care of
[17:29] <pgraner> ogasawara: thanks... looks in order
[17:29] <pgraner> [TOPIC] Open Discussion
[17:29] <MootBot> New Topic:  Open Discussion
[17:29] <pgraner> Floor is open...
[17:30] <manjo> is ext4 going to be a default in jaunty ?
[17:30] <pgraner> manjo: no
[17:30] <pgraner> manjo: purely optional
[17:30] <manjo> current option is the chose manual partition to get ext4...
[17:30] <pgraner> manjo: as planned
[17:30] <manjo> k
[17:30] <pgraner> Any idea when we will see 2.6.29 go final?
[17:31] <rtg> we're seeing some complaints about ext4
[17:31] <cking> just some?
[17:31] <rtg> 175 on one report at last count :)
[17:31] <cooloney> rtg, right, ext4 lost data ?
[17:31] <manjo> in my testing ext4 has major issues
[17:31] <amitk> pgraner: its already -rc8, so soon
[17:31] <rtg> the next upload has some patches that change some behaviors to be closer to ext3
[17:32] <apw> rtg is that the patch kit to expedite the open modify rename stuff
[17:32] <rtg> I did so at apw's suggestion
[17:32] <rtg> ^^
[17:32] <cking> kde users will be happy
[17:32] <pgraner> ogasawara: should we highlight the new ext4 patches and ask for some out of band testing for the willing?
[17:32] <rtg> the truncated files will be happier too :)
[17:33] <Riddell> we will?
[17:33] <ogasawara> pgraner: sure, wouldn't hurt.
[17:33] <pgraner> ogasawara: can you arrange?
[17:33] <ogasawara> pgraner: yup
[17:33] <pgraner> [ACTION] ogasawara to issue CFT around ext4 data loss patches
[17:33] <MootBot> ACTION received:  ogasawara to issue CFT around ext4 data loss patches
[17:34] <cjwatson> manjo: (also you can boot with partman/default_filesystem=ext4 on the kernel command line, if that makes things more convenient for you while testing)
[17:34] <pgraner> Riddell: yea, ext4 eats kde dot files and leave them zero length
[17:34] <cooloney> pgraner, sorry, CFT = ?
[17:34] <rtg> call for testing
[17:34] <Tonio_> hi (sorry was locked in a meeting here...)
[17:34] <cooloney> OK
[17:34] <Riddell> Tonio_: kubuntu meeting in #k-d
[17:34] <manjo> cjwatson, thanks that works lot better
[17:35] <pgraner> Anyone have other items... going once... twice
[17:35]  * rtg flees to another meeting
[17:35] <pgraner> [TOPIC] Next Meeting
[17:35] <MootBot> New Topic:  Next Meeting
[17:35] <pgraner> Same time and channel
[17:35] <apw> ack
[17:35] <smb_tp> ack
[17:35] <cking> ..different reality
[17:35] <cking> ack
[17:36] <lieb_> ack
[17:36] <cooloney> ok
[17:36] <manjo> k
[17:36] <pgraner> Thanks everyone! Appreciate it!
[17:36] <amitk> thanks
[17:36] <pgraner> #endmeeting
[17:36] <MootBot> Meeting finished at 12:36.
[17:36] <cooloney> thanks
[17:36]  * smb_tp shuffles away
[22:29] <juliux> @schedule berlin
[23:02] <nhandler> juliux: FYI, ubottu no longer manages the schedule. Look at the gcal
[23:59] <Laney> nhandler: Have you time for a couple of FFes?