[00:10] <mdeonte> !startmeeting
[00:10] <mdeonte> .startmeeting
[00:11] <persia> It's with a #
[07:05] <dholbach> porthose, randomaction: you guys around?
[07:05] <randomaction> yes
[07:05] <dholbach> right now we have a bit of a quorum problem... persia and nixternal are there, but we need one MC member more :)
[07:06] <nixternal> MC Hammer!
[07:06] <dholbach> but I'm sure we'll manage to get there in a bit
[07:07] <dholbach> nixternal: I'm sure you still have one of those very baggy, pink pants from the 90s? :)
[07:07]  * dholbach is going to text soren
[07:07] <nixternal> ping no, a light colored red yes
[07:07] <nixternal> pink, not ping
[07:07]  * porthose waves :)
[07:22]  * persia dithers harder
[08:03]  * soren wanders in
[08:04] <nixternal> hola
[08:04] <nixternal> right as dholbach went to walk his dog
[08:04] <persia> The timing is truly unfortunate
[08:07]  * porthose yawns and tries not to fall asleep on his key board
[08:07] <persia> porthose: If you're that tired, you might want to try another time.  I'm not convinced we'll have quorum soon, or even at all.
[08:08] <persia> Some people are not yet around, and some people are falling asleep.
[08:08] <nixternal> porthose: you and I both
[08:08] <porthose> persia, I can hang for a while longer :)
[08:09] <nixternal> 02:10 herezzzZZZZzzZzZzzZz
[08:10] <porthose> nixternal, same for me ;)
[08:17]  * soren chuckles
[08:18] <soren> I just realised dholbach created my calendar entry for this meeting. :)
[08:18] <soren> dholbach: What's your secret trick to knowing the right time in spite of Google Calendar? :)
[08:36] <dholbach> back
[08:36] <dholbach> soren: I did that ages ago
[08:42] <soren> dholbach: What? Added that calendar entry?
[08:42] <nixternal> go go go
[08:42] <nixternal> porthose and I are falling asleep
[08:42] <nixternal> not together though
[08:43] <dholbach> soren: yep
[08:43] <porthose> nixternal, haha :)
[08:44] <soren> dholbach: Can you move it, please? That'll give me a better chance of being on time. :)
[08:44] <dholbach> done
[08:45] <dholbach> so we're one member short again.. I'd propose to have the meeting now and ask questions and do the vote via mail... does that sound alright to you?
[08:45] <porthose> dholbach, yes
[08:46] <dholbach> nixternal, soren?
[08:46] <nixternal> +1
[08:46] <dholbach> maybe we're lucky and jpds or geser turn up :)
[08:46] <nixternal> persia might turn back up as well
[08:46] <nixternal> seeing as your dog walk lasted more than 20 minutes :p
[08:47] <dholbach> #startmeeting
[08:47] <MootBot> Meeting started at 02:47. The chair is dholbach.
[08:47] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[08:47] <dholbach> [LINK] Agenda: https://wiki.ubuntu.com/MOTU/Council/Meeting
[08:47] <MootBot> LINK received:  Agenda: https://wiki.ubuntu.com/MOTU/Council/Meeting
[08:47] <dholbach> [TOPIC] Charlie Smotherman's MOTU application
[08:47] <MootBot> New Topic:  Charlie Smotherman's MOTU application
[08:47] <dholbach> hey porthose... how are you doing? what time is it over there?
[08:48] <porthose> a little tired but other wise ok 0248hrs :)
[08:48] <dholbach> wow... that's dedication
[08:48]  * dholbach has no more questions ;-)
[08:48] <porthose> :)
[08:49] <dholbach> porthose: so what are your plans once you're MOTU, anything specific for lucid and lucid+1?
[08:49] <nixternal> that would have been my only question for porthose seeing as we have questioned him who knows how many times in the past already :)
[08:50] <porthose> The major thing I have planned is to get more involved in the mentoring program
[08:50] <porthose> as a mentor that is :)
[08:50] <dholbach> porthose: we had a couple of discussions about that before... how do you think people best spend their time as a mentor?
[08:51] <nixternal> we have quorum now dholbach
[08:51] <persia> I have a new question :)  porthose: You say that the only thing you dislike is Ubuntu developers who do not submit their patches to Debian.  What sort of strategies might we employ to reduce the effort required to determine if a given patch is appropriate for Debian, or do you think we should expect the Debian Developers to make the decisions?
[08:52] <porthose> dholbach, I would say insuring that prospective developers have a good knowledge of the basic processes
[08:52]  * nixternal remembers this discussion previously
[08:53] <porthose> persia, to answer your question is to make sure that while mentoring prospective developers patches that should be sent upstream are sent upstream
[08:53] <nixternal> now I have a question to follow up on persia just to make sure I am not mixing this up, but didn't you list that same problem when you did universe-contributor, and your numerous per package rights applications?
[08:53] <porthose> nixternal, yes
[08:54] <dholbach> porthose: and what kind of activities do you suggest? there's already a lot of patch review and sponsoring going on, what else should a mentor do (that the general developer community can't)?
[08:54] <nixternal> ok, thought so, as I asked a similar question to persia's before
[08:54] <nixternal> see persia, my brain isn't that bad afterall :p
[08:54] <persia> nixternal: very similar :)
[08:54] <nixternal> and i have one closed
[08:56] <porthose> mentors IMHO develop a personal one on one relationship with the mentee, thus creating trust
[08:57] <persia> porthose: Where I'm curious is about the decision process for determining if a given patch belongs in Debian.  Clearly you're (still) not happy with the nature of the decisions taken in general, and so I wonder what we can do to make you happy with the decisions.
[08:57] <porthose> this trust can be utilized to discuss the weaknesses of the mentee and thus the mentor is able to concentrate on improving these areas
[08:59] <dholbach> porthose: I was just interested to see how you think our general approach of teaching (docs, sessions, videos, help on irc and mailing lists, patch review, etc.) fits in with the more personal mentoring
[09:00] <dholbach> ok, but my question is answered :)
[09:00] <dholbach> persia, nixternal, soren: more questions?
[09:01] <nixternal> none here
[09:01] <soren> No, I think porthose has been grilled plenty.
[09:01]  * persia still kinda wants an answer
[09:01] <soren> Today and in the past :)
[09:03] <porthose> persia, I am a happy with the decision process for determining if patches go upstream, it's just that not all people do it.  to include myself, some time it is just a forgotten step in a persons work flow :)
[09:03] <persia> porthose: So you feel that the reason patches don't go to Debian is because people don't bother, rather than because they can't decide?
[09:04] <persia> Is there anything we could do to reduce the effort (grab the Debian package, build in a Debian environment, test in a Debian environment) that might make people do it more?
[09:06] <porthose> persia, to me it just comes natural to test in a debian and ubuntu chroot, because I do maintain packages in debian, an so that is how I would also mentor
[09:06] <porthose> I reall don't think it is because people don't bother, I think they just forget
[09:07] <dholbach> geser: questions? :)
[09:07] <persia> OK.
[09:08]  * geser has no questions
[09:08] <dholbach> [VOTE] Shall Charlie Smotherman become a MOTU?
[09:08] <MootBot> Please vote on:  Shall Charlie Smotherman become a MOTU?.
[09:08] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[09:08] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[09:08] <nixternal> +1
[09:08] <MootBot> +1 received from nixternal. 1 for, 0 against. 0 have abstained. Count is now 1
[09:08] <dholbach> +1
[09:08] <MootBot> +1 received from dholbach. 2 for, 0 against. 0 have abstained. Count is now 2
[09:08] <persia> +1
[09:08] <MootBot> +1 received from persia. 3 for, 0 against. 0 have abstained. Count is now 3
[09:08] <dholbach> soren, geser?
[09:08] <soren> +1
[09:08] <MootBot> +1 received from soren. 4 for, 0 against. 0 have abstained. Count is now 4
[09:09] <geser> +1
[09:09] <MootBot> +1 received from geser. 5 for, 0 against. 0 have abstained. Count is now 5
[09:09] <dholbach> [endvote]
[09:09] <MootBot> Final result is 5 for, 0 against. 0 abstained. Total: 5
[09:09] <dholbach> congratulations porthose!
[09:09] <nixternal> congrats porthose !
[09:09] <persia> Congratulations porthose
[09:09] <porthose> Thank You MC :)
[09:09] <dholbach> randomaction: still there? :)
[09:09] <persia> Welcome tothe team :)
[09:09] <randomaction> yep
[09:09] <dholbach> [TOPIC] Ilya Barygin's MOTU Application
[09:09] <MootBot> New Topic:  Ilya Barygin's MOTU Application
[09:09]  * porthose dances around the room and high fives his dog :)
[09:09] <dholbach> https://wiki.ubuntu.com/IlyaBarygin/MOTUApplication
[09:09] <dholbach> randomaction: how are you doing today? :)
[09:10] <randomaction> fine, thank you
[09:11] <persia> randomaction: So, you say you need better changelogs.  Could you describe a perfect changelog entry?
[09:12] <randomaction> sure, explain what you did, which files were changed, what bugs you close, possibly reference other things of interest
[09:13] <randomaction> e.g. "this should be dropped after [some thing] happens"
[09:13] <dholbach> randomaction: your work seems to be quite diverse... how do you usually decide what you work on?
[09:14] <randomaction> presently I mostly work on merges
[09:14] <randomaction> I have a list of outstanding merges sorted by last-changed-in-Ubuntu date
[09:15] <randomaction> so I request merges/syncs for packages that were touched long ago and were probably forgotten
[09:15] <dholbach> ok, I just had a look at your application again and you mentioned other QA activity too, like ftbfs fixes, etc
[09:15] <randomaction> yes, I plan to switch focus there after FF
[09:15] <dholbach> randomaction: how do you think we can fix the problem with the inclusion o fnew packages?
[09:15] <dholbach> ... of new packages
[09:16] <randomaction> this is hard - first you need to understand whether Ubuntu is all-inclusive or not
[09:17] <persia> randomaction: Do you believe it to be all-inclusive or not?
[09:17] <dholbach> and what does all-inclusive mean in this case? :)
[09:17] <randomaction> many packages are proposed by their authors, so it's hard to decide whether it's gonna be used by many people
[09:19] <randomaction> it's "people should not need to go anywhere else except official repos" vs "we should only include software that adds value / needed by many / etc"
[09:19] <randomaction> as things stand not, relatively few packages go through REVU, so as it happens only packages with sufficient interest are included
[09:20] <persia> randomaction: Do you have a preference for how Ubuntu should be?
[09:20] <randomaction> s/not/now/
[09:20] <randomaction> I think that there should be at least some selectiveness
[09:21] <persia> What sort of criteria should apply?
[09:21] <randomaction> (and we have it now, at the cost of hundreds unreviewed packages)
[09:22] <randomaction> probably something similar to Debian, can't remember what exactly they are, but they say something like "if you have a random piece of free software, don't expect it to be included automatically"
[09:23] <persia> Well, Debian expects someone to take responsibility for maintaining it as one of the criteria.  How might we handle a similar thing in the absence of defined maintainers?
[09:24] <randomaction> that said, if some software catches interest of, say, two Ubuntu devs, I think it's going to be included
[09:24] <randomaction> Ubuntu's packages not in Debian need maintenance
[09:24] <randomaction> so effectively the one who uploaded a package should take care of it
[09:25] <dholbach> you mean whoever packaged it, right?
[09:25] <randomaction> even if not listed as an official maintainer
[09:25] <persia> Or whoever uploaded it?
[09:25] <randomaction> yes, whoever packaged, as getting sponsorship is quite easy (yay for the empty queue btw!)
[09:26] <dholbach> ok :)
[09:26] <persia> randomaction: How do you feel about the use of new packaging as a way to learn packaging?
[09:26] <persia> (this is one argument for lots of REVU that has been used in the past)
[09:27] <randomaction> the more problematic the package, the more you will learn :)
[09:27] <randomaction> if rules.tiny works ok, you won't learn much I guess
[09:28] <randomaction> experience is gained by seeing different situations and understanding what happens where
[09:30] <dholbach> geser, soren, nixternal: more questions?
[09:30] <nixternal> none here
[09:30] <geser> none here
[09:30]  * dholbach neither
[09:30] <dholbach> persia: you're done?
[09:31] <persia> Well, I could probe at this for a while, but I don't need the discussion to make a decision.
[09:31] <dholbach> ok :)
[09:31] <dholbach> soren?
[09:33] <dholbach> ok.. I take that as a yes :)
[09:34] <dholbach> [VOTE] Shall Ilya Barygin become MOTU?
[09:34] <MootBot> Please vote on:  Shall Ilya Barygin become MOTU?.
[09:34] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[09:34] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[09:34] <nixternal> +1
[09:34] <MootBot> +1 received from nixternal. 1 for, 0 against. 0 have abstained. Count is now 1
[09:34] <dholbach> +1
[09:34] <MootBot> +1 received from dholbach. 2 for, 0 against. 0 have abstained. Count is now 2
[09:34] <geser> +1
[09:34] <MootBot> +1 received from geser. 3 for, 0 against. 0 have abstained. Count is now 3
[09:34] <persia> +1
[09:34] <MootBot> +1 received from persia. 4 for, 0 against. 0 have abstained. Count is now 4
[09:35]  * persia pokes soren with a sharper stick
[09:35]  * soren rushes back in
[09:35] <soren> +1
[09:35] <MootBot> +1 received from soren. 5 for, 0 against. 0 have abstained. Count is now 5
[09:35] <soren> Sorry, guys.
[09:35] <dholbach> [endvote]
[09:35] <MootBot> Final result is 5 for, 0 against. 0 abstained. Total: 5
[09:35] <nixternal> congrats randomaction
[09:36] <dholbach> congratulations randomaction!
[09:36] <persia> Welcome randomaction
[09:36] <randomaction> thank you
[09:36] <soren> It's like these meetings seem like an invite to random people to come and knock on my door.
[09:36] <nixternal> hehe
[09:36] <dholbach> hehe
[09:36] <nixternal> alrighty, off to bed for me
[09:36] <nixternal> g'nite all!
[09:36] <dholbach> night nixternal
[09:36] <dholbach> [TOPIC] Any other business?
[09:36] <MootBot> New Topic:  Any other business?
[09:37] <dholbach> Who's going to do the honours?
[09:37] <persia> As long as we're quorate in a formal meeting, I may as well confirm that we're happy to accept recommendations from the DMB on Contributing Developers until the Community Council completes the action from their recent decision.
[09:39] <dholbach> who's going to process the applications and everything?
[09:39] <dholbach> geser, soren, persia, nixternal, jpds, nhandler: ^? :-)
[09:39] <persia> I can do them in about 22 hours, but if someone can get to them faster, that would be better.
[09:41]  * dholbach has a bunch of other stuff to do today, but as nobody seems to volunteer I'll try to squeeze it in
[09:41] <dholbach> anything else?
[09:41] <persia> dholbach: Then if you miss, I'll get it early your tomorrow :)
[09:41] <dholbach> alrightie
[09:41] <dholbach> thanks everybody!
[09:42] <dholbach> adjourned
[09:42] <dholbach> #endmeeting
[09:42] <MootBot> Meeting finished at 03:42.
[15:57] <pitti> hello all
[15:57]  * slangasek waves
[15:57]  * fader_ waves.
[15:57] <ev> hi
[15:57] <ev> (standing in for cjwatson)
[15:57] <ttx> o/
[15:58] <fader_> I am standing in for marjo today.
[16:00]  * apw waves in a kernely way
[16:01]  * asac waves
[16:01] <slangasek> davidm, ogra, Riddell, jiboumans, ScottK, pgraner, njpatel, jdstrand: ping
[16:01] <Riddell> afternoon
[16:01] <njpatel> hey
[16:01] <jiboumans> o/
[16:01] <jdstrand> o/
[16:02] <slangasek> hi all
[16:02] <slangasek> #startmeeting
[16:02] <MootBot> Meeting started at 10:02. The chair is slangasek.
[16:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:02] <pitti> Riddell: hey Jonathan, thanks for joining in your holidays
[16:02] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-01-08
[16:02] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-01-08
[16:02] <Riddell> pitti: it's not my holidays (as far as I know?)
[16:02] <pitti> Riddell: oh, I thought so; nevermind then
[16:02] <slangasek> [TOPIC] actions from previous meeting
[16:03] <MootBot> New Topic:  actions from previous meeting
[16:03] <slangasek>   * slangasek to confirm with asac how to get the list of packages that still need rebuilt for arm toolchain
[16:03] <slangasek>   * ttx, zul to target all the canonical-application-support MIRs to lucid, and milestone to alpha-2
[16:03] <slangasek>   * slangasek to check on ld segfault on powerpc building qt4-x11 (DONE, but handed back to kubuntu team to figure out how to integrate the workaround...)
[16:03] <ttx> slangasek: done
[16:03] <asac> done
[16:03] <slangasek> ttx: ta
[16:03] <Riddell> qt4-x11 compiled on powerpc
[16:03] <Riddell> thanks to slangasek for pointing us the way
[16:04] <slangasek> ah, great!
[16:04] <slangasek> piece of cake :)
[16:04] <slangasek> [TOPIC] QA Team
[16:04] <MootBot> New Topic:  QA Team
[16:04] <fader_> Hi
[16:04] <slangasek> fader_: how are we doing?
[16:04] <fader_> * Hardware testing
[16:04] <fader_> http://people.canonical.com/~fader/hw-testing/current
[16:04] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current
[16:04] <fader_> Netbooks:
[16:04] <fader_> 	passed:  7 (54%)   failed: 2 (15%)   untested: 4 (31%)
[16:04] <fader_> Laptops:
[16:04] <fader_> 	passed: 21 (80%)   failed: 3 (12%)   untested: 2 ( 8%)
[16:04] <fader_> Servers:
[16:04] <fader_> 	passed: 45 (87%)   failed: 0 ( 0%)   untested: 7 (13%)
[16:04] <fader_> Desktops:
[16:04] <fader_> 	passed: 12 (92%)   failed: 1 ( 8%)   untested: 0 ( 0%)
[16:04] <fader_> Open bugs:
[16:04] <fader_> bug 497546
[16:04] <fader_> bug 503700
[16:04] <fader_> bug 504315
[16:05] <fader_> We have several untested machines since the holidays, but they all appear to be for environmental reasons.
[16:05] <fader_> I am working my way through them and getting them tested, but it is taking me a bit to get through the backlog of them.  They should be all done by next week.
[16:05] <fader_> Specs:
[16:05] <fader_> http://piware.de/workitems/qa/lucid/report.html
[16:05] <MootBot> LINK received:  http://piware.de/workitems/qa/lucid/report.html
[16:05] <fader_> * UbuntuSpec:lucid-qa-checkbox-desktop-experience-tests
[16:05] <fader_>         [cr3] Add DX PPA when testing and reboot if new packages are discovered: INPROGRESS
[16:05] <fader_> * UbuntuSpec:lucid-qa-checkbox-integrate-regression-testing
[16:05] <fader_>         [cr3] fixed support for QRT-Packages from the qa regression testing suite; confirmed to work by sbeattie
[16:05] <fader_> * UbuntuSpec:lucid-qa-kernel-test-automation
[16:05] <fader_>         [cr3] Initial daily kernel tests running by Lucid Alpha1: INPROGRESS
[16:05] <fader_> 	[cr3] The kernel tests (most of them) need sudo: INPROGRESS
[16:05] <fader_> * UbuntuSpec:lucid-qa-iso-tracker
[16:05] <fader_> 	There is one work item still to go, a pending merge, so ara has asked that this be defered to alpha-3.  The rest of the work items will be in production next week.
[16:05] <fader_> * UbuntuSpec:qa-lucid-automated-server-testing
[16:05] <fader_>          nightly builds of a set of server packages (in a PPA) that will show us if something regresses
[16:05] <fader_>           sbeattie was trying to get some of the q-r-t tests running Checkbox, but had some issues with tests that wanted to run as root, which most (all?) of the server related ones did, so there's some Checkbox infrastructure work
[16:05] <fader_> needed there.
[16:06] <fader_> [end of massive text dump]
[16:06] <pitti> fader_: so the netbook-launcher worked again?
[16:07] <fader_> pitti: No, it is still not working as of yesterday
[16:07] <fader_> I missed that in my open bugs, sorry
[16:07] <pitti> fader_: should have been fixed today (bug 495066)
[16:07] <fader_> pitti: I will re-test and make sure it's working now, thanks!
[16:07] <pitti> I just wondered
[16:07]  * asac uploaded it ;) 
[16:07] <asac> fader_: thanks for testing.
[16:07]  * pitti hugs asac
[16:08] <asac> we couldnt verify because australia was already evening ;)
[16:08] <fader_> asac: Yeah, I saw the update to it in my email this morning but I haven't run any tests on the netbooks yet today
[16:08] <fader_> I believe you though, so it'll just be confirmation ;)
[16:08] <slangasek> fader_: are these various "in progress" items going to be done on time for alpha-2, as the milestone targeting implies they should?
[16:09] <fader_> slangasek: I don't know; cr3 might be able to answer for his items
[16:09] <fader_> I will ping him
[16:10] <fader_> (And ara's spec has been retargeted for alpha 3)
[16:11] <cr3> fader_: kernel tests are definately targetted for alpha-2
[16:12] <fader_> cr3: What about the lucid-qa-checkbox-desktop-experience-tests spec?
[16:12] <fader_> [cr3] Add DX PPA when testing and reboot if new packages are discovered: INPROGRESS
[16:12] <cr3> fader_: not sure, I'll need to follow up with the DX folks on that one
[16:13] <slangasek> fader_: whic spec has been retargeted?  lucid-qa-iso-tracker is still targeted to alpha-2
[16:13] <fader_> slangasek: Hmm, I was going based on what ara told me this morning that she had discussed it with marjo and he agreed to re-target it
[16:13] <slangasek> cr3: please do that today, so that if it's not going to land it can be retargeted
[16:14] <fader_> That's all the info I have; I know marjo is in training today so perhaps he has not updated lp because of that
[16:14] <cr3> slangasek: will do
[16:14] <slangasek> fader_: ok; will you follow up with marjo on this?
[16:14] <fader_> slangasek: Will do
[16:15] <slangasek> [ACTION] fader_ to check with marjo whether lucid-qa-iso-tracker is deferred to alpha-3, and re-target appropriately in LP
[16:15] <MootBot> ACTION received:  fader_ to check with marjo whether lucid-qa-iso-tracker is deferred to alpha-3, and re-target appropriately in LP
[16:15] <fader_> though it may be late in the day before I can get an answer, as he is incommunicado
[16:15]  * ScottK waves
[16:17] <slangasek> as a general note, we seem to be well above our burn lines in a lot of teams since the beginning of the year, which implies that a lot of these work items are not getting done before alpha-2; we need to make sure we're reviewing the status of what is or isn't getting deferred and document that in the status
[16:17] <slangasek> s/document/documenting/
[16:17] <slangasek> the charts aren't a very effective tool if they don't reflect what's actually going on in teams
[16:18] <slangasek> any other concerns on qa?
[16:18] <slangasek> bug #503700> I'm hopeful that this might be a manifestation of the other X bug that's in progress, but we'll cover that under desktop
[16:19] <fader_> slangasek: Could be; I'm working on getting backtraces etc. for Bryce for it
[16:19] <slangasek> I've been trying to get a good backtrace out of X in lucid for over a month now
[16:20] <slangasek> (well, not fighting very hard, but apparently even working around the kernel bug doesn't do it)
[16:20] <fader_> I feel your pain
[16:20] <slangasek> [TOPIC] Desktop Team
[16:20] <MootBot> New Topic:  Desktop Team
[16:20] <slangasek> fader_: thanks
[16:20] <slangasek> pitti: hi
[16:20] <pitti> on that note, yesterday's kernel finally fixed apport
[16:20] <pitti> that should hopefully enable us to get better crash reports again
[16:20] <pitti> apport itself is enabled since Wednesday or so
[16:20] <pitti> I'll test it as soon as it lands in lucid
[16:21] <pitti> As usual, our report is at https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:21] <pitti> In the last two weeks we focused on:
[16:21] <pitti> - Got A2 specs done (except for two WIs which only affect external projects, not Ubuntu itself)
[16:21] <pitti> - More boot speed work
[16:21] <pitti> - New GNOME version
[16:21] <pitti> - New wave of DX integration yesterday and today
[16:21] <pitti> No major changes planned for alpha-2 any more.
[16:21] <pitti> Bug front is relatively quiet.
[16:22] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:22] <jdstrand> (I just binary deNEWd 10.14)
[16:22] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:22] <Riddell> on the Kubuntu side KDE 4.4 Release Candidate packages are now uploaded and building
[16:22] <pitti> actually, the "two WIs left" is kind of a lie, which my new WI tracker just uncovered; we have three more for other teams (see http://macaroni.ubuntu.com/~pitti/workitems/canonical-desktop-team-lucid-alpha-2.html)
[16:22] <pitti> I'll have a look at them after the meeting
[16:22] <jdstrand> (wrt new kernel hitting lucid)
[16:22] <pitti> jdstrand: yay
[16:22] <Riddell> we have three outstanding MIR bugs which are blocking where I'd like to be for alpha 2
[16:23] <Riddell> I havn't caught up on must of the administrata since new year so spec and critical bug statuses I need to update next week
[16:24] <pitti> bug 492931 just asks for enabling the test suite
[16:24] <pitti> so this could be pre-promoted already
[16:24] <pitti> what are the other two?
[16:24] <Riddell> virtuoso-opensource 503774
[16:24] <Riddell> libdbusmenu-qt 504267
[16:24] <asac> afaik libssh had security team concerns? not sure if we should pre-promote it with that.
[16:25] <pitti> asac: pending test suite enablement, kees approved it
[16:25] <asac> cool
[16:25] <pitti> Riddell: please move those two to lucid/alpha-2, I'll have a look ASAP
[16:25] <Riddell> ok thanks
[16:25] <pitti> (need to unbreak my browser first before I can add release targets, sorry)
[16:26] <asac> browser broken by todays update?
[16:26] <pitti> asac: no, greasemonkey stuff in lp-firefox-improvements
[16:26] <asac> good
[16:27] <slangasek> I see from the report that bug #494627 is fixed as of 3h ago
[16:28] <slangasek> fader_: ^^ that's the bug that I think might be the master for the nvidia issue you're seeing; can you prioritize retesting the hardware that was affected, to confirm?
[16:28] <fader_> slangasek: Will do; thanks
[16:28] <fader_> It sounds similar as I believe the segfaults we were seeing were all on nv hardware
[16:28] <slangasek> [ACTION] fader_ to verify whether 494627 == 503700 by re-testing affected hardware
[16:28] <MootBot> ACTION received:  fader_ to verify whether 494627 == 503700 by re-testing affected hardware
[16:29] <slangasek> fwiw, I've got a segfault-on-lid-close that I think is also the same bug, on intel
[16:29] <slangasek> so I'll be eagerly retesting here :)
[16:29] <slangasek> anything further to discuss on desktop?
[16:30] <slangasek> [TOPIC] DX Team
[16:30] <MootBot> New Topic:  DX Team
[16:30] <slangasek> pitti, Riddell: thanks
[16:30] <slangasek> davidbarth, njpatel: hello
[16:30] <davidbarth> hi
[16:31] <davidbarth> so DX was working this week on app. indicator mostly
[16:31] <davidbarth> the status is up at https://wiki.ubuntu.com/DesktopExperienceTeam/LucidReleaseStatus
[16:31] <davidbarth> of note
[16:31] <davidbarth> app. indicator is mostly there and complete (as of planned for A2)
[16:32] <davidbarth> we're getting a very positive feedback from the community, as well as a lot of help from the community team
[16:32] <davidbarth> we're working on missing features that we'll land early in a3 (automatic updates and transparent fallback)
[16:32] <slangasek> davidbarth: I see http://piware.de/workitems/dx/lucid-alpha2/report.html has been updated since yesterday, with items postponed as needed; are these postponed indefinitely, or do we now expect them to land later in the cycle?
[16:32] <davidbarth> but they won't be in a2 for the freeze; ppa release
[16:33] <davidbarth> yes, that's the other part of the report
[16:33] <slangasek> ok, please continue :)
[16:33] <davidbarth> a lot of other work items have been postponed
[16:33] <davidbarth> that's not a great news, in that we expected to do a bit more (though not all); but it indicates that we over-commited a bit too much
[16:34] <davidbarth> we assessed the situation with other managers and will be proposing a plan to adjust the scope to secure developments based on priorities
[16:34] <davidbarth> last
[16:34] <davidbarth> the session menu and the me menu have been split
[16:34] <davidbarth> (sorry not last)
[16:35] <slangasek> I guess the xsplash integration is going to hold up work on other teams for lucid, isn't it?  (boot performance / boot experience on foundations' side)
[16:35] <davidbarth> and for gtk patches; we have the argb support mostly there (bratsche is fixing the totem crasher as we speak)
[16:35] <davidbarth> but cs-deco is at risk
[16:35] <slangasek> ok
[16:36] <davidbarth> we couldn't get a review in time for gtk 2.20, so we're concerned that the distro-patch may be too big to carry for an LTS
[16:36] <davidbarth> that's the summary
[16:36] <davidbarth> questions? on particular points?
[16:36] <davidbarth> xplash (sorry reading up the log)
[16:37] <slangasek> I think that's my only question presently
[16:37] <davidbarth> we can't release a plugin version right now, though we have a branch with scott's code; but no time to really make that work for a2
[16:37] <davidbarth> i understand this is preventing the integration check
[16:38] <slangasek> oh - I did also notice yesterday that there was a workitem assigned to canonical-foundations for dx-lucid-xsplash (again, the problem pitti mentioned in his mails about not seeing cross-team WI assignments) - have you guys talked to anyone specifically on foundations about doing this, or do we need to figure out on our side who can take it?
[16:39] <slangasek> right, not for a2 - what about soon after a2?
[16:39] <davidbarth> the security check, right
[16:39] <davidbarth> yes, need to do that; that was not critical for a2, but needs to happen as part of the code review anyway
[16:40] <davidbarth> i take the action of reviewing that list of assignements outside of dx and contact the right persons
[16:41] <slangasek> [ACTION] davidbarth to review cross-team assignments for dx specs and contact right people
[16:41] <MootBot> ACTION received:  davidbarth to review cross-team assignments for dx specs and contact right people
[16:41] <slangasek> thanks
[16:41] <slangasek> anything else to discuss on DX today?
[16:41] <slangasek> [TOPIC] Mobile Team
[16:41] <MootBot> New Topic:  Mobile Team
[16:41] <slangasek> davidbarth: thanks much
[16:41] <slangasek> asac: hello
[16:42] <asac> hi
[16:42] <asac> summary:
[16:42] <asac>  * 2d-launcher archive uploads/MIRs
[16:42] <asac>   * MIR concerns/maybe pre-promote
[16:42] <asac>  * uboot imx51 work
[16:42] <asac>   * generally works, issues with .img partitioning under investigation
[16:42] <asac>  * marvel/fsl kernel update preparations for a2
[16:42] <asac>   * verified, pending upload.
[16:42] <asac>  * armel-only ftbfs for main
[16:42] <asac>   * almost on top
[16:43] <asac>  * lsb-lib porting
[16:43] <asac>   * required bits are ported; next packaging/deployment
[16:43] <asac>  * chromium porting/license review
[16:43] <asac>   * chromium runtime issues resolved
[16:43] <asac>   * licensing in reasonably good shape.
[16:43] <asac>  * getting a2 burndown in better shape
[16:43] <asac>   * down to trendline again.
[16:43] <asac> [LINK]  * getting a2 burndown in better shape * down to trendline again.
[16:43] <MootBot> LINK received:   * getting a2 burndown in better shape * down to trendline again.
[16:43] <asac> oops
[16:43] <asac> [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:43] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:43] <asac> [LINK] http://piware.de/workitems/mobile/lucid-alpha2/report.html
[16:43] <MootBot> LINK received:  http://piware.de/workitems/mobile/lucid-alpha2/report.html
[16:44] <asac> so on RC bug front we made good progress
[16:45] <asac> some kernel related issues not yet understood, but thats still ok at this point.. expecially since we will get a new one
[16:45] <asac> on spec front:
[16:45] <asac> burndown chart for alpha-2 looks quite good now after we catched up the holiday backlog
[16:45] <asac> the overall burndown is above, but we will address that when reviewing a3 goals
[16:46]  * slangasek nods
[16:46] <asac> some specs will land shortly after a2
[16:46] <asac> * mobile-lucid-arm-gcc-v7-thumb2: most ftbfs issues resolved; review work items will get done at a2; rebuild of missing packages during a3
[16:47] <asac> so that was basically never planned to be finished for alpha2 ... as the rebuild etc. was ment to happen around DIF
[16:47] <slangasek> right
[16:47] <asac> * mobile-lucid-une-2d-launcher: blocked on MIR and seeding
[16:47] <asac> we hope we can address the mir issues for a2 still
[16:47] <asac> at least to a point where we can pre-promote
[16:47] <asac> but unlikely that the switch to UNE seed will happen for the a2 image. but right afterwards
[16:48] <slangasek> the MIRs themselves don't seem to be linked from the blueprint? (and therefore don't show up on the WI tracker)
[16:48] <slangasek> could you link them?
[16:48] <asac> hmm. i can check that
[16:48] <asac> action?
[16:48] <slangasek> [ACTION] asac to link une-2d-launcher MIRs from blueprint
[16:48] <MootBot> ACTION received:  asac to link une-2d-launcher MIRs from blueprint
[16:48] <asac> thx
[16:49] <asac> * mobile-lucid-imx51-debian-cd-to-uboot: issues with partitioning -> unlikely to make a2
[16:49] <asac> ogra is investigating
[16:49] <ogra> but the having the MIR processed soon would be nice :)
[16:49]  * slangasek nods
[16:49] <asac> unfortunately i toasted my board while working on that, but i still hope that this will happen soon
[16:50] <asac> [ACTION] asac to link MIR for uboot to spec
[16:50] <asac> * mobile-lucid-bringup-testing: 2 work items will slip into a3 cycle
[16:50] <asac> thats not archive related, so its ok i thin. its basically figuring out how to extract some system information we want to include
[16:50] <slangasek> [ACTION] asac to link MIR for uboot to spec
[16:50] <MootBot> ACTION received:  asac to link MIR for uboot to spec
[16:50] <asac> might be that its not possible and those work items get postponed
[16:51]  * asac feels underpowered :)
[16:51] <asac> * mobile-lucid-arm-lightweightbrowser: benchmark/review/archive upload pending
[16:51] <asac> chromium porting to arm took longer, as it takes like 16h to build :) ... but we are at it and doing the benchmarking etc. now
[16:51] <asac> so its good. also the licensing was hard work, but i think we are in good shape :)
[16:52] <slangasek> I see the benchmarking is assigned to dave-martin-arm - are you in communication with him about that, and do you expect that to happen soon?
[16:52] <asac> http://people.canonical.com/~asac/tmp/copyright.full if someone is interested
[16:52] <MootBot> LINK received:  http://people.canonical.com/~asac/tmp/copyright.full if someone is interested
[16:52] <slangasek> benchmarking etc. now> ah, ok
[16:52] <ogra> he attends each of our meetings
[16:52] <asac> slangasek: yes. arm has internal tools
[16:52] <ogra> so there is close communication
[16:52] <asac> it was blocked by not having firefox/chromium
[16:52]  * slangasek nods
[16:53] <asac> but both is now resolved, so the last few items will get done swiftly... then decision and seed inclusion
[16:53] <asac>  * mobile-lucid-arm-lib-tests: late; porting done; reassigned packaging, deployment and execution to team to help out.
[16:53] <asac> we had to shuffle assignments in team a bit ... this will get on track soon
[16:53] <slangasek> I see there's a workitem assigned to mcasadevall for adding arm images to the ISO tracker, which I'm pretty sure he doesn't have access to do - should that be reassigned to me or to someone on QA?
[16:54] <asac> we need it for the thumb2 spec ... so around DIF
[16:54] <slangasek> or is there groundwork he's doing there first?
[16:54] <ogra> its just about him taking care of contacting you guys
[16:54] <asac> slangasek: the assignment basically means that he should take care of it, but if you want to take that item directly i would be happy
[16:54] <slangasek> [ACTION] slangasek to claim "adding ARM alternate images to the ISO tracker"
[16:54] <MootBot> ACTION received:  slangasek to claim "adding ARM alternate images to the ISO tracker"
[16:54] <asac> slangasek: according to him alternate images are finished. just needs to get produced and verified
[16:54] <asac> thanks i will assign that work item to you (if there is a matching one)
[16:55] <asac> the others are fortunately done
[16:55] <slangasek> "produced" - so they're not in the cronjob yet?
[16:55] <ogra> slangasek, they are ... since jaunty
[16:55] <slangasek> ok
[16:55] <asac> i dont know abut the details, but i think so
[16:55] <ogra> we never had them on the tracker
[16:55] <asac> they were broken for two cycles, so i guess not
[16:55] <slangasek> let's take any further discussion of that offline, meeting's running a bit behind
[16:55] <slangasek> anything else on the mobile front that needs covered?
[16:55] <JamieBennett> MIR's linked to 2D Launcher blueprint now - https://blueprints.edge.launchpad.net/ubuntu/+spec/mobile-lucid-une-2d-launcher
[16:55] <asac> yes. so only risky thing for a2 is: * new upstream/fsl kernel for imx51 and dove
[16:56] <asac> thats it
[16:56] <asac> but we verified those kernels already today
[16:56] <asac> so they should be good
[16:56] <slangasek> ok
[16:56] <asac> if upload doesnt happen on monday we have to push that after a2
[16:56] <ogra> imx kernel looks pretty awesome, i dont expect issues
[16:56] <ogra> (kudos to the kernel team !)
[16:56] <asac> yep
[16:56] <slangasek> please keep #ubuntu-release in the loop regarding any problems that do turn up there
[16:56] <slangasek> [TOPIC] Server Team
[16:56] <MootBot> New Topic:  Server Team
[16:56] <ttx> o/
[16:56] <asac> thanks!
[16:56] <slangasek> asac, ogra: thanks
[16:56] <slangasek> ttx: hiya
[16:57] <ogra> thanks !
[16:57] <ttx> Team status updated at:
[16:57] <ttx> https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:57] <ttx> Weekly news: The server team was very busy this week (and still is) trying to complete all alpha-2 blueprints in time
[16:57] <ttx> We expect to finalize the work items affecting the Server ISO by Monday, in time for the soft freeze
[16:57] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:57] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:57] <ttx> Work affecting the Alpha2 cloud images is expected to land by Tuesday
[16:57] <ttx> Some MIR/promotion/demotion work (canonical-application-support, seeds) might also land on Tuesday
[16:57] <ttx> Others, like UEC testing, do not result in any alpha2 deliverable and still have until Thursday to be completed
[16:58] <ttx> On the Alpha2-milestoned bugs front:
[16:58] <ttx> Bug 462169 might need some retargeting ?
[16:58] <ttx> slangasek: ^ ?
[16:58] <slangasek> "Establish access to central hardware when available"> I'm not surprised to see that workitem isn't done, given that it's a WI at all because we've had problems there in the past... is more escalation needed to make that happen?
[16:59] <slangasek> ttx: oh, I have that listed under foundations ;)  Yes, I'll have that fixed beginning of next week
[16:59] <ttx> Other bugs account for work items in the blueprints, we'll see them in detail next
[16:59] <ttx> we expect access to hardware on Thursday :)
[16:59] <jiboumans> slangasek: that is targeted for the 14th by IS
[16:59] <slangasek> jiboumans: great, thanks
[16:59] <ttx> Let's look at alpha2-targeted blueprints in detail, now:
[16:59] <jiboumans> slangasek: our alpha3 goals include *using* it :)
[16:59] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-canonical-application-support
[17:00] <ttx> 89% completed, on track, still misses some MIR review:
[17:00] <ttx> bug 493594: MIR for pastedeploy (zul) -- still needs MIR assignee/review
[17:00] <ttx> the others have been reviewed and in good shape
[17:00] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-ec2-boothooks
[17:01] <ttx> 57% completed, met some unexpected behavior with upstart/EC2, only 6 work items left, should be in time for alpha2 cloud images
[17:01] <ttx> this one is the most in danger, but we still think we can complete it
[17:01] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-ec2-config
[17:01] <ttx> 50% completed, expected to be at 80% by the end of the day, on track for alpha2 cloud images
[17:01] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-euca-remote-autoregister
[17:01] <ttx> Work items for alpha2 completed. Some bugfixes and security improvements expected in alpha3.
[17:02] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-eucalyptus-karmic-retrospective
[17:02] <ttx> 92% completed, last item depends on IS delivery
[17:02] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-landscape-refresh
[17:02] <ttx> All work items completed
[17:02] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-seeds
[17:02] <ttx> 69% completed, still pending some discussion, end on Monday
[17:02] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-uec-testing
[17:02] <ttx> 62% completed, on track, can be completed next week (we have until Thursday for this one)
[17:03] <ttx> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-cloud-krd
[17:03] <slangasek> I note "irqbalance - add to the default install" is targeted to a2; I'd suggest deferring that to a3 explicitly, I think the discussion that should happen before it's enabled by default is going to run longer than our window
[17:03] <ttx> slangasek: good point
[17:03] <ttx> please action me
[17:03] <slangasek> [ACTION] ttx to target "irqbalance - add to the default install" to a3
[17:03] <MootBot> ACTION received:  ttx to target "irqbalance - add to the default install" to a3
[17:04] <ttx> 89% completed. I just learned that the last item (dependent on kernel team) won't get into alpha2
[17:04] <ttx> bug 494565
[17:04] <ttx> This is mostly optional, useful for testing
[17:04] <ttx> so we'll probably have to defer that one as well.
[17:04]  * slangasek nods
[17:04] <ttx> Note that the feature is currently buggy due to a mountall issue, bug 503212
[17:05] <ttx> It would be great to have this one fixed
[17:05] <ttx> I nominated it for alpha2, but there is no assignee yet
[17:05] <ttx> foundations team, anyone ? :)
[17:06] <slangasek> assigned to self
[17:06] <ttx> many thanks
[17:06] <ttx> finally, https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-euca2ools
[17:06] <ttx> All alpha2work items completed
[17:06] <ttx> burndownchart-wise, We should hit the line atthe end of the day
[17:06] <slangasek> and then tomorrow the line will move ;)
[17:06] <ttx> if nobody has been lying to me
[17:07] <slangasek> but yes, looks good
[17:07] <ttx> Alpha3 planning work started this week, more on that... next week.
[17:07] <slangasek> ack
[17:07] <slangasek> anyone else have anything to bring up with the server team?
[17:07] <jiboumans> all clear here
[17:08] <slangasek> [TOPIC] Kernel Team
[17:08] <MootBot> New Topic:  Kernel Team
[17:08] <slangasek> ttx, jiboumans: thanks
[17:08] <slangasek> apw: hi
[17:08] <apw> Overall Kernel Team status is summarised at the first URL below, including the items called out in the agenda.  Overall we are doing pretty well with only a small number of items being pushed out to Alpha-3, see the second link for an Alpha-2 summary.  We are still below the burndown line despite the holidays.
[17:08] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[17:08] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[17:08] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20lucid-alpha-2
[17:08] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid#Milestone%20lucid-alpha-2
[17:08] <apw> AppArmour is looking better with the alpha-2 deliverables expected to make it.  Boot performance is pretty good at ~1.6s with some variablilty updates just hitting the archive.  KMS progress is a good for ATI with a number of fixes for radeon coming in, nouveau is a little slow with us hoping to have a package for very early Alpha-3.  The rest of our Alpha-2 deliverables either are on track or have been pushed out to Alpha-2.  We may have to uplo
[17:08] <apw> ad the kernel once more to fix an Alpha-2 targetted bug (bug #488636).  The kernel is currently at 2.6.32.2 and we have a 2.6.32.3 update to apply as soon as the Alpha-2 freeze is lifted.
[17:11] <slangasek> sounds good to me
[17:11] <slangasek> anything else?
[17:11] <apw> nothing from me
[17:12] <slangasek> questions from others on kernel?
[17:12] <slangasek> [TOPIC] Security Team
[17:12] <MootBot> New Topic:  Security Team
[17:12] <slangasek> apw: thanks
[17:12] <slangasek> jdstrand: hi
[17:12] <jdstrand> hi
[17:12] <jdstrand> as usual: https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:13] <jdstrand> We've had to postpone lower priority items, and are making progress on higher priority ones.
[17:13] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:13] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:13] <jdstrand> A bug worth mentioning is: bug #503869. This bug slows down profile cache generation significantly under some circumstances and affects progress on security-lucid-apparmor-tunables.
[17:13] <jdstrand> A profile's cache is regenerated whenever a package that ships a profile is upgraded (eg, 503869 was noticed due to a slow evince upgrade). Specifically, we needed to revert the apparmor change for likewise-open in bug #274350.
[17:13] <jdstrand> This should be improved by jjohansen's current dfa minimization work once it lands.
[17:14] <jdstrand> apparmor in Lucid now has support for tunables/home.d (part of the same spec), so the current plan is to have likewise-open ship its own tunable, this way only likewise-open users will be affected by slow profile generation until the dfa work is done.
[17:14] <jdstrand> Another part of that spec is to detect user's home directory and dynamically generate the HOMEDIRS tunable. This will also affect profile cache generation times, but not nearly as much as the likewise-open tunable, which uses a glob in the tunable.
[17:15] <jdstrand> still trying to get that part in for alpha-2, but may be alpha-3
[17:15] <jdstrand> on a related note, kees is following up on profile cache generation at the end of the installer, so that first boot is not affected by any of this.
[17:16] <ev> we've actually just resolved that an hour ago.  We're reverting the apparmor=0 change to the live CD and kees has already uploaded a new apparmor and ifupdown to detect the live CD in the init scripts.  I'll add the profile cache generation to the end of the install on Monday.
[17:16] <slangasek> great
[17:16] <jdstrand> \o/
[17:16] <jdstrand> that's it from me
[17:17] <slangasek> ok
[17:17] <slangasek> anyone else have questions for security?
[17:17] <slangasek> [LINK] Foundations Team
[17:17] <MootBot> LINK received:  Foundations Team
[17:17] <slangasek> jdstrand: thanks
[17:17] <jdstrand> sure :)
[17:17] <slangasek> ev: hello
[17:17] <ev> slangasek: hi
[17:17] <ev> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:17] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:17] <ev> [LINK] http://piware.de/workitems/foundations/lucid-alpha2/report.html
[17:17] <MootBot> LINK received:  http://piware.de/workitems/foundations/lucid-alpha2/report.html
[17:17] <mdz> slangasek: I have two brief items for the foundations team, if I may (at the end)
[17:18] <ev> We're looking good for alpha-2.
[17:18] <ev> foundations-lucid-boot-experience is done on our end.
[17:18] <ev> Riddell: did you get "no root" support into KDM?
[17:18] <ev> foundations-lucid-boot-recovery: mvo is going to do the last two items on Monday.
[17:18] <slangasek> mdz: certainly
[17:18] <ev> foundations-lucid-gfxboot-update:
[17:18] <ev> I suspect "Replace "Safe graphics mode" with bullet-proof X, with automatic VESA fallback" will not land for alpha-2, but I'll confirm with cjwatson as I intend to work on that area as well for an oem-config specification.
[17:18] <ev> davidbarth: I take it the installer gdm greeter will need to be deferred, correct?
[17:19] <ev> I believe Michael Forrest has looked over the new "try ubuntu without installing" string, but I'll send him a mail asking him to close the work item or follow up with cjwatson.
[17:19] <ev> I'm trying to reproduce bug 495012 now, and have assigned it to myself.
[17:19] <ev> [LINK] http://piware.de/workitems/foundations/lucid/report.html
[17:19] <MootBot> LINK received:  http://piware.de/workitems/foundations/lucid/report.html
[17:20] <ev> We were doing fine leading up to the holidays, but I imagine we may end up having to defer some things.  I'll raise it at the next team meeting.
[17:20] <ev> and that's it from me
[17:20] <davidbarth> ev: unfortunately yes, it won't ready today or even monday
[17:21] <ev> davidbarth: okay, thanks
[17:21] <slangasek> is there an action for the above?  I don't see "gdm greeter" anywhere in the workitems
[17:21] <slangasek> oh, "develop a greeter offering..."?
[17:21] <ev> indeed
[17:22] <slangasek> ev: you'll retarget?
[17:22] <ev> slangasek: sure
[17:22] <slangasek> [ACTION] ev to retarget foundations-lucid-gfxboot-update greeter to alpha-3
[17:22] <MootBot> ACTION received:  ev to retarget foundations-lucid-gfxboot-update greeter to alpha-3
[17:23] <slangasek> ev: anything else?
[17:23] <ev> nope
[17:23] <slangasek> mdz: you had a couple of things?
[17:23] <mdz> slangasek: I just filed bug 504847 about a cron crash, which (although no one else had seen it when I asked) looks like it is not specific to me
[17:24] <mdz> it looks like cron should have been restarted after a recent glibc upgrade, but wasn't
[17:24] <slangasek> oh, indeed; I caught a whiff of that earlier, thanks for jogging my memory
[17:24] <mdz> slangasek: I subscribed you to the bug because I couldn't figure out how to make it public
[17:24] <mdz> I found a workaround and made it public, but can't unsubscribe you, so sorry for the spam
[17:25] <slangasek> no problem, I'll probably go ahead and work that bug today anyway
[17:25] <mdz> #2 is, while I was there, I noticed there seemed to be a stack of untriaged bugs on cron, including some other crashes which looked potentially related
[17:25] <mdz> https://bugs.edge.launchpad.net/ubuntu/+source/cron
[17:25] <slangasek> in fact, cron is crashing here for me even after a reboot
[17:25] <mdz> slangasek: hmm, restarting fixed it for me on 1 of the 2 systems where I saw that bug
[17:25] <mdz> (I haven't tried the other yet)
[17:25] <mdz> (restarting cron, that is)
[17:26] <mdz> Keybuk seems to be the bug contact
[17:26] <slangasek> [ACTION] slangasek to do some triaging of cron bug reports
[17:26] <MootBot> ACTION received:  slangasek to do some triaging of cron bug reports
[17:27] <slangasek> I think Keybuk probably has his hands full right now
[17:27] <slangasek> mdz: thanks for bringing this to our attention
[17:27] <mdz> slangasek: np, thanks for checking into it
[17:27] <mdz> that's all from me
[17:27] <slangasek> anyone else?
[17:28] <slangasek> [TOPIC] MOTU
[17:28] <MootBot> New Topic:  MOTU
[17:28] <slangasek> ScottK had to jet, but gave me a brief summary, which I'll dump in
 Nothing major to report on MOTU.  FTBFS numbers are improving.  The volunteer for the rebuildable binaries spec is working on it, but he got sick/had to have surgery so we're slightly delayed.  Expect to have that done before Alpha 3.
[17:28] <slangasek> any other concerns on MOTU?
[17:29] <slangasek> [TOPIC] AOB
[17:29] <MootBot> New Topic:  AOB
[17:29] <slangasek> anything else at all? :)
[17:29] <slangasek> #endmeeting
[17:29] <MootBot> Meeting finished at 11:29.
[17:29] <slangasek> thanks, folks
[17:30] <pitti> thanks all
[17:30] <ev> thanks