=== Varka_ is now known as Varka === ubottu changed the topic of #ubuntu-meeting to: Current meeting: Platform Team | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 28 May 17:00 UTC: Launchpad users meeting | 28 May 21:00 UTC: Server Team | 29 May 01:00 UTC: Americas Ubuntu Membership Approval Board | 29 May 13:00 UTC: Desktop Team | 30 May 12:00 UTC: MOTU [07:00] * ArneGoetje waves [07:00] hi all [07:00] good morning === doko_ is now known as doko [07:01] hi [07:01] Greetings. [07:01] good morning all [07:01] heya all [07:02] I hope everyone had a decent trip back from Prague [07:02] Yes, as well as one can have. [07:03] I can't complain either [07:03] Chris and Steve are on holiday [07:03] * ogra coughs and sniffs [07:05] Prague Plague, ogra? [07:05] bryce, mdz plague i'd say [07:05] ogra: kees too [07:05] seems seb and daniel have it too [07:05] so, first thing is UDS proceedings [07:05] and Jorge and Jono :) [07:05] heh [07:06] I sent out a mail about the reports I dumped into the wiki, and getting those transformed into specs [07:06] does anyone have questions about the process there? [07:06] cjwatson: I've dumped my notes in as well [07:06] No, I only need to try and find the dmraid document that was in gobby. [07:06] And I have the document for the accessibility review of ubuntu specific desktop tools. [07:06] IntrepidReleaseSchedule gives 5 June as the deadline for specs to be finalised [07:06] gobby appears to have been cleared out or something; I couldn't find my xorg ones there [07:06] SO will get to that in the next few days. [07:07] * cjwatson guesses the gobby server crashed and ate its state again [07:08] gobby gobble [07:08] apparently the state is very very tasty [07:08] is it time to spend some effort on gobby reliability? at least having the client autosave, perhaps? [07:08] I was just thinking that, though autosave has its own problems [07:09] afaik Kees took the dmraid notes so he should probably have a copy somewhere. [07:09] preferably server side reliablity, of course [07:09] with the lack of undo, autosave guarantees that nobody has a spare copy if somebody highlights the whole document and starts typing [07:09] autosave; bzr commit [07:09] bzr backing would rock [07:10] I wonder if tweaking the editor to prevent overtyping a selection would be a good idea [07:10] undo would be more awesome [07:10] gobby needs a lot of tender loving care, it seems [07:11] is that the sound of a volunteer? ;-) [07:11] kyllä [07:11] always answer in Finnish to questions about being a volunteer... :) [07:12] (translation for those who are not slangasek: yes, I am willing to volunteer) [07:12] I found http://www.kylla.com/ and my brain melted [07:12] sorry reconnected [07:13] can someone paste the session so far? [07:13] asac, sure, just a moment [07:13] thx [07:13] asac, http://paste.ubuntu.com/15259/ [07:14] I've started trying to put together lists of what people are doing at https://wiki.canonical.com/DistroTeam/Platform/8.10 [07:14] this is horribly incomplete as yet, and even blank for some people [07:14] (and only accessible to Canonical people) [07:15] indeed, it should end up being just an internal-organisation document full of links to the outside world [07:15] I just find it more convenient to plan stuff there than in Launchpad [07:16] cjwatson, edits to that page should be discussed with you beforehand, I assume [07:17] if they're trivial, go ahead, otherwise please ask [07:17] the archive reorg is the biggest unowned item there [07:18] however, for a change, I'm not looking for volunteers for that right now - to start with it isn't really an implementation project on our side [07:18] we much more need to get it specced out and agreed, so that the right changes can be made in Launchpad [07:19] and probably prototyped [07:20] these are only tasks that are directly aimed at 8.10, I assume? [07:20] I will work on that, but it isn't urgent that it lands in this cycle, as long as we get started; in fact it's unlikely to land in this cycle because all the Launchpad people-time has already been assigned [07:20] ArneGoetje: loosely, yes [07:20] ArneGoetje: why? [07:20] so, I don't need to add more long-term stuff to it? === asac_ is now known as asac [07:21] no; I don't have a good place for that, maybe just on your personal wiki page if you want somewhere to aggregate it? [07:21] ok [07:21] or you could create a page linked off DistroTeam/Platform for longer-term ideas [07:22] (actually, any page named DistroTeam/Platform/blah will get magically autolinked) [07:22] well, the point is that I also need to allocate time for those, besides the tasks for 8.10... not that the long-term ones get pushed back... ;) [07:23] ah, right [07:23] send me mail with the details and I'll think about it and get it folded in [07:25] ok. I was just thinking if it would be more useful to have a general overview page what people are working on, with tasks marked as 8.10, long-term or general duties, for example... [07:25] cjwatson: the tasks "upstream bugs/crashers" + "automated testing" belong more to the QA team i guess. should i add them to my list on that platform page anyway? [07:25] asac: I explicitly hadn't included them for you there because I wanted to talk with you first about that :-) [07:26] I'll check up with Henrik about that [07:26] ok [07:26] likewise, compcache is a kernel team item [07:26] not completely [07:26] well, mostly [07:26] it needs udev implementation i volunteered to do [07:27] cjwatson: i also have "large scale extensino maintenance using bzr", which fits nicely into "distributed development" i guess. [07:27] kernel team adds the module to l-u-m, but it needs userspace setup [07:28] asac: new heavy-duty use of bzr in the distro should definitely liaise with james_w to make sure it won't have to be redone in six months' time [07:28] ogra: point me to a spec once there is one [07:28] cjwatson: What do you mean by heavy duty? [07:28] cjwatson, will do [07:29] TheMuso: rolling out new systems for large groups of packages, as opposed to just sticking a stray package here and there in bzr [07:29] (which is obviously to be encouraged) [07:29] cjwatson: Right. [07:29] cjwatson: needs coordination with james_w, right. [07:30] it's unlikely to cause a problem, but James may want to know what you're doing in order to take account of it [07:30] though I see from James' activity report that you've already been talking [07:31] cjwatson: we are already doing that and had discussions on that topic at UDS [07:31] yep [07:33] so, meeting times [07:33] we last rotated these in February [07:34] any reason to change? :) [07:34] from 1500 UTC to 0600 UTC [07:34] ArneGoetje: yes, i finally got used to this time - and that scares me. [07:34] ArneGoetje: I did promise at the time to rotate every few months, to spread out the pain [07:34] asac: LOL [07:35] Wednesday still seems fairly convenient [07:35] so simply rotate another -8 hours? e.g. 22h UTC ? [07:36] is there a time that will allow all of us to be awake at our normal times, rather than two-three hours after normal bedtime? [07:36] 2200 UTC == 0600 Arne's time, if I'm doing my sums correctly [07:36] liw, no there isn't [07:36] liw: I don't think so :-( [07:37] alas [07:37] liw: we cover western and eastern US, Europe, Taiwan, Australia [07:37] in that case, spread the pain [07:37] I'd be happy to move to Australia or Canada, if that helps ;-) [07:37] it's just about pessimal for arranging meetings [07:38] Since I've had it good for the last few months, I'm willing to do whatever is decided upon. [07:38] +1 [07:38] Evan and Chris have probably had it worst [07:38] I like asac's proposal - easy to remember and apply [07:39] ++ [07:39] I think asac's is probably fine though possibly with an hour or so's tweak either way; we settled on 0600 because it was a bit less unpleasant for eastern US [07:40] we could just reshuffle the teams so that the desktop team manager gets to deal with more than just Europe and western US for a change ;-) [07:40] "just" [07:41] do I understand correctly: asac's suggestion would be to have the meeting at Tuesday 22:00 UTC? [07:41] ArneGoetje: on what you said above: I think you're probably right, but I'll have to think on how to do it so as to avoid too much duplication and hence stuff getting out of date [07:42] liw: my idea was Wed 2200 UTC [07:42] cjwatson: got it [07:42] asac, ack [07:42] I'm ok with that [07:43] I'll stare at a timezone map for a bit and send mail, then [07:43] any other business? [07:43] Yes, minutes. [07:43] Wed 22:00 soudns fine [07:43] oh yes, that rather ought to rotate too [07:43] I can do this meeting's minutes, but I would like to share the work around for those. [07:43] volunteers? [07:43] whoever joins the meeting last gets to do the minutes? :) [07:44] earlier I volunteered to help out. I might be out on jury duty part of June though (or maybe not) [07:44] I'd be happy with a setup where the secretary gets chosen randomly at the beginning of each meeting [07:45] Well I'd rather not do them if the meeting ends up at a time which requires me to get up/make myself available for it. [07:45] I don't mind doing such a meeting time, but I'd probably rather not have to worry about minutes for that meeting. [07:46] one does need to be awake; seems best to have it selected from those people for whom it's normal working hours [07:46] TheMuso: yeah that sounds fair [07:46] yeah, that sounds good [07:46] which means bryce is probably a good candidate for this rotation anyway, modulo jury duty [07:46] yup [07:46] done [07:47] any other other business? [07:48] my keyboard battery is about to die... [07:48] so nothing from me [07:48] :) [07:48] nothing from me either [07:49] * ogra will go back to bed and stay there for most of the day to cure that flu ting [07:49] Only that it was great to see everybody face to face once again. :) [07:49] ack++ [07:49] liw: punched cards are the way forward [07:49] yeah [07:49] greatness.lock(); greatness.set_value(greatness.get_value() + 1); greatness.unlock() [07:50] indeed so [07:50] adjourned, then [07:50] thanks [07:50] thanks [07:50] thanks [07:50] thanks [07:50] Thanks. [07:50] kiitos [07:50] thanks === ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 28 May 17:00 UTC: Launchpad users meeting | 28 May 21:00 UTC: Server Team | 29 May 01:00 UTC: Americas Ubuntu Membership Approval Board | 29 May 13:00 UTC: Desktop Team | 30 May 12:00 UTC: MOTU | 31 May 12:30 UTC: Forum Council === asac_ is now known as asac === ubottu changed the topic of #ubuntu-meeting to: Current meeting: Launchpad users meeting | Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 28 May 21:00 UTC: Server Team | 29 May 01:00 UTC: Americas Ubuntu Membership Approval Board | 29 May 13:00 UTC: Desktop Team | 30 May 12:00 UTC: MOTU | 31 May 12:30 UTC: Forum Council [17:59] Anyone? [18:13] @schedule lima [18:13] RoAkSoAx: Schedule for America/Lima: Current meeting: Launchpad users meeting | 28 May 16:00: Server Team | 28 May 20:00: Americas Ubuntu Membership Approval Board | 29 May 08:00: Desktop Team | 30 May 07:00: MOTU | 31 May 07:30: Forum Council [18:14] @schedule houston [18:14] lukehasnoname: Error: Unknown timezone: houston - Full list: http://jussi01.com/web/timezones.html [18:14] haha [18:15] @schedule central [18:15] lukehasnoname: Schedule for Canada/Central: Current meeting: Launchpad users meeting | 28 May 16:00: Server Team | 28 May 20:00: Americas Ubuntu Membership Approval Board | 29 May 08:00: Desktop Team | 30 May 07:00: MOTU | 31 May 07:30: Forum Council [18:15] nice. [18:24] @schedule [18:24] Syntux: Schedule for Etc/UTC: Current meeting: Launchpad users meeting | 28 May 21:00: Server Team | 29 May 01:00: Americas Ubuntu Membership Approval Board | 29 May 13:00: Desktop Team | 30 May 12:00: MOTU | 31 May 12:30: Forum Council [18:26] @schedule montreal [18:26] zul: Schedule for America/Montreal: Current meeting: Launchpad users meeting | 28 May 17:00: Server Team | 28 May 21:00: Americas Ubuntu Membership Approval Board | 29 May 09:00: Desktop Team | 30 May 08:00: MOTU | 31 May 08:30: Forum Council [18:54] @schedule amsterdam [18:54] leoquant: Schedule for Europe/Amsterdam: Current meeting: Launchpad users meeting | 28 May 23:00: Server Team | 29 May 03:00: Americas Ubuntu Membership Approval Board | 29 May 15:00: Desktop Team | 30 May 14:00: MOTU | 31 May 14:30: Forum Council [18:58] @schedule [18:58] fdd: Schedule for Etc/UTC: Current meeting: Launchpad users meeting | 28 May 21:00: Server Team | 29 May 01:00: Americas Ubuntu Membership Approval Board | 29 May 13:00: Desktop Team | 30 May 12:00: MOTU | 31 May 12:30: Forum Council [18:58] @schedule bucharest [18:58] fdd: Schedule for Europe/Bucharest: Current meeting: Launchpad users meeting | 29 May 00:00: Server Team | 29 May 04:00: Americas Ubuntu Membership Approval Board | 29 May 16:00: Desktop Team | 30 May 15:00: MOTU | 31 May 15:30: Forum Council === ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 28 May 21:00 UTC: Server Team | 29 May 01:00 UTC: Americas Ubuntu Membership Approval Board | 29 May 13:00 UTC: Desktop Team | 30 May 12:00 UTC: MOTU | 31 May 12:30 UTC: Forum Council | 04 Jun 16:00 UTC: LoCo Council [19:53] * lukehasnoname says hi [19:58] ahoj! [19:58] * ogasawara_ waves [19:59] * cgregan waves back [20:00] hey! [20:00] Good evening everybody :) [20:00] * stgraber waves [20:01] hi [20:02] * heno tries the bot [20:02] #startmeeting [20:02] hi all [20:02] no bot :( [20:02] hey [20:03] hope everyone who was at UDS made it home ok [20:03] broken bot - sorry, I've got exams at the moment, i'll fix it when they are over [20:03] I'm fine, except the UbuFlu :) [20:03] Seeker`: thanks, no worries [20:03] I'm just with a bit of Ubuflu ;-) [20:03] +1 [20:04] I must be lucky...no Flubuntu here [20:04] Ubuflu is over for me :) but I was only in Prague for a few days [20:04] * heno is UbuFluFree :) [20:04] I even shared a plane with MattZ [20:04] I'm not :D [20:04] * pedro_ spreading lysol [20:04] What meeting is starting? [20:04] lukehasnoname: QA team [20:04] ooo! [20:04] I'm finally recovering from the Prague Plague... [20:04] cgregan: heh, you finally met Matt on the plane home? :) [20:05] This isn't on the calender [20:05] heno: yes...kept my distance though ;-0 [20:05] or is it [20:05] lukehasnoname, it's secret, don't tell anyone :p [20:05] @schedule [20:05] lukehasnoname: Schedule for Etc/UTC: 28 May 21:00: Server Team | 29 May 01:00: Americas Ubuntu Membership Approval Board | 29 May 13:00: Desktop Team | 30 May 12:00: MOTU | 31 May 12:30: Forum Council | 04 Jun 16:00: LoCo Council [20:06] jcastro: you know your way around the Fridge right? Could you look at getting the QA team meeting added on a rolling basis? [20:06] So the first step to being an "Ubuntero" / contributor is universe/multiverse package management? [20:07] I seem to remember the calendar needed hand-cranking each month or something [20:07] heno: I'll look into it [20:07] jcastro: thanks! [20:07] I /think/ they need to be added manually [20:07] ok, let's start [20:07] topic: Intrepid QA schedule [20:07] please see https://wiki.ubuntu.com/QATeam/IntrepidSchedule and raise any objections [20:08] thanks bdmurray for updating it for Intrepid [20:08] looks fine to me [20:08] There is still some filing in to do of the focus [20:09] the developer sprint will be between the 14 and 18 of July, right? [20:09] 1)What is SRU verification? [20:09] briefly. I know I'm new, and I don't want to take too much time [20:09] Looks good [20:09] we should have a point for test case review [20:10] lukehasnoname: Stable Release Update verification [20:10] lukehasnoname: https://wiki.ubuntu.com/StableReleaseUpdates [20:10] 1-2 weeks before Beta IMObefore Beta [20:10] heno: I agree. [20:10] week 20? [20:10] so they get reviewed with Alpha 6? [20:11] sure, ~September 18th seems good [20:11] or 21 after UI freeze? [20:11] after UI freeze, before beta some time [20:12] we should perhaps allow a week for that process [20:12] I updated week 21 w/ test case review [20:12] Alpha 6 is a good time to confirm that its A-ok [20:12] thanks [20:13] that's all I can see for now [20:13] please raise further feedback on the qa list or at next weeks meeting [20:13] topic: Intrepid QA specifications [20:14] we should update https://wiki.ubuntu.com/QATeam/Specs for Intrepid [20:15] deadline is June 5th but allow some time for review [20:15] so we should try to get specs in place by Tuesday in the Review state [20:16] do we have a list of prospective spec titles/stubs? [20:16] topics from here http://people.ubuntu.com/~scott/uds-intrepid/ don't all map well to specs [20:16] indeed [20:16] mgunes: right, so some rejigging will be required [20:17] I'll start updating the spec wiki page with my take on that, but please also add specs you are leading / involved in [20:17] some can be recycles from last cycle [20:18] I'll be quite busy with exams next week so I'd really appreciate anyone helping me spec the QA-Website, QA-Portal, Package website and Brainstorm specs. I'm not sure of the status of the QA-Tracker spec at the moment [20:18] like the desktop testing one [20:18] QA-Website, QA-Portal and QA-Tracker need a spec, not sure about the two others (Brainstorm and app website) [20:19] stgraber: I can help with the QA specs [20:19] stgraber, I can probably help if you share all your local UDS Gobby sessions that I couldn't save :) [20:19] jcastro: I assume you'll keep in touch with stgraber and nand Re the brainstorm stuff [20:19] heno: yep I was just writing the mail in fact [20:20] ah, yes, please help fill the gaps of lost gobby docs generally! [20:20] jcastro: cool! [20:20] so at next weeks meeting we'll focus on getting the specs wrapped up [20:21] I'm hoping to implement a "tester weather report" that I talked briefly about at UDS; will add to the specs page once I have a rough spec + some initial feedback [20:21] mgunes: the gobby session for Brainstorm and AppWebsite are on the wiki, not sure about the QA-Portal one (I may still have it somewhere here) [20:21] (I'm also emailing and phoning various people about this this week) [20:21] how many of you actually went to UDS? [20:21] lukehasnoname: probably all the ones talking [20:21] o_o [20:22] I'm alone in my absence [20:22] we had a good QA showing indeed [20:22] stgraber, I'd appreciate qa-portal one if you can find it [20:23] lukehasnoname: your not I wasn't there either :( [20:23] any more questions about spec writing? [20:23] mgunes: I can't find it on gobby, the wiki or my hdd but I think I emailed it to cr3 so I should find it in my sent mails :) [20:23] mgunes, stgraber: I might have it [20:24] topic: Promoting and tracking the use of proposed [20:24] stgraber, sbeattie, if you do, please forward to me or ping me (and let's use a standard namespace on gobby.ubuntu.com next time) [20:24] sbeattie: cool, mine is pre-UDS so I only have the bits discussed at FOSSCamp :( [20:24] yay for proposed packages [20:24] that was the extending-qa.ubuntu.com session, right? [20:24] please see https://wiki.ubuntu.com/Testing/EnableProposed [20:24] mgunes: I put the one I have in https://wiki.ubuntu.com/QATeam/FossCamp/ [20:24] sbeattie: yes [20:24] i should blog about that... [20:25] stgraber, thanks [20:25] stgraber: yeah, I have it, I'll email. [20:25] note that my test of Apport failed - does anyone know more about that? [20:25] heno: its /etc/default/apport now [20:25] hardy proposed is for the point release? [20:25] heno: what failed ? did you see the point I added to your instructions ? [20:25] If a restart is required I should add that to the page [20:26] modifying /etc/default/apport and running /etc/init.d/apport restart should start it [20:26] an apport restart should do the trick [20:26] right [20:26] stgraber, bdmurray: I did that [20:27] ah! we need to add the /etc/init.d/apport step [20:27] heno: I just ran the commands and nothing happens [20:27] heno: how did you get the smaller picture, it's not obvious to me at the moment [20:28] ok, it works now. I'll update the instructions [20:28] bdmurray: the thumbnai? resize in gimp :) [20:28] thumbnail even [20:28] ah, I thought it was some wiki magic [20:29] bdmurray: would be too easy :) [20:29] bdmurray: no just a lot of time in the gimp and a line of text a mile long ;) [20:30] guys I still can't get apport to run :( [20:30] its legs are tired [20:30] what do people think of tracking -proposed usage in this way? See: https://bugs.edge.launchpad.net/proposed-tracking/+bugs [20:31] If we agree that it's sane I'll blog about it later [20:31] mgunes: could you echo that in a forum thread as well? [20:32] looks good to me [20:32] heno, will do if we decide to go on with it [20:32] mgunes: I actually stole your idea of using a forum sticky with me too comments [20:32] Did we have some discussion about tagging proposed package crashes somehow? If so that should be in those two bug reports. [20:32] Looks good but I don't seem to be able to enable apport still :( [20:33] but I though LP would be good because testers really should have an LP account and have uploaded a HW profile [20:33] heno, cool; improvised solutions can work better than elaborate ones :) [20:34] bdmurray: perhaps we should also link to bug filing guidelines [20:34] heno, but what would be the "more automated solution" mentioned at https://wiki.ubuntu.com/Testing/EnableProposed ? [20:34] mgunes: we discussed at UDS to use popcon to collect the info [20:34] (opt-in obviously) [20:35] but we'll look closer at that post hardy.1 [20:35] ah, ok, I remember [20:35] sbeattie has looked at the code a bit [20:36] ok, we seem agreed. I'll go ahead with that [20:36] please help seed the bugs with your registrations! [20:37] bdmurray: will you add the tag and bug filing doc links to the bug descriptions? [20:37] bdmurray: use whatever tag convention you feel is appropriate [20:37] heno: sure [20:37] thanks [20:38] topic: Can people check out the files under [WWW] https://wiki.ubuntu.com/Testing/Includes please? -- davmor2 [20:38] heno, there's yet no way to query one's own uploaded hardware info (or whether it's uploaded at all) in LP right? [20:38] mgunes: you have to check the non-published URL [20:38] Guys, quick question: Hypothetically, if someone designed a website for Ubuntu that had a system integrating bug tracking, error reporting, wiki, brainstorm, member information, etc., do you think Ubuntu would ipliment it? [20:38] on the form https://launchpad.net/~/+hwdb-submissions [20:39] mgunes: probably not but if your a tester then you can always add your HW spec to your tracker account and that can [20:39] *implement, I'm smarter than I spell [20:39] isn't the last test on the Tomboy page a bit generic? [20:39] lukehasnoname: why would you want to reimplement that? [20:40] heno, found it right after asking, thanks :) [20:40] i mean, that's the goal for almost all the UI applications [20:41] cool :) [20:41] I admit I am no expert at navigating the different sites. Perhaps it is my ignorance. However, it seems that the layout and the ways in which things are done are thrown together [20:41] writing test cases can be hard because you run out of new things to test after a while -- I'm sure additions are welcome :) [20:42] If there were a more structured, planned setup, things might be more navigable / easier to maintain [20:42] I know, I've written some and you find yourself stumped for coming up with interesting ways to test even the simplest applications [20:43] davmor2: cgregan has some stuff on the wiki about testing mobile apps, might be able to steal specific tests from that. [20:43] Now that Ubuntu is becoming larger in the community, it is not so hard to make a plan on a professional, deliberate web environment. [20:43] sbeattie: he and davmor2 have actually worked together on those :) [20:43] sbeattie: I been working on them with him :) [20:44] If I'm hijacking the meeting, I'll stop, I'll just draw up specs myself and see where things go. thanks for bouncing my ideas. [20:44] I think the new test case structure and layout generally rocks! [20:44] though a bit more detail would help in many cases [20:45] pedro_: could you do a review of the desktop cases and add some more steps? [20:45] heno: sure, will do it [20:45] thanks [20:45] np :-) [20:46] ok, any other topics? [20:46] Now how do I contribute to testing? [20:46] I feel a 3 [20:47] er, register for it? [20:47] lukehasnoname: what kind of testing? [20:47] Hardy updates, ISO testing, or mobile perhaps? :) [20:48] https://wiki.ubuntu.com/Testing is a good place to start reading [20:48] in the testing cases for install and desktop [20:48] For mobile: https://wiki.ubuntu.com/Testing/Cases/UMEdesktop [20:49] lukehasnoname: that's install, so you'll need to register at http://iso.qa.ubuntu.com/ [20:49] Let me clarify: Are those for people to test their own software for their own sake, or for testers to verify and report back to Ubuntu QA? [20:49] we actually have proper test tracking for that :) [20:50] to report back that the updated/installed packages work as expected [20:50] looks like we are done with meeting [20:50] thanks everyone! [20:50] thanks [20:50] thanks you [20:50] Every Wednesday at this time? [20:51] thanks [20:51] thanks, see you all [20:51] yay got apport working :) [20:51] take care guys! [20:51] davmor2: cool [20:52] lukehasnoname: you might want to think about joining the #ubuntu-testing channel [20:53] hm, cool [20:53] @schedule [20:53] Daviey: Schedule for Etc/UTC: 28 May 21:00: Server Team | 29 May 01:00: Americas Ubuntu Membership Approval Board | 29 May 13:00: Desktop Team | 30 May 12:00: MOTU | 31 May 12:30: Forum Council | 04 Jun 16:00: LoCo Council [20:53] Now that I have a job I have time to kill on the net studying Ubuntu [20:54] gah, UTC != UTC+1 :( [20:54] pedro_, have a question, at what time is the Americas Membership Board meeting?? because, in the wiki says 00.00 UTC and here 01.00 UTC... [20:54] BTW, My birthday is October 30th, so I expect a damned fine Ibex. [20:54] it's at UTC 00:00 [20:54] It's at 8pm CDT [20:54] don't trust the topic this time ;-) [20:55] I think? [20:55] the right information is available at https://wiki.ubuntu.com/Membership/RegionalBoards/Americas [20:56] pedro_, haha ok thanks ;) [20:57] RoAkSoAx: you're welcome :-) [20:58] pedro_: how many hours is that? ;) [21:02] bdmurray: the meeting? should be like ~1 hour (hope so) [21:02] I really meant hours away [21:03] apparently math and english are hard [21:04] 4 from now on [21:04]