=== starcraftman is now known as WikiNinja === WikiNinja is now known as starcraftman === AWAY|_Tux_ is now known as _Tux_ === jjohansen1 is now known as jj-afk === Ayrton is now known as Ayrton` === Ayrton` is now known as Ayrton === ptkhanh|zzz is now known as ptkhanh === nijaba is now known as nijaba_afk === nijaba_afk is now known as nijaba === doko__ is now known as doko === oubiwann is now known as oubiwann-away === oubiwann-away is now known as oubiwann === zul is now known as ep === ep is now known as zul === yofel_ is now known as yofel === azul_ is now known as jodh [16:01] o/ [16:01] o/ [16:02] hi [16:02] lo [16:02] hey [16:02] azul_: is this your final irc nic? [16:02] lol [16:03] hello [16:03] #startmeeting [16:03] Meeting started at 10:03. The chair is robbiew. [16:03] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [16:03] [TOPIC] Foundations Team Lightning Round [16:03] New Topic: Foundations Team Lightning Round [16:03] barry is sick [16:04] cjwatson: since I know you have an extremely interesting report...you can go first :P [16:04] hah [16:04] done: loads of merges, plymouth/upstart interop patches, working on new grub snapshot packaging (should help with flicker-free boot), figuring out what spec drafting I need to do [16:04] todo: draft a small handful of specs, continue with new grub, polish off a few easy work items [16:04] -- [16:05] thnx [16:05] ev: anything? (know you've been hangin with the sheiks [16:05] lol [16:05] ARGH DAMN SOYUZ [16:05] (sorry) [16:06] turret's [16:06] very short week; on holiday in Abu Dhabi (yay Vettel and Red Bull!). Working on ubiquity-preserve-home in partman-auto. [16:06] done [16:06] ubiquity-perserve-home++ [16:07] mvo: you can go next ;) [16:07] short week: mon,tue vacation; friday afternoon sick :( [16:07] added some workitems; work on rnr-server, work on s-c client review branch; upload new squid-deb-proxy; Support-timeframe LP branch (week 5?): finally had to setup a full LP dev environment :/ (that took a bit); unattended-upgrades: merge stuff; update-manager: bugfixes in i586 detection, upload SRU, work on better EOL presentation, enable maverick->natty [16:07] todo: check WI/spec, work on rnr-server [16:07] (done) [16:09] thnx [16:09] psurbhi: ? === cypher_ is now known as czajkowski [16:09] Nov 11th onwards: short week, was unwell half of last week [16:09] btrfs - grub - testing - got a bug from a user, reproducing that. [16:09] looking at mountall code, understanding dbus. [16:09] todo - draft spec for event based initramfs, make a package of btrfs for grub and test more. [16:09] (done) [16:10] oh yeah, plymouth/upstart interop involved sucking dbus into my head too [16:10] thanx...glad you're feel better [16:10] my sympathies [16:10] heh [16:10] thanks :) [16:10] much needed! [16:10] azul_: ? [16:10] psurbhi: how is the license stuff with grub going? [16:10] robbiew: re nick - well, maybe. "jodh" isn't exactly gr8, but jhunt, etc taken and jamesodhunt too long :) [16:11] one sec... [16:11] I liked "ifdef" :) [16:11] mvo, i did not get a chance to talk to cmason, but spoke to Peter Anvin and he happens to think that the license should be resolved :) [16:11] how 'bout Keybuk2 [16:11] lol [16:11] just for completeness: eglibc backports, second change in linking behaviour, spent most time with an internal project [16:11] should as in ought to be in the future, or should as in believes it is now? [16:11] hmm. [16:11] weeks exec summary: lp:#674146 + pain [16:11] :) [16:11] either Keybuk++ or Keybuk-- depending on performance [16:11] (silly ambiguous language) [16:12] detail: Met up with Scott on Friday, which I found very useful. [16:12] Re lp:#674146 - Created a patch to disable optimizations for building [16:12] dpkg on armel for cjwatson (temporary fix). Hacking dpkg down to a basic [16:12] testcase is proving tricky (who _wrote_ that code? :). Will persist with [16:12] this. Currently isolating specific gcc-4.5 optimizer flag causing SEGV. [16:12] This is hampered by speed of kakadu (and doko compiling at same time :) [16:12] Wishing "configure" wouldn't attempt to parse CFLAGS (as it can't). [16:12] Plan to put lp:#674146 aside to concentrate on upstart for rest of week. [16:12] yeah, as I said, no rush on that bug now I think [16:12] azul_: what about jhung? ;) [16:12] ... once I've updated lp bug with details of currently running optimizer tests. [16:12] arf arf [16:12] we know who wrote the code! [16:13] jhung...lol [16:13] azul_: thanks! [16:13] doko: ? [16:13] gahh, was wondering why kakadu was that slow ... [16:14] doko: soz - I've been compiling like mad on that box. I asked is about any other atmel kit, but apparently that is it :( [16:15] ok, stopped my build [16:16] doko: thx [16:17] robbiew should send you a http://www.genesi-usa.com/products/efika - They come with Karmic, but building in Natty chroots works well. [16:18] or ScottK could send you one...since he got 2 for free! :P [16:18] !! [16:18] I ordered one, didn't arrive yet [16:18] robbiew: Mine are all busy. [16:18] doko: btw, that's 100% expensible [16:18] Keybuk: ? [16:19] done: met up with $(get-current-irc-nick-for jamesodhunt) in London on Friday, very productive and useful, we'll be doing more of these [16:19] done: planned tech talk, just got to arrange a time and date [16:19] done: still figuring out how to handle "profiles" in Upstart :( [16:19] * doko orders to one with gold plating [16:20] lol [16:20] [TOPIC] Natty blueprints [16:20] New Topic: Natty blueprints [16:21] I'm out next week...so will plow through BPs this week [16:21] only a handful left that are unapproved [16:21] so shouldn't be an issue [16:21] doko: what? only gold? latinum !! (Or better yet coated with printer ink? :) [16:22] [TOPIC] Natty Release [16:22] New Topic: Natty Release [16:22] first release meeting is this week [16:22] cjwatson: do we have a status page yet? I haven't looked :/ [16:22] I haven't created one, so probably not [16:23] will have to assemble some kind of report, but I'll probably just use people's lightning-round updates for the last couple of weeks [16:23] and cull something out of that [16:23] not too long before we have to start settling down a bit for alpha-1, though [16:23] * skaet nods [16:23] the archive isn't that badly out of shape, though [16:24] cool [16:24] [TOPIC] Sponsorship Queue [16:24] New Topic: Sponsorship Queue [16:25] I haven't checked recently, but looked like folks have been signing up [16:25] nothing else to add here [16:25] [TOPIC]AOB/GoodNews? [16:25] New Topic: AOB/GoodNews? [16:25] apparently we are selling Ubuntu Cycling Kits in the store [16:25] wtf? [16:26] not really anything to do with our team, but firefox 4 is ace [16:26] I have my house keys back [16:26] it's actually heard of performance [16:26] Competition is good for that kind of thing. [16:26] any thoughts on how it compares to Chrome? [16:27] I can still use my extensions ... [16:27] same experience here, firefox4 is just great, I swtiched to it from chrome [16:27] no subjective experience of chrome performance since its UI rubbed me up really badly the wrong way [16:27] mozilla's benchmarks show slightly faster js execution than chrome, but that's the only thing I've seen [16:27] the awsome bar is awsome and noscript is great to get rid of most anoyances [16:28] re browsers, I'm loving http://www.uzbl.org/. [16:29] it's only a matter of time before we're all using RockMelt anyway. :-P [16:30] heh [16:30] #endmeeting [16:30] Meeting finished at 10:30. [16:30] thanks all! [16:30] seeya [16:30] thanks [16:33] ev: jhung is taken :( [16:33] hung is free :-P [16:33] I need someone else to misspell my name in amusing ways to inspire me! [16:34] hungon! [16:34] according to nickserv both jhung and hung are not registered [16:34] hahaha [16:34] there you go [16:35] ev: RockMelt [16:35] is that the next big thing, like Flock was? [16:35] oh yeah [16:36] it's the second coming of Flock [16:36] All the success of the original, but with Chrome this time === jdstrand is now known as jdstrand_ === oubiwann is now known as oubiwann-away === oubiwann-away is now known as oubiwann === zul_ is now known as zul [18:58] https://wiki.ubuntu.com/Edubuntu/Meetings/Agenda [18:58] hi, highvoltage :) [18:58] hi folks [18:59] hi HedgeMage and dinda, good to see both of you here again [18:59] not sure if everyone's here yet, but I'll kick off with the technical stuff so long [18:59] * HedgeMage listens and eats lunch [19:00] * We have daily builds again, they're a bit rough at the edges, but it's early days so that's normal [19:01] * I responded to the artwork team regarding their request for specifications: https://lists.ubuntu.com/archives/edubuntu-devel/2010-November/003659.html [19:01] they've shown interest on working on a new wallpaper and other artwork we might want [19:01] we just need to ask for it [19:01] Alpha 2 is on 2011-12-02 [19:02] we're not shaping up too badly: https://wiki.ubuntu.com/Edubuntu/Devel/RoadMap [19:02] [i] indicates in progress [19:03] there's something I'm forgetting that I wanted to mention yesterday, but it will come to me later :) [19:04] ah yes, and there's also the Faenza icon set that I suggested last time- [19:04] Xubuntu is going with it, Debian is, and a few other systems. it's not really unique anymore, so I guess we'll stick with plan A then and just fix up the breathe-icon-theme [19:05] dinda: any feedback from all your recent adventures? [19:06] hihgvoltage; lots of interest for Ubuntu in Education but things move slowly [19:06] highvoltage: That's Alpha 1, not Alpha 2, FYI. [19:06] I did make some progress on the Edubuntu marketplace topic [19:06] oops, yes I meant alpha 1 [19:07] dinda: ah, I meant to talk to you about that, stgraber talked to claire at UDS [19:07] AFAIK it's fine if you want to create a marketplace but Legal is looking for a suitable agreement, similar to what is on the current Ubuntu marketplace [19:07] not sure how you planned on handling those companies who request to be listed there? [19:07] dinda: so the agreement is that service providers and ubuntu partners go on the canonical partner page [19:08] dinda: and we keep people who sell pre-installed systems with edubuntu on the edubuntu marketplace page [19:08] correct, marketplace has no business relationship with Canonical, asked for legal to write up a disclaimer to that affect [19:09] did you plan on some approval process? say through the edubuntu council? [19:09] nope, they can just contact our web team via the contact form and provide details that will be listed [19:10] I can't currently see a need for an approval process, but if there should be then I'd like to hear what you think [19:11] not sure but it seems like there should be some minimal requirement [19:11] some record of activity [19:12] maybe at least a website and contact person [19:12] that sounds very reasonable === xfaf is now known as zul [19:13] dinda: I'll add that to the marketplace page when I update it again [19:14] the listing agreement that Canonical uses to list folks in the marketplace can be used [19:14] once they sign, they can be listed [19:14] I can handle that part for now [19:14] is that new? I added a company there last year without signing anything [19:15] probably, they have tons of new forms [19:15] ok [19:15] will send you a copy and the edubuntu council when I have one [19:16] dinda: is the 'server in a box' part on the meeting page new or from a previous meeting? is there something left to discuss there or should I take it off? [19:17] * mhall119 made it [19:17] been talking to various parties about that project but nothing solid yet [19:17] it can be taken off for edubuntu for the moment [19:18] and "Official support for educational-desktop software"? I can't remember seeing that before? [19:18] oh yes! some good news there [19:18] it's on the table now [19:19] What's a "school server in a box" supposed to do? [19:19] Canonical is willing to offer support for the educational-desktop software and help move items in Main [19:20] dinda: ok. personally I was quite happy when they moved out of main :) [19:20] but we have package sets now so having them in main won't be problematic anymore [19:20] yeah, but stuff moving out of main caused a translations issue on one game (can't remember which) [19:20] but it affected Qimo troo [19:20] too [19:21] the issue for Canonical is that we (I) need to be able to go to large deployments and offer full support [19:21] that can't happen without that software being in Main [19:21] mhall119: yep, we'll just have to be careful with that [19:22] all it means is that it goes into our QA process and we offer technical support for paid customers [19:22] so either I can select just certain applications to move into Main. . . [19:22] or I can ask for the entire educational-desktop to be included? [19:24] there's a lot of packages pulled in by edubuntu-desktop [19:24] dinda: what effect does the archive reorganisation have on Canonical support? I thought that the split between universe and main was becomming mostly cosmetic now? [19:24] * mhall119 assumes that's what you meant [19:24] dinda: oops, and stgraber talked to jane, not claire :) [19:24] not exactly sure highvoltage [19:25] but I know we can't offer paid support on anything that is not in Main [19:25] ok [19:25] and right now I can't go to schools and tell them any educational software is covered by our current support offerings [19:26] dinda: universe/multiverse are going to disappear and the new infrastructure (planned for Natty) will let any company (with coredev) announce support to any package, be them in universe or in main [19:26] so we need to see what packages in ubuntu-edu-* are not currently in main? [19:27] dinda: so moving stuff in main just feels like additional pain (because we need MIRs for any additional dependencies). If Canonical wants to do them all, that's fine, but I'm not going to wait for a package to be in main to ship it or restrict package selection to what's in main [19:27] mhall119: all of them [19:27] dinda: do you have any other details about this yet? I'm quite interested in who will be working on it [19:27] mhall119: only the package that are also shipped on ubuntu-desktop are in main [19:27] highvoltage: that's fine it really doesn't affect what you want to do or what edubuntu needs. . . [19:27] ok [19:28] it's just something I'm trying to make happen so that Canonical can offer support. . . [19:28] highvoltage: no set plans yet, we would do the moving when needed [19:28] I think Canonical could make contracts listing specific packages outside of main to support anyway [19:30] maybe you need a Canonical-internal list of packages you want to (or don't want to) support if requested, even if not in main? [19:30] JanC: think about an Ubuntu Advantage (UA) for Education, the current UA only covers the default install [19:31] so selling support to schools really gets them nothing b/c none of the educational software is covered [19:32] yeah, that might be useful, and if I understand stgraber correctly, the rigid supported/not supported distinction is going to be removed anyway [19:32] I'm asking to create a way for shcools to buy low cost support that covers what they will actually be using, not just generic support [19:32] dinda: the issue with moving packages in main is that they won't be able to depend on packages that are in universe. That essentially means that if we want to keep our current flexibility, none of the meta packages will be moved. [19:33] right now any company except Canonical can cover whatever they want, it's just that Canonical can't [19:33] looking at the recent RHEL 6 release, they have RHEL Server & RHEL Desktop, plus several "plugins" [19:33] dinda: and that if we want any of the package moved to main to dpeend on additional packages, we'll ask them to be demoted to universe [19:33] where the "plugins" offer support for specific use cases [19:34] the most likely scenario is that a very large deployment will ask to have certain apps pre-installed, in which Canonical has to support them [19:34] and that means those items will automatically get migrated to Main as part of the support & image QA process [19:34] dinda: no packages ever gets automatically migrated to main [19:35] dinda: it really feels like we're re-discussing exactly what was discussed and agreed on at UDS. The new debtags-based support system is designed for exactly what you're describing and doesn't depend on packages being in main. [19:35] dinda: what if there was just a list of "educational" packages that Canonical would provide support for separate from the typical support agreements? [19:35] or, what stgraber said [19:36] mhall119: that's what I asked earlier, maybe I should just ask for a select few apps to be included under an Ubuntu Advantage umbrella [19:37] stgraber: but I'll review the UDS discussion and try to better understand how it relates [19:38] stgraber: so who would put the debtags on the educational packages, edubuntu or canonical? [19:38] or revolution linux? [19:38] canonical would [19:38] dinda: https://wiki.ubuntu.com/Specs/ImprovedSupportDeclarations [19:38] thanks [19:39] mhall119: any company who has coredev and wants to support packages would be able to tag the specific set of packages they want to support [19:39] highvoltage: are these debtags only for paid support? [19:39] mhall119: there'd be 3 class of support: sru, security and helpdesk [19:39] mhall119: for each of them, there would be a period of validity (18 months would be the current one for ubuntu-desktop) [19:39] mhall119: I guess the short answer there is "no" :) [19:39] ok [19:40] so if I wanted to advertise certain packages as being supported by Qimo, how do I go about doing that? [19:40] as it's based on tags, the new structure allows more than a company to offer support on a given package [19:40] mhall119: the implementation of it is not yet complete (as seen in that wiki page) [19:41] which wiki page? [19:41] mhall119: but basically, you'd have to agree to do a certain amount of work and maintenance of those packages and be responsible for them [19:41] mhall119: https://wiki.ubuntu.com/Specs/ImprovedSupportDeclarations [19:41] thanks [19:42] interesting, it's a high priority but not yet been assigned to anyone [19:42] totally makes sense though [19:42] mhall119: in short, you'd be able to do something like an apt-cache show packagename, and then it would show you which company(ies) are supporting the package and for how long. [19:44] that sounds nice [19:44] thanks all for discussion on that topic, any suggestions most appreciated [19:44] dinda: this implemention would mean, no additional paperwork (as in, main) for the edubuntu community (that's, until universe is merged into main) and lets Canonical, Revolution Linux, ... do clear support declaration so users know what is REALLY supported [19:45] (as opposed to the general belief that all of main is supported by Canonical, which is wrong) [19:45] that sounds like a lot to put into package headers though.... [19:45] edubuntu-council renewal is up (as I sent out to the lists), I haven't heard back from nixternal yet, not sure if he's going to be available for another term [19:45] mhall119: debtags are already used in debian for other purposes, so we know it works and it scales [19:45] mgariepy has been nominated though [19:46] mhall119: we just need some LP (or other script) magic to automatically tag packages based on support declarations [19:46] stgraber: scales how far? What if 100 companies offer support for the same package? [19:46] highvoltage: saw that notice, when are you planning on holding the elections? [19:46] stgraber: I guess having LP auto-generate them would make maintenance easier [19:46] mhall119: the outcome of the UDS discussion was "Companies who have Ubuntu Core developers working for them" which currently means maybe 4-5 companies [19:47] ok, so Qimo wouldn't be eligible [19:47] dinda: I mailed the CC list about it because we don't really have a large candidate pool, and sabdfl said he's fine with a re-approval since it's a tight core [19:48] mhall119: you can always become a core-dev ;) [19:48] mhall119: even if there was hundreds of companies in this case, I doubt they'd all support the same packages. It seems more likely to have a larger amount of supported packages (with only 1-2 companies supporting them) then having the current amount but support by hundreds of companies [19:48] highvoltage: I was little confused on the requirement to be an edubuntu member as opposed to just an ubuntu member? [19:48] I need a bit more packaging knowledge before I apply for core-dev [19:49] highvoltage: is that a different approval process? [19:49] mhall119: but I do think it would be kind of weird for a non-profit to do that, unless they have sponsored employees for that or something [19:49] dinda: yep [19:49] dinda: for an Ubuntu member, it's just a matter of putting your name on the agenda and we'll vote at the next EC meeting. It's usually quite easy for an Ubuntu member to become Edubuntu member. [19:50] * mhall119 's name is on the list [19:50] ok, that's kind of what I thought [19:51] * dinda supports mhall119's edubuntu membership :) [19:51] dinda: currently you can become an Ubuntu member through regional boards, DMB or by becoming an Edubuntu or Kubuntu member. The first two just give you Ubuntu membership, the last two also give you Edubuntu or Kubuntu membership [19:52] yip, that part I knew just wasn't sure the reverse was true; makes sense though [19:53] highvoltage: can you give a quick overview of the status of the edubuntu website? and I have a request [19:53] dinda: sure! [19:53] I'm replacing the identica widget with twidenash [19:53] it still has some css issues, I should actually poke mhall119 about it :) [19:54] sure [19:54] dinda: since we last spoke, you probably noticed that it has a banner at the top now that explains what edubuntu is. you mentioned before that there's no explanation on the front page, that was the plan for it [19:54] it's still kind of work in progress, the banners just hasn't been extremely high priority so far [19:55] last week we also added a contact form to the website [19:55] ooh, that's nice, like the banner [19:55] dinda: and I guess you've also seen weblive by now? it was also added in the last month or so [19:55] yeah, that is totally awesome! [19:56] I also added some more links and documentation to the documentaiton page [19:56] that's about all that I can think of for the website at this stage [19:56] we're close to 6400 weblive users since we launched it [19:56] I'm working on a blog entry about ltsp fat clients that's turning out to be closer than documentation at this stage [19:56] highvoltage: where's the contact form? [19:57] I'll probably blog it and then copy and paste it for our docs [19:57] mhall119: last button on the top [19:57] Documentation? [19:57] mhall119: oops, I just noticed it only displays for logged-in users *fail* [19:57] :) [19:57] yes, since it's taking a very long time to get some updates the ubuntu.com education webpages [19:58] so I might just ask to put the info on the edubuntu site - it's a page on How to run a successful ubuntu pilot in your school [19:58] or I could just do a wiki page but a web page looks so much nicer [19:59] I'll create the page and you can decide if it's appropriate for the edubuntu site [20:00] also have some lessons plans almost ready so teachers can just pick up and use [20:01] that's about all from here - any questions [20:02] dinda: what apps do your lesson plans utilize? [20:02] i have a support request I want to ask you folks while I have you but will ask in #edubuntu after this meeting [20:02] mhall119: right now just gcompris but want to expand to other apps [20:03] mhall119: would be nice to have a few for each grade level as a hook for different teachers [20:03] I'd like to see topical or application specific lesson plans [20:03] but I have no idea how to make them [20:04] mhall119: I'm aiming for topical and the software is just one tool they can use to teach the topic/objective [20:04] I think lesson plans often need to be adapted to local rules anyway [20:04] JanC: exactly , they have to be aligned with local curriculum standards [20:05] JanC: I'm starting with Texas b/c that's where I live and where I have teachers to help me [20:06] dinda: cool, we'd like to get some user stories (which are not case studies) on the website [20:07] so it should be more like a collection of possible lessons, exercises, etc. -- something teachers can adapt to their local rules [20:08] highvoltage: I think I can locate a few for you [20:08] JanC: *nod* that would be awesome++ [20:08] JanC correct [20:09] Janc: can't possibly hit every national and local standard but want to select a few key countries [20:09] perhaps Ingots in the UK & India [20:10] Ingots is also quite big in South Africa [20:11] * JanC googles for "ingots" [20:12] mhall119: I'll poke you a bit later about that twidenash script :) [20:13] ok [20:13] it's soem on-line course program? [20:13] I may not be around, I have to run up to the hospital in a bit [20:15] ok, I guess that's it for the meeting... *GONG* [20:16] no quorum for a membership vote? [20:17] mhall119: I think we should try to get a specific meeting for that, I didn't get around to pinging the council members and telling them to be present today [20:17] mhall119: sorry about that [20:17] mhall119: I'll try to round them up and poke you tomorrow if that's ok [20:17] if the meeting is over: What's a "school server in a box" supposed to do? [20:17] okay [20:22] JanC: I think it was meant to be a general school infrastructure server. I'm not sure what was discussed at that UDS session, but I think it was deemed out of the schope of Edubuntu [20:22] probably more appropriate for the server team. [20:23] I would think there is not much difference between a school server and a company server [20:23] JanC: come over to #edubuntu and I'll tell you about it [20:23] okay, I'm there ;) [20:23] JanC: indeed. I guess if we were talking about server-side stuff like schooltool and moodle, then that might have been something else that we might have looked into then [20:24] yeah let's move over :) [21:00] hi folks, who's around for today's udd meeting? [21:00] #startmeeting [21:00] Meeting started at 15:00. The chair is barry_. [21:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [21:02] thumper, poolie, james_w ping [21:02] me [21:02] hi [21:02] is it that time already? [21:02] ajmitch: ping [21:03] hi, yeah. i know the usa (canada too?) went off dst so it comes even earlier for us now [21:03] * slangasek waves [21:03] hi [21:03] slangasek: hi [21:03] * ajmitch is here [21:04] [TOPIC] agenda [21:04] New Topic: agenda [21:05] barry_: hi [21:05] thumper: hi [21:05] [TOPIC] action items [21:05] New Topic: action items [21:05] ? [21:05] no agenda? i added something... [21:05] * barry to start some sphinx docs to be well-integrated w/ wiki.u.c (ongoing) [21:05] [21:06] er, yes, sorry [21:06] I think the wiki formatting is a bit off [21:06] i've been a little ill so kind of unprepared ;) [21:06] sorry to hear that [21:06] fixing... thanks... [21:06] [LINK] https://wiki.ubuntu.com/DistributedDevelopment/20101117 [21:06] LINK received: https://wiki.ubuntu.com/DistributedDevelopment/20101117 [21:07] agenda: action items, udd survey results, bugs [21:07] * barry to start some sphinx docs to be well-integrated w/ wiki.u.c (ongoing) [21:07] [21:07] not done, but i'd like to keep it on the list [21:07] agree [21:07] * poolie to start list thread to find problems which can be carried on at UDS (ongoing) [21:07] [21:07] i didn't want to take this off without poolie's input [21:08] and... [21:08] * barry to contact poolie about getting his UDS session notes into the blueprint [21:08] [21:08] ah, i don't think we had a new thread, but i did gather stuff from old ones [21:08] i sent a brief mail [21:08] poolie: i know you posted to ml, but i haven't read it yet [21:08] with a link [21:08] should we turn them into a blueprint? it's more a bunch of ideas and issues than an actual blueprint [21:08] poolie: thanks. i think that covers both items [21:08] perhaps we should capture them on a wiki page in more detail than my mail [21:08] i'll take that on [21:09] poolie: thanks. i do think we should have a blueprint that we can use to track work items [21:09] [ACTION] poolie to capture notes from email into wiki page with more detail [21:09] ACTION received: poolie to capture notes from email into wiki page with more detail [21:10] poolie: which reminds me, will jelmer be joining us here after the 1st of the year? [21:10] from the 10th [21:10] oh, in this meeting in particular - i hope so [21:10] cool [21:10] mm, but what time will that be? about 10pm? [21:11] if so, i hope he can [21:11] i have no problem moving the meeting earlier to accommodate, but i think that will affect you and thumper, right? [21:11] it's currently 8am for me; 7am wouldn't be a burden; 6 would be a slight burden [21:11] barry_: I'm ok with an hour earlier (normally) [21:11] let's see how we go [21:12] okay, we can take that up when jelmer's on officially [21:12] so he'll be joining us from the start of the bzr sprint at the platform rally [21:13] excellent. is that happening at the same time, or a week before/after? or maybe that's the lp sprint i'm thinking about? [21:13] (sorry, my brain is not with me today) [21:13] overlapping in time and space with the (canonical internal) platform rally, [21:13] that'll be great [21:13] and immediately prior to the lp epic, which we will also be attending [21:13] the first week i plan for us to mostly work together as a small team, of course also talking to ubuntu people [21:14] and the second week i want us to do lots of work crossing the lp:bzr boundary [21:14] eg bzr people fixing things in lp and vice versa [21:15] nice. i won't be able to attend the lp epic [21:15] [TOPIC] udd survey results [21:15] New Topic: udd survey results [21:16] -> poolie [21:16] ok, we got 82 great responses to our "how is udd for you" [21:17] mostly pretty positive: net promoter score (of people who responded) very widely distributed, but with ~60% of people voting 8, 9, or 10 [21:17] lots of textual answers [21:17] perhaps i'll just send a dump of raw answers to the list? [21:17] +1 [21:17] i don't think there's anything sensitive in there, but i'll check first [21:17] or edit that out if there is [21:18] probably best to anonymize the responses [21:18] the answers which score low would be interesting to read [21:18] ajmitch: yep. it would be nice to see which of those map to known bugs [21:19] so that's an action for me [21:19] [ACTION] poolie to send a dump of udd survey results to mlist [21:19] ACTION received: poolie to send a dump of udd survey results to mlist [21:19] poolie: any themes that stand out? [21:20] good qn [21:20] people generally find the bzr interface nice [21:20] (btw, that Bazaar/Plate page does not yet exist) [21:20] reliability, including getting up to date imports [21:20] error messages caan be confusing [21:20] lp ui clunky [21:21] it's another layer on top of a complicated stack [21:21] when things work, it's great [21:21] contradictory messages (i guess varying experiences) on whether git imports are good or not [21:22] also varying opinions on whether they're glad or frustrated we don't use git [21:22] ;) [21:22] barry_: I'll show you my clamav mess at bacon-pig if you want more use cases. [21:22] perhaps not surprisingly the people with bad experiences seem to use it the least [21:23] so, we need to look for the place to insert a wedge, where making things a bit better will make people use it more [21:23] ScottK: sounds great [21:23] poolie: I gave it a try, wrote a long mail to the UDD list about issues I found. I don't have a sense that a lot has changed. Not sure if that's accurate or not. [21:24] ScottK: if it's the mail i'm thinking of, i think we got through nearly half since it was sent earlier this year [21:24] * ScottK would be glad to try it again if significant progress has been made. [21:24] maybe half by count not size [21:24] poolie: OK. That's good to know. [21:24] the others are definitely still on the list [21:24] one interesting thing to call out from udd, is that the general things for the bzr team are [21:25] - network speed, holistically (including mirroring, or shallow checkouts, etc) [21:25] It's difficult to know the state of the project as a casual observer and has it progressed enough to be worth trying again. [21:25] maybe we should send a better summary of what's changed since eg the last ubuntu release? [21:26] * ajmitch will need to sort out something about REVU & branches if I'm to be of use to this meeting [21:26] poolie: +1 [21:27] ajmitch: yes, would you like to prepare something for 2 weeks time? [21:27] barry_: OK, I'll try & come up with some questions/suggestions at least [21:28] ajmitch: great! [21:28] who wants to talk about bugs? :) [21:28] [TOPIC] bugs of interest / top bugs [21:28] New Topic: bugs of interest / top bugs [21:28] reliability is still a big problem right now; almost 2000 failures according to http://package-import.ubuntu.com/status/ [21:28] i'm a little afraid this list is getting pretty long ;) [21:29] slangasek: agreed. we really need to address the import failures. can't use udd if the branches aren't there [21:29] http://package-import.ubuntu.com/status/language-pack-gnome-lo-base.html [21:29] LINK received: http://package-import.ubuntu.com/status/language-pack-gnome-lo-base.html [21:29] that's a funny failure mode [21:30] 696 packages failed with key AssertionError::main:import_package:import_package [21:30] debian unstable is hardly getting any updates at the moment, due to squeeze freezing [21:30] oops, ECHAN [21:30] so package imports in particular, as a special focus? ok [21:30] james_w: I see gourmet has landed back in that failure state again in spite of your efforts :( [21:30] ajmitch: It actually fits. [21:30] we're still having some trouble getting enough time to work on udd things outside of bzr itself [21:31] perhaps a big push on that specific thing will help us focus on it [21:31] slangasek, yeah, I'm still working on it, but it's having to fit in around other things unfortunately [21:31] * slangasek nods [21:31] poolie: we have bug 653307 for a different failure case, i guess we should have separate bugs for each major class of import failures? [21:31] Launchpad bug 653307 in Ubuntu Distributed Development "Import fails with missing referenced chk root keys" [Critical,In progress] https://launchpad.net/bugs/653307 [21:31] slangasek, I understand why we are getting the failure though now [21:31] oh, good :) [21:34] we have 10 "bugs of interest". do we want to go through each one? maybe take a look at the wiki page and see if there has been any progress on any of them? [21:34] barry_: 10? i see 3 on the agenda.. [21:35] ... unless i reload [21:35] refresh :) [21:35] let's go, quickly [21:35] a graph of packages is flacoste's favorite nomination [21:35] (and he sets my bonus :-) [21:35] heh [21:35] on the grounds that you should put metrics in place early in the use of a feature [21:36] this is mostly about inserting an X-SBC field to mark a package as having been built from a branch [21:36] probably trivial to do; just needs figuring out what would be tasteful to put in it [21:36] how much of the BFB infrastructure is in place for that so far? [21:36] i'd also like a graph of the package-imports and/or hottest100 results [21:36] according to jelmer there is infrastructure to scan it out there [21:36] so that we assess the quality of our service [21:37] there are graphs of them [21:37] possibly there should be better graphs? [21:37] if we're going to do 10 bugs, and stay roughly within our hour, i'm going to go fairly fast [21:38] poolie: please do [21:38] http://pad.lv/556132 is the top vote for Linaro - problems in conch - probably needs to be fixed upstream in twisted; i will push it [21:38] LINK received: http://pad.lv/556132 is the top vote for Linaro - problems in conch - probably needs to be fixed upstream in twisted; i will push it [21:38] * barry_ remembers a uds conversation about this during a walk to/from dinner [21:39] poolie: I assume that is the point where ssh needs to renegotiate keys? [21:39] http://pad.lv/375013, commit to stacked branches, is Tim's top vote for the code team - it will ease some issues in building enormous branches in moderate sized vms [21:39] LINK received: http://pad.lv/375013, commit to stacked branches, is Tim's top vote for the code team - it will ease some issues in building enormous branches in moderate sized vms [21:39] jam: yes, apparently conch says "too hard, bye!" [21:39] > bzr branches are too expensive to use for casual sponsoring, compared with downloading packages from my local mirror (slangasek) [21:39] needs to be turned into a proper bug, with a number - can you do that steve? [21:40] (watch file support) - james_w and barry to sprint on that at uds-n [21:40] poolie: couldn't we use stacked branch for that? [21:40] rockin [21:40] flacoste: for what? [21:40] poolie: ack [21:40] poolie: specifically, slangasek bug [21:40] it can be part of the solution [21:40] * flacoste trying to push Tim's bug up the chain :-) [21:41] this is the thing from uds i described as "network performance holistically" [21:41] on bug 295274; i need to get back to that branch [21:41] Launchpad bug 295274 in bzr-builddeb "merge-upstream shouldn't require --version when debian/watch is present" [High,Triaged] https://launchpad.net/bugs/295274 [21:41] https://launchpad.net/bugs/653307 missing chk root keys [21:41] flacoste: the issue raised at UDS is that no matter how little we download, a local mirror is still a lot faster [21:42] (even if we get the download to be ~ the same size as the tarball) [21:42] jam: that's compared to apt-get source right [21:42] right [21:42] right [21:42] right - to be productive I need a good way to have the source already be local [21:42] there was a discussion about being able to list the packages you are interested, and having a cron-ish script keep those up to date in a local mirror/shared repo [21:42] there are a bunch of things we can usefully do - local mirrors, raw speed, etc [21:42] let's give it a number, then split it into bugs for each step [21:43] re the missing chk root keys [21:43] i know spiv was working on this [21:44] he didn't mention it recently; i'm not sure why he stopped [21:44] james_w: do you know? [21:44] no, I don't [21:45] i'll ping on the bug [21:45] I think the immediate cause was his bout of illness [21:45] [ACTION] slangasek to file bug on "bzr branches are too expensive to use for casual sponsoring, compared with downloading packages from my local mirror" [21:45] ACTION received: slangasek to file bug on "bzr branches are too expensive to use for casual sponsoring, compared with downloading packages from my local mirror" [21:45] probably [21:45] poolie: Why does the distro packages file need to know if something was built from branch? [21:46] https://bugs.launchpad.net/bzr/+bug/603395 commit in checkout doesn't propagate tags [21:46] (or flacoste) [21:46] spiv is working on this and i think it should be done soon [21:46] ScottK: simply to allow us to track uptake of UDD across the distro [21:46] ScottK: two things: firstly, to answer "how can i get the exact source for this"; secondly and a bit pragmatically, so we can trace how much of ubuntu is using this [21:47] we should split it out from the 'want a graph' bug [21:47] Right, but making the packages file larger makes apt-get update slower for every single user of Ubuntu. [21:47] true [21:47] Surely there are less invasive ways to track this. [21:47] perhaps it should not propagate to the binary? or perhaps there's a better way? [21:47] there probably is [21:47] i'd love suggestions [21:47] and that's what i meant by making sure it was tasteful [21:48] X-C should be enough, but that might require some special-casing in LP unfortunately [21:48] I think that's better than adding more noise to the Packages files. [21:48] we need to decide what data we want, and then we can come up with a way to allow us to capture it [21:48] ok [21:49] if only there was a forum in which we could discuss what data to capture to ensure we were tracking what we wanted [21:49] there's a bug, let's capture the constraints/ideas there [21:49] https://launchpad.net/bugs/653832 "trying to import version ... again" [21:50] new to me [21:50] that's one that I'm looking at currently [21:50] I know the immediate cause, but I'm a bit worried about what will happen when I unclog the pipe :-) [21:50] cool, thanks [21:51] there's a related thing that's on my plate, which is migrating the package importer onto "proper" is-managed service [21:51] currently in a holding pattern waiting for losa timeslices [21:51] https://launchpad.net/bugs/499684 "Interface to dpkg-buildpackage inconsistent and not well documented" is also new to me [21:52] i think that's ScottK's complaint about -- (one i share :) [21:53] it seems like a good bug report [21:53] it is a bit obscure when explaining how to use the tools to newcomers [21:53] on my changelog "bug" - i haven't hit it again yet, so i'm still waiting for a specific example before i file a bug [21:53] i don't think it should preempt others already in train? [21:53] i should probably remove it from top bugs since it isn't one yet [21:54] i think that's it for bugs, unless anybody has any other comments? [21:55] [TOPIC] * Sponsoring/Patch Pilot [21:55] New Topic: * Sponsoring/Patch Pilot [21:55] please file a bug for the changelog/merge thing when you can describe it [21:55] nothing else from me [21:55] poolie: yep, definitely [21:56] so next week we start the new regime for sponsoring. i'm up on monday and i plan to heavily encourage branches and merge proposals. i'd like to give preferential treatment to reviews in mps. (note though i can only review anyway) [21:57] this'll be a good way to get feedback about sponsoring workflow [21:57] yep, i'll keep copious notes :) [21:58] that's a great idea [21:58] i'll post my thoughts to the udd mlist afterward [21:59] i just wanted to mention this; i don't have much else [21:59] unless anybody has suggestions, or things to emphasize, etc... ? [22:00] [TOPIC] AOB [22:00] New Topic: AOB [22:00] anything else not on the agenda? [22:00] sorry one more [22:00] i'd like to look for someone to do a rotation onto the bzr team, ideally from platform [22:00] to free up some time for them to work on this [22:01] if anyone here is interested in working on something different, that's great [22:01] otherwise, think of someone else you might know who it would suit [22:01] poolie: maybe a solicitation on the platform mlist? (i don't think i can take it on until the py27 transition is done) [22:01] maybe someone who's been working on the same group for a few years and could do with a refresher [22:02] sure, i just thought about it in the shower this morning [22:02] :) [22:02] i will get the idea out there [22:02] good idea [22:02] awesome [22:02] [ACTION] poolie to send bzr rotation pitch to platform list [22:02] ACTION received: poolie to send bzr rotation pitch to platform list [22:02] i'd like to also approach likely candidates individually, if we can get a shortlist [22:04] cool, thanks. any other business? [22:04] i'll just mention https://wiki.ubuntu.com/Bazaar/Plate [22:04] (private only, sorry) [22:04] as a view of what we're up to [22:05] nothing else from me [22:05] I have a merge proposal for barry_, but I think that's a bit to "Other Business" [22:05] poolie, ubuntu.com or canonical.com? [22:06] sorry, canonical [22:06] https://wiki.canonical.com/Bazaar/Plate [22:07] poolie: thanks [22:07] okay, folks. thanks again for another great meeting. see you in two weeks [22:07] #endmeeting [22:07] Meeting finished at 16:07. [22:08] thanks all [22:08] thanks! :) [22:08] thanks:) [22:20] barry_: That's definitely on my list.