=== WaVeR` is now known as WaVeR === lan3y is now known as Laney === doko__ is now known as doko === nxvl_ is now known as nxvl === Amaranth__ is now known as Amaranth === asac_ is now known as asac === alsroot_ is now known as alsroot === Igorot is now known as Knightlust === JamieBennett1 is now known as JamieBennett === jarlen_ is now known as jarlen [13:00] * asac waves [13:00] #startmeeting [13:00] Meeting started at 07:00. The chair is NCommander. [13:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [13:00] morning all [13:00] G'day [13:00] need coffee [13:00] Zzzz [13:01] Happy New Year ! [13:01] [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20100105 [13:01] LINK received: https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20100105 [13:01] * ogra waves (with a head that doesnt feel like it fits through the door) [13:01] [link] http://piware.de/workitems/mobile/lucid-alpha2/report.html [13:01] LINK received: http://piware.de/workitems/mobile/lucid-alpha2/report.html [13:02] [topic] Action Item Review [13:02] i guess we can ignore the ARs this week :) [13:02] New Topic: Action Item Review [13:03] [topic] cooloney to ask ericm about 2.6.32 patches for marvell dove [13:03] New Topic: cooloney to ask ericm about 2.6.32 patches for marvell dove [13:03] i think ericm_ just got the .32 patches from marvell [13:03] NCommander, btw. you should include one of the kernel guys in the meeting ping in the future [13:04] ogra, ah, will do [13:04] both please [13:04] [topic] NCommander to email Marvell about the date of the next expected kernel drop [13:04] New Topic: NCommander to email Marvell about the date of the next expected kernel drop [13:05] c/o on this one, although if ericm_ got the 32 patches already, then not needed. [13:05] [topic] asac, ogra, persia to make sure .32 backporting for imx51 kernels is documented somewhere (c/o) [13:05] New Topic: asac, ogra, persia to make sure .32 backporting for imx51 kernels is documented somewhere (c/o) [13:05] We failed on this one again. [13:05] what was that about? (probably needs to be carried forward) [13:05] * ogra didnt do anything here [13:06] asac, that was about getting the non arch specific features ported to the .31 kernel [13:06] is that about user space? [13:06] asac: ogra: let's get together about 9:00 UTC tomorrow and do this. [13:06] so we have all distro features available [13:06] asac, nope [13:06] hmm. shouldnt we get cooloney_ on board too then? [13:06] about aufs, apparmor and friends [13:06] We were supposed to give cooloney_ a report :) [13:06] right [13:06] * ericm_ waves to all [13:06] So yeah, tomorrow work for you two? [13:07] hey ericm_, did we get a 32 drop from Marvell? [13:07] persia, 1h later ? [13:07] OK. [13:07] great [13:07] NCommander, yes - I'm working on the rebase [13:07] ok [13:07] we can try [13:07] hopefully to get a working kernel in these days [13:08] would be good to have both new kernels there for A2 [13:08] ericm_, where are the base Marvell branches? I think we may have another thumb mode kernel bug (I sent you an email about it) [13:08] since they will need heavy testing [13:08] NCommander, yes I've got that email - the branch is on kernel.ubuntu.com [13:08] let me find the exact URL [13:09] ogra: persia: sent an invite for tomorrow (in case you care) [13:09] thanks [13:09] http://kernel.ubuntu.com/git?p=marvell/dove-kernel/.git;a=shortlog;h=refs/heads/marvell-dove-2.6.32.2 [13:09] LINK received: http://kernel.ubuntu.com/git?p=marvell/dove-kernel/.git;a=shortlog;h=refs/heads/marvell-dove-2.6.32.2 [13:09] yes. from whati understood cooloney_ will try to get the fsl kernel done this week [13:09] asac: yeah, [13:09] i am working on this [13:09] ericm_, awesome. I'll talk to you more about the issues outside this meeting. [13:09] asac, hopefully me too [13:09] NCommander, no problem [13:10] [topic] Current Items for Lucid Alpha 2 [13:10] New Topic: Current Items for Lucid Alpha 2 [13:10] [link] http://piware.de/workitems/mobile/lucid-alpha2/report.html [13:10] LINK received: http://piware.de/workitems/mobile/lucid-alpha2/report.html [13:10] we have a big backlog ... [13:10] asac, Christmas holidays unfortunately do that :-/ [13:10] yeah [13:10] so part of the backlog is definitly me [13:11] me too [13:11] Any objection if we just run through each Alpha 2 spec individually? [13:11] thats the nature of the items i have ... most are items that are scheduled to happen at alpha-2 [13:11] like the thumb spec etc. [13:11] but ... would be great if everyone could check his spec and see if there are work items that either are DONE or can be POSTPONED [13:11] but we have until monday ... [13:12] so a good bunch should be affordable [13:12] We should have working alternates for Alpha2, although the dove alternate currently seems to be semi-foobar during kernel installation [13:13] is the test requirement fulfilled already ` [13:13] There was an image on antimony that was preventing alternate images for ports spinning. This has been resolved [13:13] ogra, which test requirements? ISO testing? [13:13] iirc that is supposed to have clearified the community testing first [13:14] at least thats what i was told at UDS [13:14] i.e. we will only do it if we have enough community testing since we dont have the resources in the team [13:15] i would suggest to do it... and see how well the testing goes [13:15] * ogra definately doesnt have additional 6h per image to invest [13:15] of coures not officially support it until we have the resources [13:15] we dont have them *now* [13:15] and the desktop images will suffer through pulling time off them [13:15] s/them/their testing/ [13:16] which we definately have to do [13:16] but from the technical side, what is missing? [13:16] alternate testing takes at least 3x as much time [13:16] NCommander: ? [13:16] [topic] Standing Items [13:16] New Topic: Standing Items [13:16] [link] http://piware.de/workitems/mobile/lucid/report.html [13:16] LINK received: http://piware.de/workitems/mobile/lucid/report.html [13:16] [topic] ARM Image Status [13:16] New Topic: ARM Image Status [13:17] ?? [13:17] NCommander: whats going on? [13:17] oh [13:17] bugger [13:17] * NCommander goes to drink more coffee [13:17] asac, on the technical side, not too much. the d-cd script for dove have been fixed, so now our alternates boot [13:17] NCommander already talked about the alternate status. [13:17] ok [13:18] NCommander, what about the ppp package issues ? [13:18] we fixed that a month ago ;) [13:18] or two? [13:18] Live images have been mostly built, although today's were hit with hplib version skew. [13:18] ogra, the fix was deploy to antimony just before Christmas break [13:18] asac, and the new packages are backported and installed on the builder ? [13:18] yes [13:18] NCommander, ah, thanks [13:18] persia: Was that just a delay with NEW or something else? [13:18] ok ... so to finish this alternate image topic. [13:18] i know when you fixed it ... just didnt know when it went into hardy [13:19] I thought it was just a build-time delay between arch:all and arch:any === fader|away is now known as fader_ [13:19] ogra, its in hardy-cat, I don't believe we did an SRU for it [13:19] can we agree that we have all the bits in place ... and that we can do manual image runs to ensure that they work? [13:19] asac, +1 [13:19] but we dont enable them until we have a) more builders ... and b) a community testing plan? [13:19] asac, we can ... and i'd be happy to test them, juct not during alpha testing in general [13:19] asac, the images are built on antimony and not on an armel box, so an alternate rebuild is trivial [13:19] right, building isnt an issue [13:20] ok so a) can be scratchd [13:20] asac, I'd say we provide them as a best effort, but I'd lthem to at least have a semi-good chance of working [13:20] so cant we keep them being produced, but just not supported? [13:20] they build since jaunty :) [13:20] more or less functional though [13:20] ogra, imx51 ones maybe, dove just got their first working ones [13:20] yeah, imx51 indeed [13:21] StevenK: You're right: it was NEW. [13:21] persia: Right, skew due to NEW I can deal with. [13:22] so [13:22] go onto ARM image status? [13:22] I thought we were talking about ARM image status. [13:22] wait a bit [13:22] * ogra didnt do any test install, but the build logs for imx51 look perfect [13:22] wanted to check a few others. [13:23] JamieBennett: do you have a way forward for figuring out where the time is lost in the debconf-communicate thing? [13:23] ogra: livefs builds failed today (libmpmud0 NEW) [13:23] (casper speedup) [13:23] asac: Yes, 3 actually [13:23] But one is the obvious choice [13:23] persia, didnt look today yet, just returned from the dentist and will lay down after the meeting again [13:24] ok cool. thats on track then [13:24] persia, but nothing that wouldnt be solved in general ... its not arch specific [13:24] plars: efficient instlal testing ... when will we get the all-pairs generated? [13:24] ogra: Right. Same happened for powerpc. Anyway, I'll be glad to give this back to you :) [13:24] :) [13:24] the test pairs are generated and documented in the wiki, I just need to write the detail for them on the qa testplan wiki [13:24] then we can create the virtual milestones and link them [13:25] cool [13:25] so when can we start doing all-pairs testing? [13:25] asac: good target would be somewhere after A2 at the soonest [13:25] the milestones should exist between milestone images [13:26] but A2 is even pretty early to focus *too* hard on it [13:26] ok great. [13:26] doesn't hurt though [13:26] so we assume that paramaters == questions asked during instlal? [13:27] thought it could also be things like: "what install media type" ... "what network connection" etc. [13:27] though testing that might be tricky [13:27] essentially, or could be boot screen options also (once supported), network connection during install, partitioning selection, etc [13:28] asac: for purposes of this type of testing, the network connected or disconnected during install is really what we want to focus on [13:28] ok. lets start with what you have now. we can extend later [13:28] since problems have been exhibited there before [13:28] plars: did you manually generate the all-pairs or do you use a script? [13:28] asac: right, we can certainly extend it all if needs be [13:28] if you have a script that would be great to post on wiki so we can rerun it if we have more paramaters we want to pair [13:28] the pairs were generated programatically, but had to be translated manually (easy) into which items that corresponded with [13:29] could you post the tool you used to generate it there? [13:29] ogra: uboot spec is on track for alpha-2 until we know its not on track? [13:29] :-P [13:29] I think it's linked from the bp wiki page, but I'll check to make sure [13:30] asac, yeah ... will be done latest on the weekend [13:30] will get 100% of my focus as soon as i feel better [13:30] ok. [13:30] * asac sends a grain of good feeling to ogra [13:30] :) [13:31] anything else we want to bring up for Alpha 2? [13:31] i already am better ... just that anaesthesia going away leaves me with massive pain [13:31] asac: we have issues with 2D launcher MIR's. We need to convince reviews that upstream will sort out what they call 'minor issues' or provide patches ourself to speed up the process (also two MIR's are unassigned) [13:31] (and i'm not allowed to put painkillers on top) [13:31] JamieBennett: ok. thanks for letting me know. lets talk about that after meeting [13:32] ok [13:32] ok the other specs have a backlog as previously pointed out: [13:32] thumb -> work items are review items to happen at alpha-2 stage [13:32] lightweight browser -> took a while to get chromium working, but now we have progress again [13:33] when will we see it in the archive ? [13:33] suspend-resume -> reduced set of work items (most was moved to alpha-3) should be doable for alpha-2 [13:33] chromium is GREAT [13:33] I'd like to see a debian/copyright I'm happy with for Chromium, but that is A LOT of work [13:34] asac, did we have a working ff build now? [13:34] ogra: i am working on license documentation ... tough task, but progress. i hope we get that to a stage that StevenK is happy to accept it [13:34] bribe him [13:34] dmart: the patch will get uploaded with .7 [13:34] Needs to be a big bribe. That's almost megabytes of licenses. [13:34] which is happening ... erm ... now ;) [13:34] * ogra heard rubber boats go well in east australia atm [13:34] oh, that was mean, sorry [13:34] persia: i have a tool to generate dep5 format copyrigh tnow [13:35] ogra: Hm? [13:35] asac: Yeah, but still :) [13:35] with whitelisting etc. stuff will get down to a reasoanble amount of unknown stuff [13:35] persia: yes. but thats StevenK's main job then ;) [13:35] now that didrocks has started :-P [13:35] ok [13:35] we can move on [13:36] oh ... lib-test ... probably will be late [13:36] not too scary as long as it happens soon after alpha-2 [13:36] Maybe it's worth re-milestoning those then. [13:36] persia: its tricky the work item tracker needs a different approach [13:36] Hrm. [13:36] so for split up blueprints we target the next delivery milestone [13:36] and then move ahead [13:37] So, do I need to repeat the stuff about the ARM image status, or is that done? [13:37] otherwise the items we want to see done by alpha-2 wont show up here. [13:37] persia: i think that sank ... maybe repeat ;) [13:37] 14:16 < NCommander> [topic] ARM Image Status [13:37] OK. [13:38] So, ports alternates just got fixed a few hours back (some issue with confusion in a cron job) [13:38] * ogra just repeats imx51 looks good apart from general non armel related breakage [13:38] As a result, we should start seeing alternate images again soon. [13:38] persia, d-cd didn't take well to lpia being rm'ed [13:38] NCommander: Yeah, but I wasn't getting into details :) [13:38] (desktop that is) [13:39] Live images have been OK for a while, but the livefs builds failed today due to NEW delay (sorted for tomorrow). [13:39] NCommander, how about dove desktop ? [13:39] ogra, they're working aside from the usual livefs breakages [13:39] whats "usual" ? [13:39] ogra, i.e., somethng that would also break imx51 [13:40] ogra, I guess I should say, no dove specific breakage known at this time [13:40] and amd64 ? [13:40] or x86 [13:40] great :) [13:40] as long as its not armel related i dont care :P [13:40] ogra, I'm testing images daily at this point as a lead into alpha2. Rather not miss another milestone with dove [13:41] you know that they can become shaky this week ... dont count to much on installability [13:41] everyone tries to get features for A2 ready [13:41] the archive will be out of sync often [13:41] * StevenK is planning to break armel images this week and get them building UNE [13:41] ogra, I rather catch failure early than during A2 ISO testing. [13:41] StevenK, need a hand? [13:41] :-) [13:41] Oh, and the last thing I had to say about images is that I'm glad people are returning from holiday so that others are watching them :) [13:41] right, just make sure to tell them apart from feature development [13:42] StevenK: how about keeping keeping the desktop images until we have a working une image? at least we have a image at alpha-2 then ;) [13:42] multi package features are likely to trash stuff, especially this week with the last minute uploads [13:42] ogra, we still do have some ubiquity weirdness with manual partitioning on dove. That might slide to Alpha 3, I'm grinding my wheels on that one. [13:42] asac: I'm happy enough to do that, and davidm agrees with you. [13:42] asac: As long as we have all the packages built correctly, why not change the seeds? [13:42] StevenK: ok cool. thx! [13:42] NCommander, thats just a bug we can release note ... [13:43] persia: risk minmization [13:43] you never know [13:43] its an alpha after all, not a final :) [13:43] you can just enable a new seed [13:43] and if that work we disable the old seed ;) [13:43] StevenK, is the actual desktop image on dove going to be UNE-2D, or are we going to simply build desktop and ubuntu-netbook-edition-2d ARM [13:43] or asac beat me to that question [13:43] new seed? I thought the plan was just arch-specific stuff to existing seeds. [13:43] NCommander: At first, both, and then the former only [13:43] NCommander: UNE-2D is our main target [13:44] persia: yes. new seed for armel [13:44] not overal [13:44] asac, StevenK, TBH, I rather just disable the desktop task on the image build system, and leave alternates for people who want them [13:44] NCommander: that doesnt conflict with what we say [13:44] asac: It wasn't going to be a new seed? [13:44] StevenK: your decision ;) [13:44] * ogra thoughgt it was an on-top seed [13:44] If we can build both concurrently, I say thats the way to do it, then just focus on UNE [13:44] i just think having desktop images produced until we have the new images would be great [13:44] It will not be a new seed. There. [13:45] and reduces risk and burn out syndrom potential in case something goes bad [13:45] platform -> netbook is hard enough; I don't want to deal with platform -> netbook -> armel-stuff [13:45] \o/ reduced number of seeds [13:45] asac, I rather just keep the desktop image around like we build kubuntu and xubuntu armel [13:45] NCommander, ask IS if you may :P [13:46] Maybe turn off the live images to save some time on the livefs builder [13:46] NCommander: cdimage space is still a going concern [13:46] yeah [13:46] a huge concern [13:46] (Since it always is) [13:46] * StevenK gives the ogra the secret cdimage high five [13:46] * ogra grins :) [13:46] one which will never go away due to images go up, not down. I realize its a concern, but we're simply going to have the same issue when we get a new SoC, or a new image type [13:47] NCommander, you will always have the ubuntu-desktop task you can install [13:47] so is there anything to discuss? from what i understand we make a seemless transition to the new seed, by keeping desktop images enabled until we have a first working UNE image for armel with 2D launcher, right? [13:47] even more if we get a new SoC [13:47] yeah [13:47] ok [13:47] then we all know where we are heading ;) [13:47] Are we going to transition people from desktop to UNE on the upgrade usecase? [13:48] * ogra doesnt think so [13:48] NCommander: unlikely [13:48] Do we actually care about the karmic->lucid upgrade for dove and imx51? [13:48] It wouldn't be ideal to force a transitoin. [13:48] NCommander, we should test them [13:48] desktop packages are still there and in main .... so users just ride the general support wave [13:48] Supporting upgrades is nice, if there is commonly supported hardware. [13:48] persia, hence the question. [13:49] would be good to have a metapackage to provide them the packages to update to the all the new UNE stuff, but forcing it on them would probably get some complaining [13:49] Anyway, anyone have anything else to bring up on ARM Image Status? [13:49] plars, we have to have a task anyway [13:49] yep [13:49] ok so i think we can move on [13:49] NCommander: ^ [13:50] [topic] Any Other Business [13:50] New Topic: Any Other Business [13:51] Chromium was mentioned before. I suggest it should be adopted in main [13:51] FTBFS's [13:52] mok0: thats the plan [13:52] asac, I saw you assigned a bunch :-) [13:52] depends on various factors ;) [13:52] asac: ah. Great! [13:52] yep ... so i went through all main FTBFS and assigned them to either ncommander or dyfet [13:52] and both subscribed to both [13:53] dont hesitate to tell me if there are FTBFS you get stuck with [13:53] ;) [13:53] so we can unblock them somehow [13:53] asac, thanks a lot for apex btw [13:53] for univeres i am through half of the list [13:53] with assignments [13:53] asac, thanks for the ocaml upload. Upstream is looking at the bug now as well [13:53] will do the rest [13:53] next ... [13:54] well, we used to handle universe as a nice to have [13:54] i think its important to get all armel-only build failures fixed. of course main has higher prio [13:54] but universe is also important [13:54] because we are the only ones with hardware to actually work on those [13:54] do you plan to change that since you are actively assigning stuff ? [13:54] Do we have a general goal to when to have main armel-only FTBFS free? [13:54] thats what we used to have [13:54] seems asac wants to widen that goal [13:54] ogra: i assign them because main is almost fixed [13:54] I think universe is all the more important considering the spec to remove binaries for anything that FTBFS. [13:55] its still a lower prio, but its more than a nice to have [13:55] So for *this* release, it's more important than usual to demonstrate that something *can* build. [13:55] at least the armel-only build failures [13:55] sorry [13:55] I meant an Alpha 2 main-free armel-only FBFS [13:55] but we give MOTU tools in their hands to work on them [13:55] right. its also more important in the light of the new toolchain [13:55] Please fix libtool then as it's causing other FTBFS. [13:55] NCommander: would be great. [13:55] and i'd like to see MOTU getting more knowledge here [13:55] yes. libtool has highest prio [13:55] i have put that on release team radar too [13:56] and assigned NCommander to it ;) [13:56] if you assign them to us MOTU wont care at all [13:56] asac, I was going to ask for it actually :-) [13:56] ogra: i dont see that realistic for now [13:56] they dont have hardware [13:56] thats why i wrote all these tools [13:56] ogra: Without access to hardware, there isn't much we can do. [13:56] dyfet, can you make my shell reappear, or should I work off jocote? [13:56] and blogged about it ... and set up wiki pages [13:56] ScottK, you can build in chroots to fix FTBFS [13:57] ogra: well. so most i assigned now are _old_ build failures [13:57] seems noone picked them up [13:57] but yes, we should make a new blog post etc. [13:57] http://ograblog.wordpress.com/2009/07/18/juggling-your-arms-in-karmic-and-no-more-excuses/ [13:57] LINK received: http://ograblog.wordpress.com/2009/07/18/juggling-your-arms-in-karmic-and-no-more-excuses/ [13:57] ncommander: shell? you mean on my arm? [13:57] dyfet, yeah [13:57] * ogra wonders if anyone reads his posts on planet :P [13:57] So who wants to blog to planet? [13:57] * NCommander has a layer of dust on his blog :-/ [13:58] two minute warning [13:58] so who has a blog at all? ;) [13:58] and who is on planet? [13:58] I'm on planet [13:58] both combined probably reduces the set of candidates ;) [13:58] (both Ubuntu & Debian) [13:58] i am on planet too [13:58] * ogra too [13:58] ok so we have three [13:58] and i regulary blog about my armel tools and achievements [13:58] Or heating houses [13:59] lets discuss communication offline. [13:59] heh, yeah :) [13:59] [action] ogra, asac, NCommander to blog on planet about ARM work [13:59] ACTION received: ogra, asac, NCommander to blog on planet about ARM work [13:59] right, time is up [13:59] :-) [13:59] anything else quickly? [14:00] #endmeeting [14:00] Meeting finished at 07:59. [14:00] argh [14:00] * NCommander was a minute early [14:00] NCommander: dyfet: try to work together on the FTBFS ;) [14:00] [action] ^^^ :) [14:01] NCommander: also ... do you want me to monitor that list for you and do assignments in future or will both of you coordinate that together? [14:01] also consider me part of that FTBFS effort ;) [14:02] thanks all! [14:04] dmart: http://pastebin.com/f10c0fe94 [14:04] thats hte list of packages not yet touched [14:04] i didnt exclude "arch all" packages yet [14:05] asac: Is that different from http://qa.ubuntuwire.com/multidistrotools/unchanged/unchanged_since_karmic ? [14:05] so probably its a bit less packages not yet touched [14:05] not sure :) [14:05] persia: my list is just main [14:05] OK. [14:06] but good to know === txwikinger2 is now known as txwikinger === robbiew_ is now known as robbiew [14:59] \o [15:02] o/ [15:02] mdz, cjwatson? [15:03] pitti: hi [15:03] #startmeeting [15:03] Meeting started at 09:03. The chair is mdz. [15:03] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [15:03] [link] https://wiki.canonical.com/UbuntuPlatform/WritingObjectives [15:03] LINK received: https://wiki.canonical.com/UbuntuPlatform/WritingObjectives [15:03] hello [15:03] er [15:03] [link] https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda [15:03] LINK received: https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda [15:04] one day the X clipboard will work as we expect... [15:04] I see cjwatson, pitti, kees [15:04] both of them? :-) [15:05] sabdfl is on holiday [15:05] I don't know about Keybuk [15:05] he was online yesterday [15:05] pitti: I thought there was only one clipboard, plus the selection buffer [15:05] ScottK: are you here? (your agenda item is pretty much the only one that we have) [15:06] I'm heree [15:06] here even [15:06] ScottK: happy new year! [15:06] [topic] Review action items from previous meeting [15:06] New Topic: Review action items from previous meeting [15:06] Happy New Year. [15:06] mdz to drive election for DMB, based on existing members of TB and MC [15:06] voting is in progress now [15:06] * persia very much appreciated the second call for votes: something rarely seen in these polls. [15:06] 77 votes cast out of 146 eligible voters [15:07] the vote will end in 13 days, one week from Monday [15:07] persia: it occurred to me in doing this that there is not a lot of guidance available to our governance teams as to how to conduct elections [15:07] different teams have done it in different ways [15:07] perhaps something for the CC to consider [15:07] next action: [15:08] persia to ask CC to make DMB an admin of ~universe-contributors, as part of the DMB/MC merge [15:08] I saw the request happen [15:08] persia: have you received any response? [15:08] I haven't seen any follow-up. I'm planning to ask at the CC meeting on the 20th if I haven't seen anything by then (I'm not confident I'll be awake for today's meeting). [15:09] Err, 19th. [15:09] persia: perhaps someone who will be awake could proxy for you at today's meeting? that would be better than waiting 2 weeks [15:09] mdz: As far as how to do elections, I think the move to use CIVS is a huge step forward for the project. [15:09] mdz: I'll seek someone for that. [15:09] persia: when is it? [15:10] 21 UTC [15:10] ScottK: yes, but it's only one part of the process. I had to make it up as I went along in terms of soliciting and confirming nominations, establishing who was eligible, how long the vote should be, and so on [15:10] persia: so somebody in the US would be best. kees? [15:11] mdz: I think it needs to be someone on MC: likely nixternal or nhandler [15:11] mdz: Certainly. I think it makes sense to have it documented and some standardization. [15:11] persia: ok, I'll leave it with you then [15:11] [topic] MOTU direction (ScottK, cjwatson) [15:11] New Topic: MOTU direction (ScottK, cjwatson) [15:11] I didn't put this on the agenda for today ... [15:12] cjwatson: ? [15:12] It was carry-over from the last meeting. [15:12] I carried it over from the last meeting, since we didn't get to it [15:12] Ah. [15:12] I just didn't want to drop it [15:12] as far as I'm concerned this is a "guilt item" [15:12] we're looking for a progress check [15:12] unless ScottK has done more than I have ... [15:12] any progress since 22 december? [15:13] I have been on holiday since 22 Dec, mostly [15:13] what needs to happen next? do you two need any help? [15:13] Well we do have this action and persia has helpfully drafted some material, but cjwatson and I have not had a chance to discuss it. [15:13] So unless he's done something I'm not aware of, I think it needs to be pushed. [15:13] ScottK: do you have the URL for persia's draft? [15:13] There isn't a URL. [15:13] cjwatson: He emailed it to you and me. [15:13] oh, ok, I'll dig that out [15:14] he mentioned that he updated: [15:14] https://wiki.ubuntu.com/UbuntuDevelopers [15:14] https://wiki.ubuntu.com/DeveloperMembershipBoard [15:14] https://wiki.ubuntu.com/DeveloperMembershipBoard/ApplicationProcess [15:14] https://wiki.ubuntu.com/MOTU [15:14] https://wiki.ubuntu.com/MOTU/Council [15:14] I don't know if that's the same thing ScottK is talking about [15:14] No. [15:14] No, that was what I did as a result of the questions about DMB/MC from last meeting. [15:14] I have the gobby dump from UDS which AIUI needs to be written up properly and presented to the TB. [15:15] Yes, and persia to a stab at writing it up for us. [15:15] Message-ID: <9bd2f8971001031949u15ba5fc4k20cb9abe0bacff8@mail.gmail.com> [15:16] I'm going to go ahead and dump that into the wiki, and work from there [15:17] I don't think there's anything else for this meeting, we just need to not forget it [15:17] Agreed. [15:17] I'll try to have a bit more progress for next time [15:18] ok [15:18] actions? [15:18] just carry over [15:19] cjwatson to write up gobby notes from UDS? [15:19] [action] ScottK+cjwatson to pull joint fingers out and write up proposal [15:19] I think it's just work we know we have to do. [15:19] [action] ScottK+cjwatson to pull joint fingers out and write up proposal [15:19] ACTION received: ScottK+cjwatson to pull joint fingers out and write up proposal [15:19] Sounds good. [15:19] [topic] AOB [15:19] New Topic: AOB [15:19] anything else? [15:20] the next meeting will be the constituting one with the new board, right? [15:21] so I guess meeting lead rotation, meeting time, etc. should be discussed in that meeting [15:21] Should not a date, time, and lead for that meeting be set at this one though? [15:22] we might as well just use the same time, and let the new board decide on what's convenient for them [15:22] I'm not sure we can know a lead before knowing who's going to be on the board :) [15:22] we could select 3 ranked options, and since it is a 7/9 election we could be guaranteed to get one right ;-) [15:22] I was thinking someone could volunteer to chair, and if they didn't happen to be on the board, act as a facilitator for that meeting alone. [15:23] I can do that [15:23] I think the "old" board should turn up at the next meeting regardless, to help with continuity [15:23] at least some of us [15:23] I will be traveling to a time zone which would make participation difficult [15:24] I'm happy to join that meeting [15:24] [agreed] cjwatson and pitti will participate in the next DMB meeting regardless of the election outcome [15:24] AGREED received: cjwatson and pitti will participate in the next DMB meeting regardless of the election outcome [15:24] you can work out what to do about a chair between yourselves ;-) [15:24] any other business? [15:25] please remember to vote if you haven't already [15:25] ok, thanks all [15:25] #endmeeting [15:25] Meeting finished at 09:25. [15:25] thanks all === \vish is now known as mac_v === mac_v is now known as \vish [17:03] * apw zones in [17:03] * cking_ is here [17:03] * ogasawara waves [17:03] * smb is there [17:03] * manjo waves [17:03] bjf: yo [17:03] Roll Call [17:04] * apw appears again [17:04] #startmeeting [17:04] Meeting started at 11:04. The chair is bjf. [17:04] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [17:04] [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting [17:04] [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid [17:04] NOTE: '..' indicates that you are finished with your input. [17:04] [TOPIC] Open Action Item: amitk to meet with keybuk on automated boot tests [17:04] LINK received: https://wiki.ubuntu.com/KernelTeam/Meeting [17:04] LINK received: https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid [17:04] New Topic: Open Action Item: amitk to meet with keybuk on automated boot tests [17:04] * jjohansen fades in [17:05] amitk, you are up [17:05] I think he's on holiday? [17:05] nm, that was yesterday [17:05] we'll skip him for now [17:06] [TOPIC] Lucid Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs [17:06] New Topic: Lucid Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs [17:06] Release Meeting Bugs (1 bug, 4 blueprints) - https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid [17:06] Alpha 2 Milestoned Bugs (23 bugs) - https://bugs.edge.launchpad.net/ubuntu/lucid/+bugs?field.milestone%3Alist=21444 [17:06] * 3 linux kernel bugs (all In Progress) - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux/+bugs?field.milestone%3Alist=21444 [17:06] * 1 linux-fsl-imx51 bugs (tracked in release meeting) - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux-fsl-imx51/+bugs?field.milestone%3Alist=21444 [17:06] * 0 linux-ec2 bug - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux-ec2/+bugs?field.milestone%3Alist=21444 [17:06] * 0 linux-mvl-dove bugs - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux-mvl-dove/+bugs?field.milestone%3Alist=21444 [17:06] * Release Targeted Bugs (88 bugs) https://bugs.edge.launchpad.net/ubuntu/lucid/+bugs [17:06] * 8 linux kernel bugs - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux [17:06] * 3 linux-fsl-imx51 bugs - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux-fsl-imx51 [17:06] * 1 linux-ec2 bug - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux-ec2 [17:06] * 1 linux-mvl-dove bug - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux-mvl-dove [17:06] .. [17:06] [TOPIC] Lucid Release Status: Milestoned Features [17:06] New Topic: Lucid Release Status: Milestoned Features [17:06] Milestoned Features - https://edge.launchpad.net/ubuntu/+milestone/ubuntu-10.04 [17:07] nothing kernel specific listed there [17:07] .. [17:07] any questions on any of this? is that pgraner guy around? [17:07] bjf: sorry I'm here [17:07] bjf: expenses are due today ... :-) [17:08] bjf: no questions [17:08] pgraner, thanks, moving on ... [17:08] [TOPIC] Blueprints: kernel-lucid-bug-handling (ogasawara) [17:08] New Topic: Blueprints: kernel-lucid-bug-handling (ogasawara) [17:08] bjf: nothing new to update [17:08] .. [17:08] [TOPIC] Blueprints: kernel-lucid-review-of-ubuntu-delta (apw) [17:08] [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-review-of-ubuntu-delta [17:08] New Topic: Blueprints: kernel-lucid-review-of-ubuntu-delta (apw) [17:08] LINK received: https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-review-of-ubuntu-delta [17:09] no change since last meeting. mostly complete [17:09] .. [17:09] [TOPIC] Blueprints: kernel-lucid-kernel-config-review (apw) [17:09] [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kernel-config-review [17:09] New Topic: Blueprints: kernel-lucid-kernel-config-review (apw) [17:09] LINK received: https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kernel-config-review [17:09] config checker is now in and checking things [17:09] we have a few config changes coming down the pipe from other teams which are going in [17:09] otherwise quiet [17:09] .. [17:10] [TOPIC] Blueprints: kernel-lucid-kms (sconklin) [17:10] [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kms [17:10] New Topic: Blueprints: kernel-lucid-kms (sconklin) [17:10] LINK received: https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kms [17:10] i had a poke about with a nouveau drop which may be compatible with our tree. trying to acertain if it would be good as a default [17:11] the main drop is definatly a 'lbm' style component [17:11] .. [17:11] why? [17:11] why not in the main package [17:11] sconklin, New Topic: Blueprints: kernel-lucid-kms (sconklin) [17:11] cause it has dependancies on updating the whole of drm [17:12] no, four commits thats all [17:12] those 4 commits are big, and those commits do not apply without other patches [17:12] ok then [17:12] the version which was applied resonably well to .32 was an older nouveau drop [17:13] which is what i was referring to previously. not had a chance to test it yet [17:13] .. [17:13] sconklin, you have anything to add? [17:13] no [17:13] .. [17:13] [TOPIC] Blueprints: kernel-lucid-suspend-resume (manjo) [17:13] [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-suspend-resume [17:13] New Topic: Blueprints: kernel-lucid-suspend-resume (manjo) [17:13] LINK received: https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-suspend-resume [17:14] no change there since last meeting [17:14] .. [17:14] [TOPIC] Blueprints: kernel-lucid-apparmor-development (jjohansen) [17:14] [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-apparmor-development [17:14] New Topic: Blueprints: kernel-lucid-apparmor-development (jjohansen) [17:14] LINK received: https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-apparmor-development [17:14] Upstream AppArmor update incoming today, just cleaning up some commit messages. I still need to file the compiler bug that was tripping me up [17:14] The kernel side of policy optimizations is done, I should have user side dfa [17:14] minimization in by the end of the week. If there is time the table packing [17:14] part of optimization can be done for alpha3 [17:15] jjohansen, ok will look for it tommorrow [17:15] .. [17:15] [TOPIC] Blueprints: kernel-lucid-boot-performance (apw, csurbhi) [17:15] [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-boot-performance [17:15] New Topic: Blueprints: kernel-lucid-boot-performance (apw, csurbhi) [17:15] LINK received: https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-boot-performance [17:15] 2.6.32.2 brought in some regressions in performance [17:15] (boot performance) those turn out to be present already but triggered more often in this combination [17:16] i think i have this nailed, an interaction between acpi battery and hpet [17:16] am testing a couple of patches to sort it out now [17:16] this may give us another 0.05 as a bonus [17:16] .. [17:16] [TOPIC] Other Release Tasks: Lucid Audio Support (bjf) [17:16] New Topic: Other Release Tasks: Lucid Audio Support (bjf) [17:17] I have my "crack-of-the-day" builds going. I've sent out email to a few of the alsa folks letting them know [17:17] about them. [17:17] .. [17:17] when might they be announced publically ? [17:17] apw, I guess I can do that any time [17:18] apw, I'll try to get an email out today [17:18] .. [17:18] [TOPIC] Other Release Tasks: Lucid Better Power Mgt (amitk) [17:18] New Topic: Other Release Tasks: Lucid Better Power Mgt (amitk) [17:18] skipping [17:18] .. [17:18] [TOPIC] Other Release Tasks: EC2 Lucid Kernel Status (jjohansen) [17:18] New Topic: Other Release Tasks: EC2 Lucid Kernel Status (jjohansen) [17:18] I am working on an EC2 update that should land today [17:19] jj is that against the ec2 branch in lucid? [17:19] yeah [17:19] just pulling in suses updates to the patches [17:19] Dapper: 2.6.15-55.81 (security) [17:19] Hardy: 2.6.24-26.64 (security) [17:19] -LBM: 2.6.24-26.35 (proposed)[26] 0/ 1 verifications done [17:19] -LUM: 2.6.24-26.44 (proposed)[26] 0/ 1 verifications done [17:19] Intrepid: 2.6.27-16.44 (security) [17:19] Jaunty: 2.6.28-17.58 (security) [17:19] Karmic: 2.6.31-17.54 (proposed)[26] 9/19 verifications done [17:19] -LBM: 2.6.31-17.19 (proposed)[26] 0/ 1 verifications done [17:19] -fsl-imx51: 2.6.31-107.18 (proposed)[18] 16/34 verifications done [17:19] -mvl-dove: 2.6.31-210.21 (proposed)[15] 16/35 verifications done [17:19] Proposed kernels could move to updates soon. Trying to get some feedback [17:19] on the arm kernels to preferably move them together with the main kernel. [17:19] The next upstream stable (2.6.31.10, 2.6.32.3) are coming up. [17:19] oops [17:19] :) [17:19] ok i'll hold the upload for now ... [17:20] .. [17:20] [TOPIC] Status: Lucid (apw) [17:20] New Topic: Status: Lucid (apw) [17:21] i've recently applied 2.6.32.2 but had regressions. those look resolved. would be uploading today, but the compilers are building right now [17:21] so will have to wait for those to complete. [17:21] REMINDER: you want anything in Alpha-2 we need it in and uploaded by monday at the very latest [17:21] if its going to be monday make sure i know as i want to upload friday [17:21] with people in the air etc. [17:21] .. [17:22] [TOPIC] Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (gnarl/smb) [17:22] New Topic: Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (gnarl/smb) [17:22] I think we got this already :-) [17:22] a [17:22] as above [17:22] anything to add? [17:22] yeah, somehow return key has a live of its own [17:22] nope [17:22] .. [17:23] [TOPIC] Incoming Bugs: Regressions (ogasawara) [17:23] New Topic: Incoming Bugs: Regressions (ogasawara) [17:23] Current regression stats (broken down by release): [17:23] == regression-potential (up 10) == [17:23] 26 lucid bugs [17:23] * https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-potential+lucid&field.tags_combinator=ALL [17:23] == regression-update (up 2)== [17:23] 7 karmic bugs [17:23] * https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-update+karmic&field.tags_combinator=ALL [17:23] 5 jaunty bugs [17:23] * https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-update+jaunty&field.tags_combinator=ALL [17:23] 2 intrepid bugs [17:23] * https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-update+intrepid&field.tags_combinator=ALL [17:23] 1 hardy bug [17:23] * https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-update+hardy&field.tags_combinator=ALL [17:23] == regression-release (down 2)== [17:23] 58 karmic bugs [17:23] * https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-release+karmic&field.tags_combinator=ALL [17:23] 22 jaunty bugs [17:23] * https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-release+jaunty&field.tags_combinator=ALL [17:23] 12 intrepid bugs [17:23] * https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-release+intrepid&field.tags_combinator=ALL [17:23] 4 hardy bugs [17:23] * https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-release+hardy&field.tags_combinator=ALL [17:24] == regression-proposed (no change)== [17:24] 1 karmic bug [17:24] * https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-proposed+karmic&field.tags_combinator=ALL [17:24] .. [17:24] [TOPIC] Incoming Bugs: Bug day report (ogasawara) [17:24] New Topic: Incoming Bugs: Bug day report (ogasawara) [17:24] Due to the holiday, there wasn't much activity the previous bug day: [17:24] http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20091222.html [17:24] The next bug day should be next week but we'll be sprinting. I'll postpone it to Tues Jan 19. [17:24] LINK received: http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20091222.html [17:24] .. [17:24] [TOPIC] Open Discussion or Questions: Anyone have anything? [17:25] New Topic: Open Discussion or Questions: Anyone have anything? [17:25] Server team would like us to get a body looking at Bug #499785 [17:25] Launchpad bug 499785 in linux "nic-usb-modules should include asix" [Medium,Triaged] https://launchpad.net/bugs/499785 [17:25] jjohansen: I was going to send a patch for that shortly [17:25] ogasawara, can you get that on the list [17:25] ogasawara: nice, thanks [17:25] bjf: no meeting next week since we are sprinting? [17:26] Note: there will not be a meeting next week, the kernel team will be in London buried under snow. [17:26] pgraner, you beat me to it [17:26] :-) [17:26] heh in the airport burried ... [17:26] anything else? [17:26] thanks everyone [17:26] #endmeeting [17:26] Meeting finished at 11:26. [17:26] bjf thanks === \vish is now known as vish === fader_ is now known as fader|lunch [19:18] === zul_ is now known as uzl === uzl is now known as zul [19:25] hey folks, wasn't the EMEA meeting meant to start about 25 minutes ago? [19:25] alonswartz: according to my cal, 20:00, but it very well could be wrong [19:25] because it also says 22:00 for the CC, but our agenda says 21:00 [19:26] silly Google calendar is probably foobarring me, and possibly your too? [19:26] nixternal: according to the wiki page: The next meeting is scheduled for January 5th 2010, 19:00 UTC [19:26] hrmm [19:27] If you follow the link it translates into local time. That was 30 minutes ago. Strange. [19:27] right, but the google calendar for the meeting says 20:00 :/ [19:27] http://fridge.ubuntu.com/calendar [19:30] nixternal: the calendar doesn't seem in sync with the wiki page, oh well... so we start in 30 minutes ? [19:30] Alright, so there was a mistake and the meeting is still today but half an hour later than the schedule on the wiki site. === fader|lunch is now known as fader_ [19:41] the EMEA meeting will start at 21:00 [19:42] 21:00 UTC? [19:42] nope, 20:00 UTC [19:44] seems that there's a mistake on the wiki [19:44] anyway, the EMEA meeting will start at 20:00 UTC === zul_ is now known as zul === yofel_ is now known as yofel [20:02] yes, it seems there is [20:03] * popey pings forumsmatthew / phanatic / Seveas / stgraber / phanatic [20:03] pong [20:04] I'm here [20:04] pong [20:04] Apologies for getting the wiki wrong. I suspect that was my fault [20:05] stuff happens [20:05] shall we begin? [20:05] Go! [20:05] yes [20:06] ok, BlackZ you're up. Please introduce yourself [20:06] Hi all, my name is Lorenzo De Liso, I'm 19 years old, I'm Italian, and I live in Italy. I'm a security consultant (I work in a Italian datacenter). I use ubuntu since 3 years about, and I like it. I study informatic enginner on the university Federico II in Naples. I worked and I work again to some bugs, I help to translate ubuntu in Italian, I help in ubuntu's Italian forum, I translate the Italian ubuntu wiki and I help in #ubuntu-it. [20:08] -1. There's no information about your contributions on your wikipage, launcpad karma is low, indicating limited contributions. Testimonials added by yourself, which is very bad... [20:08] agreed -1 [20:09] Yeah, -1, I'd certainly like to see more contributions listed and testimonials added by those people who are listed [20:10] phanatic, ? [20:10] sorry, i was on the phone. -1 [20:10] ok, that's -4. BlackZ please make sure your wikipage is fully prepared next time :) [20:11] Ioneye seems to be missing [20:11] Shezif as well [20:11] LirazSiri, you're up [20:11] Hi everybody [20:11] * stgraber waves [20:11] I'm 28 years old, from Israel. A software engineer by day and open source enthusiast by night. [20:11] hey stgraber! [20:12] LirazSiri: we've spoken before haven't we [20:12] hi all [20:12] yep [20:12] As I recall we rejected your application last time [20:12] on the grounds that we wanted to see more contributions to core ubuntu itself? [20:12] yes, last time we said -1, considering contributions to TurnKey not to be contributions to Ubuntu [20:12] if my memory is right [20:12] hey guys [20:12] the endorsements are stronger now [20:13] You do have two testimonials this time. John's is pretty good. The other is helpful, if a little lukewarm. [20:13] I've been a contributing member to the news team for over a year now. Responsible for 5 sections [20:13] but the actual contributions haven't changed, have they? [20:14] They have evolved somewhat. TurnKey has gotten closer to Ubuntu. We've been collaborating with Ubuntu developers and discussing appliance development on the list. [20:14] I guess it is going to depend on whether we consider helping with the weekly newsletter sufficient community involvement for membership [20:14] I've seen that and that's really encouraging LirazSiri [20:14] And sabdfl also said positive words about turnkey [20:14] On the subject of TurnKey's relationship with Ubuntu, you can read the endorsements on Alon's wiki page [20:15] those testimonials emphasize on "hope to work closer with..." [20:16] which is what I'd like to see as well, a bit closer collaboration [20:16] forumsmatthew: you have in the past granted membership to members of the Ubuntu news team and I've been doing that for much longer than the 3 months of sustained contribution described in the membership criteria [20:16] LirazSiri, but never based on news contributions alone I believe [20:16] Every week, I maintain all the statistics, package and security updates, etc. [20:17] LirazSiri, how much time do you spend on that each week? [20:17] That depends on the week [20:17] After releases it can take longer [20:17] because there are lots and lots of updates [20:18] how about this week or last? [20:18] About an hour [20:18] wait, that's unfair due to christmas [20:18] on average [20:18] to be perfectly blunt, one hour per week is not much as a contribution [20:18] well I divide my time between that and other projects [20:19] other ubuntu projects? [20:19] and I realize turnkeylinux is your bigger contribution, but I'm not sure whether that actually 'counts' for us [20:19] personally I feel TurnKey is a much larger contribution to Ubuntu. As the sabdfl stated, it's a new kind of contribution we're pioneering, so it's a bit difficult to get endorsements [20:19] there isn't an established framework. [20:19] I hope you don't mind me dropping in, but TurnKey Linux a sort of LoCo for server appliances. Instead of helping introduce users to Ubuntu on a geographical basis, we help introduce users to Ubuntu by helping them quickly setup and deploy Ubuntu as a server platform. Through TurnKey, we have introduced tens of thousands of new users to Ubuntu as server platform (over 100,000 downloads). [20:20] I have downloaded turnkey [20:20] a couple of images [20:20] which ones? [20:20] that's about 60 hours total since you've started [20:20] an smb server and another [20:20] I certainly don't mind, alonswartz . What you are saying is helpful. [20:20] i cant recall [20:20] I booted them up and played, liked what I saw, and shut them down and deleted them [20:21] that's not to say I didnt like or enjoy the work you do [20:21] merely that I had no use for them [20:21] so i wouldn't hold tooooo much sway with 100000 downloads :) [20:21] do you see turnkey as a part of the Ubuntu community, an insider, or as a project that stands alongside Ubuntu? [20:21] that's still great, a lot of our users do that [20:21] sure, it's a great way to introduce ubuntu appliances to people [20:21] and i think thats valuable work [20:21] thanks! [20:22] dammit, I can't find the thread about TKL [20:22] in the same way that dell selling laptops running ubuntu is valuable work [20:22] popey, do you recall whether sabdfl said that we could consider contributions to TKL contributions to Ubuntu? [20:22] if I had more time I'd evaluate it properly [20:22] I can find the quote from the sadbfl if it helps [20:22] LirazSiri, it would [20:23] Note that we're also partnering up with Canonical to offer all TurnKey appliances through the new Ubuntu cloud initiative [20:23] things that stand along side are helpful, but not integral, that is, the main project may benefit from their existence, but won't necessarily cease to exist or be harmed if the project disappears [20:23] I'm looking for a balance [20:23] "Liraz, you are a valued member of the community, and that is true even if it takes a little while to build the case for Ubuntu membership. It takes time to establish yourself in something the scale of Ubuntu - especially if you are pioneering a new kind of contribution, which I think you are. If you were working mainly in an established area, there would be a network of folks who could immediately comment on your contribution. Since you [20:23] is what mark said [20:23] Ok I found the quote [20:23] popey, that got cut off at 'since yo' [20:24] let me cut and paste and paste the relevant part.. [20:24] ". Since you aren't, you need to build that network, and raise the profile of your work." [20:24] also... [20:24] one more thing, for no other external project or canonical partner do we consider contribusions to them contributions to ubuntu [20:24] "In principle, I think building Turnkey *could well* turn out to be a great contribution to Ubuntu. If the Turnkey folks contribute patches, share war stories about EC2, build common infrastructure, participate in UDS etc, then I would say we should recognise that contribution. " [20:24] ^^ from Mark [20:24] thanks popey [20:25] thanks, popey [20:25] * popey hugs gmail [20:25] where is that from? I found another quote [20:25] I didn't know Mark spoke about TurnKey twice... [20:25] so, based on that last sentence of Mark's comment, how much of that is happening [20:25] popey: I've never seen that last quote... ? [20:25] patches? infrastructure? UDS even? [20:27] I have seen discussion of Turnkey on the devel mailing list very recently, talking about webmail. [20:27] er, webmin [20:27] erk [20:27] webmin [20:27] popey: that discussion got started off talking about appliance development [20:27] heh [20:27] guys, I'm trying to copy paste but have trouble with my application so I'm going to restart it. Back in a jiffy [20:28] which was in reply to a previous thread regarding developing appliances as deb packages [20:28] sure, lets not get too bogged down in one specific discussion on -devel list [20:28] yeah, you clearly are doing that the correct way [20:29] the criteria for membership is 'significant and sustained' contribution to ubuntu [20:29] we has just released tklpatch, a tool to patch and create appliances [20:30] alonswartz, have you ever thought of using puppet to create appliances? [20:30] I'm keen for us to not spend the entire meeting on Turnkey (as we did last time) [20:30] popey, me too, I'm just waiting for liraz to return [20:30] ah, speak of the devil :) [20:30] Seveas: its not the best fit, but lets talk about that later (i agree with popey) [20:30] OK, hopefully this will work now [20:31] Liraz, you are a valued member of the community, and that is true even if it takes a little while to build the case for Ubuntu membership. It takes time to establish yourself in something the scale of Ubuntu - especially if you are pioneering a new kind of contribution, which I think you are. If you were working mainly in an established area, there would be a network of folks who could... [20:31] ...immediately comment on your contribution. Since you aren't, you need to build that network, and raise the profile of your work. [20:31] Others have gone before you in this. The IRC community now has folks devoted to nourishing that part of the community, as do the Forums, translation, documentation, marketing, development, QA etc. Each of those communities had good leaders who now help in the recognition of the people who do great work there. Without those leaders, it would be impossible for the regional membership boards,... [20:31] ...or worse, the CC, to recognise the full diversity of contribution that goes into something like 9.04. So, please be patient. The criterion for membership if "substantial and sustained contribution", there is no rush. It is NOT a popularity contest [20:31] ^^^ Mark [20:31] yeah, I've seen that quote and it confirms my opinion [20:31] ok, summing up my opinion: I think TurnKey is great, but am -1 on membership for LirazSiri (and alonswartz for that matter). This would easily change to a +1 if in the mean time sabdfl/CC consider contributions to TurnKey to be contributions to Ubuntu as well. [20:32] if we could find a way to document that (or how) Turnkey development directly contributes to the Ubuntu community [20:32] Ok, so the specific recommendations to take away from that are 'build that network' and 'raise the profile of your work' (within the Ubuntu community) [20:32] doh, you beat me to it [20:32] I echo Seveas comments above [20:32] that's what we've been doing with the discussions in ubuntu-devel [20:32] But there's no way to currently integrate the projects unfortunately [20:32] so basically, I want you to go back to Mark or the CC Liraz. I think you've made progress but I feel this is above us to decide [20:32] agreed [20:33] LirazSiri: i see _one_ thread on ubuntu-devel with your name on it [20:33] that's a pretty extensive thread popey [20:33] I'm -1 for now, but hope to see that change with some further community integration [20:33] its 12 mails [20:33] thats not an extensive thread [20:33] popey, stgraber, phanatic: can I please get a +1/-1. [20:33] (and also for alonswartz for the moment, since he is also to be considered shortly) [20:34] doesn't the two contributions together count though? [20:34] two? [20:34] -1 on alonswartz as well for the same reason. It's not a we-dont-want-you -1, but a not-sure-what-to-do -1 [20:34] I have received a strong endorsement from Ubuntu News editor? [20:35] LirazSiri, the UWN is useful and appreciated, but I can't think of a single instance where we conferred membership with that as the SOLE or MAIN community contribution. [20:35] I'm thinking maybe volunteering on a regular basis for a year shouldn't be discounted so quickly. Especially in combination with other contributions. Even if they are a bit out of the normal framework [20:35] If we can document the addition of TKL as a part of the wider Ubuntu community, that would be great [20:35] forumsmatthew: but my contributi [20:35] sorry cut in mid sentence [20:36] anyhow. its a judgment call. I feel that my previous rejection raised the bar is creating some resistance [20:36] not at all [20:37] not really [20:37] forumsmatthew: what do you consider the "wider ubuntu community" ? [20:37] we look at each application individually [20:37] things which are specific to Ubuntu and not potentially side projects with only a light affiliation [20:37] popey, stgraber, phanatic: can I please get a +1/-1. We have more candidates to come and not much time. [20:38] LirazSiri: the problem is that we don't know how to judge TKL involvement, and your UWN contribution was a total of ca. 60 hours (according to yourself), which is far from enough in my book. so it's a -1 from me. [20:38] TKL is wonderful, but we can't yet document it is internal to the Ubuntu community, only that it benefits as a project that stands along side [20:38] I will -1 for now. I would like to see more contribution to ubuntu from TKL [20:38] forumsmatthew: if Alon and I traveled all over the world and helped thousands of people set up Ubuntu on the server, I don't think anyone would say that isn't enough [20:39] I'm going to -1 on this one until we know how to judge TKL contributions and Ubuntu News contributions alone don't seem enough for membership (at least for me) [20:39] I don't think we should get discounted because we've figured out a more efficient way of doing exactly that... [20:39] ok thanks guys [20:39] does the development work on TKL happen in a way that contributes directly to Ubuntu, or is that a wonderful side effect? We are not qualified to judge, and that is the issue, LirazSiri [20:39] LirazSiri: perhaps you should look at partner status? [20:39] thats what other vendors of products do [20:39] we're not a vendor, we're a sister project [20:39] LirazSiri, please talk to the CC and ask them whether contributions to TKL should be seen as contributions to Ubuntu. Pending that decision, your application is now being rejected I'm afraid [20:40] hlippek, you're up next, please introduce yourself [20:40] Alright. Thanks anyway. Cheers! [20:40] hlippek seems to be missing [20:40] hi my name is hendrik im 29 years. living in haburg and work in softwaredevelopment for 5 years now [20:40] ah apologies [20:41] https://wiki.ubuntu.com/Membership [20:41] please read this and follow the directions under preparing your application [20:41] -1 please read that wikipage forumsmatthew just linked and prepare yourself for these meetings [20:42] i'm afraid it's a -1 from me as well [20:42] to make it official -1 [20:42] hlippek: I'd like to see some testimonials, and indication of a sustained contribution to Ubuntu on your wiki page please... -1 for now.. [20:43] right im very new in the comunity [20:43] -1 [20:43] great to have you here hlippek ! [20:43] no problem, please come back when you are prepared [20:43] :) [20:43] keep up the great work, and come back to us in maybe 3-6 months [20:43] we always need new blood :) [20:43] alonswartz is up next. forumsmatthew and myself already voted -1 because his application is based on TKL as well [20:44] did you even read my wiki page guys? [20:44] alonswartz, I have [20:44] yes [20:44] in the past i worked with zul to get the confconsole into karmic [20:44] alonswartz: i did, you have very good testimonials [20:45] and with soren on a number of issues [20:45] wrote a library that will be included in the ec2-init package [20:45] I know you've done more non-TKL contributions than Liraz, but I'd consider TKL a key part of it [20:46] yes, i too consider it a key part [20:46] besides that, membership applications based on packaging are better directed to the motu council as they can judge these contributions better [20:46] as we are trying to bring the projects closer together... [20:46] so the -1 from me means "I don't know what to do" and not "I don't want you" [20:46] ok, i havent read already about the time of contribution. but ill stii be active in the community [20:46] * forumsmatthew repeats what Seveas just said [20:46] thanks hlippek [20:47] OK, thanks guys... [20:47] the development work you seem to have done all very much revolves around TKL.. [20:48] popey: does it matter? [20:48] if it benefits both ubuntu and turnkey, i don't see the problem [20:48] popey, as long as it's a contribution to Ubuntu, that doesn't matter :) [20:48] well thats my point [20:48] how does di-live help ubuntu? [20:48] and what we need help establishing [20:49] or tklpatch? [20:49] regarding di-live, there has been talk about adding support to ubuntu-server to run live [20:49] when I said 'revolves around' I meant 'is limited to' [20:49] ok, thats useful [20:49] which is what di-live does. [20:50] with tklpatch included in ubuntu, making tkl-like applications would be easier, so that's useful [20:50] where was that talk? [20:50] about a year ago i spoke to cjwatson [20:50] but it wasn't needed back then, it might be in the future [20:50] right [20:50] so a year ago (two releases of ubuntu) you had a discussion with a developer about possibly including something in the future [20:50] regarding tklpatch, ignore the name, its a generically useful tool to create appliances [20:51] that to me isn't a sustained contribution to ubuntu [20:51] which was the basis for that long thread on ubuntu-devel [20:51] which long thread? [20:51] the thread you referred to when talking to liraz [20:51] the 12 mail one that has run this month? [20:51] a year later? [20:51] which mostly focussed on the pro/con of webmin [20:51] popey, "TurnKey Linux's take on Ubuntu appliance development: KISS" [20:52] Seveas: yes, that one [20:52] I still dont see one conversation with a developer and one small thread on -devel as a sustained contribution. [20:52] 33 mails so far. More than 12 but not very long. [20:52] hmm [20:52] o rly [20:52] -devel or -devel-discuss? [20:52] -devel [20:53] i see only 12 mails [20:53] how odd [20:53] ahh, broken thread, my bad [20:53] * popey stabs gmail [20:54] popey: love hate relationship with gmial tonight [20:54] indeed [20:55] I will go +0 [20:55] positive testimonials of potential future work, not a ringing endorsement of past achievements [20:55] ooh, well said [20:56] I truly value what TKL are doing, I think the range of VM images and the simplicity you've brought are exceptionally valuable to new users. [20:56] when you take into account introducing tens of thousands of new users to ubuntu (just like a loco), and the development work, i would think that is a sustained and considerate contribution ... [20:56] let's not rehash the entire TKL discussion please [20:56] Seveas: ok [20:56] stgraber, phanatic: votes please [20:57] alonswartz: I dont believe you can use those numbers [20:57] I am one of the people who downloaded it, and I'm already a member [20:57] +0 [20:57] .. and even then I deleted the VM [20:57] you need other ways of building a community around the product you have.. [20:58] popey: isn't that like saying that introducing people to Ubuntu in LoCos shouldn't count because you know somebody that continued using Windows XP? [20:58] alonswartz / LirazSiri do you have a separate section on the ubuntu forums? do you have an irc channel? [20:58] i dont follow that logic [20:58] that two -1 and 2 +0 [20:58] popey: we have very active forums [20:58] I'm just arguing that apache download logs do not prove new users.. [20:58] Today's score for the board: terrible. No new members :( [20:59] agreed. rough day [20:59] but lots of active people Seveas ! [20:59] popey: that's why we're applying for membership. We'd like to bring the two projects closer together. Even if only symbolically. [20:59] people contributing [20:59] you dont need membership for that LirazSiri [20:59] I'd compare TKL to crunchbang linux [20:59] does that still live? [20:59] Seveas: some months I guess are going to be like that, but good to see folks trying [20:59] sadly not [20:59] well, kinda [21:00] last month is the standard I would like to see [21:00] TKL and Crunchbang are projects that use Ubuntu technology, but dont specifically give technology back to the core product, but do generate a population of new users [21:00] how many users is hard to tell.. [21:01] The EMEA folks need a few more minutes? [21:01] people came prepared with great evidence and testimonials of sustained direct involvement in the Ubuntu community and that rocked. May we see that more often [21:01] no, I dont think so [21:01] technoviking, I think we're done [21:01] we know how many active users we have from the apache logs of our package archive [21:02] If you parse the logs for archive.turnkeylinux.org, you can count unique IPs and get a good guess for how many people are actively using TurnKey [21:02] yeah, our meeting is done [21:02] see you next month! [21:02] don't be sad, guys :) [21:02] I will contribute again and I will prepare me well for few meetings :D [21:02] technoviking, the mic is yours [21:02] goodbye, everyone! [21:02] o/ [21:02] thanks all ;) [21:02] BlackZ, awesome :) [21:02] bye everyone [21:02] technoviking: cc isnt for another hour [21:02] thanks guys... [21:02] according to my calendar [21:02] the %^#@*#@ wiki is wrong again :) [21:02] so, the next hour will just be Mike entertaining us :) [21:02] oops [21:02] popey: Are you sure? I have 21:00 UTC [21:03] se you in further meetings:-) [21:03] fridge says 22:00 [21:03] daylight savings time...the bane of humanity [21:03] I'm happy to do either [21:03] I'm here for 21 [21:03] have I messed up _two_ meeting times in one day!? [21:03] lol [21:03] yes [21:03] you're just trying to make me feel better about myself [21:03] holy cow I'm rubbish [21:04] no, wasnt me :) [21:04] Created by: N for Ubuntu Fridge Calendar [21:04] whoever N is [21:04] it gets messed up with DST [21:04] the fridge is correct in the summer :) [21:04] technoviking: doesnt this happen a lot to you :p [21:04] I repeat: daylight savings time...the bane of humanity [21:05] forumsmatthew: *hugs* so true [21:05] :) [21:05] see if folks stick to UTC no confusion [21:05] czajkowski: I'm from Indiana, I did not have daylight savings growing up:) [21:05] so now you do double DST to compensate? :) [21:05] Arizona, where I am, still doesn't use it. Wisely, i believe [21:06] popey: Nick I think [21:06] okay, I need to help my son with something [21:06] bye, all! [21:06] forestpiskie: toodles [21:07] so, are there only 3 of us? [21:08] bet more turn up in an hour [21:08] well, 52 mins [21:09] technoviking: I hope you didnt rush from some place to be here for now [21:09] o/ czajkowski [21:10] forestpiskie: don't mind me, I tab fail lots [21:10] * popey pokes nixternal [21:10] hello [21:10] czajkowski: that's cool then - I wondered who I had forgotten ;) [21:13] technoviking / pleia2 / persia _can_ you be around in 48 mins, should the rest of the CC be around? [21:13] yeah [21:13] Um, I'm not actually in the CC :) [21:13] popey: I should be, useless I have to pick up my son at school [21:13] i know, but you said you were here for it... [21:13] maybe you didnt [21:13] Sure, I can be around. [21:13] I appear to be making up stuff [21:13] hehe [21:14] popey, what else is new? [21:14] So.. my mum (mom) made some wine out of grapes we had in our garden. I have had two glasses. It is entirely possible that this has clouded my ability to operate a keyboard. [21:14] :) [21:15] also.. snow! [21:15] http://popeydc.dyndns.org/webcam/index.html [21:15] :) [21:15] popey: its beautiful [21:16] more snow: http://www.facebook.com/album.php?aid=39995&id=1016333075 [21:16] :) [21:16] fear my weapons! http://www.facebook.com/photo.php?pid=818472&l=662ad781d3&id=1016333075 === etali1 is now known as etali === noy_ is now known as noy [22:00] * pleia2 peers in [22:02] * nixternal hides in a corner [22:06] * geser offers nixternal some black light for his corner [22:09] afternoon all [22:10] Aloha [22:11] o/ === fader_ is now known as fader|away [22:13] Is anyone else here for the CC meeting? [22:13] yep [22:14] o/ [22:15] \o [22:15] looks like it just might be the 4 of us [22:16] looks like there are 3 items [22:17] 1st is dholbach and mdke, both seem to be afk [22:17] 2nd I think we need some background stuff pulled together [22:17] right, as for the 3rd one, we should just +1 and put it in to action [22:17] MC -> DMB [22:17] nothing to discuss really [22:17] right, I think that just needs a formal +1 [22:18] shortest meeting eva! [22:18] fine with me [22:18] indeed [22:18] definite +1 for DMB membership [22:18] 3rd item needs more than a +1: someone has to go and make the change in LP. [22:18] I am fairly certain it was a given anyways [22:19] as for #2, we need to get together the documentation as to what each board does for appointments/elections and go from there with streamlining the process [22:19] I can start that this week [22:19] persia: right, which I am guessing will be easy enough [22:20] yeah, I'll mail the list my summary when it's done === robbiew is now known as robbiew_ [23:55] time? [23:56] 5 minutes [23:56] 5 minutes nigel_nb [23:56] doh [23:56] 4 minutes, actually :) [23:56] unless my time is also wrong [23:57] it was 5ish before I hit enter! ;) [23:57] I still prefer to work in UTC. Lessens confusion. [23:58] pleia2: [23:55] < nigel_nb> time? [23:58] [23:56] < pleia2> 5 minutes [23:58] 3 minutes now [23:58] not that I'm being picky, even I'm not that fussy over things :P