=== yofel_ is now known as yofel === tumbleweed_ is now known as tumbleweed === AndrewMC` is now known as Guest13774 === 50UAAGBPG is now known as Amaranth === juliux is now known as Guest26939 === Guest36926 is now known as IdleOne === JamieBen1ett is now known as JamieBennett === deegee_1 is now known as deegee === javalogger is now known as apachelogger === Guest94281 is now known as niko === lool- is now known as lool === doko_ is now known as doko === RawChid_ is now known as RawChid === Guest13774 is now known as AndrewMC === apachelogger is now known as thresh_fan_fan === chuck_ is now known as zul === thresh_fan_fan is now known as apachelogger === thermi is now known as Thermi === dantaliz1ng is now known as dantalizing === Quintasan_ is now known as Quintasan === jjohansen is now known as jj-afk === Ursinha is now known as Ursinha-afk [16:55] hi [16:57] o/ [16:57] \o\ [16:57] /o/ [16:57] o\ [16:58] \o [17:01] who's on bat? [17:01] hallyn: was it you last week? [17:01] o/ [17:01] no, two or three weeks ago [17:01] who did last week? [17:02] spamaps? [17:02] * hallyn checks the blog [17:02] yes \ [17:02] i think its Daviey this week [17:02] yeah [17:03] Sorry, chaps... was on the phone... I'm back now. [17:03] * hallyn tips his hat [17:03] two moments whilst i compose myself. [17:04] #startmeeting [17:04] Meeting started at 11:04. The chair is Daviey. [17:04] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [17:04] *\o/* [17:04] Hellow everyone, and thank you for coming. Apologies for starting later than scheduled. [17:04] pom poms, robbiew ? [17:04] you know it! [17:04] [TOPIC] Review ACTION points from previous meeting [17:04] New Topic: Review ACTION points from previous meeting [17:05] Daviey to talk with wider docs team regarding translations (deferred, carry over) [17:05] -- This is still carried over. [17:05] Daviey to post another followup one euca-dhcp bug. (carry over) [17:05] -- scheduled to talk with upstream today via phone. [17:05] (and yesterday for that matter) [17:05] SpamapS to put his version of ubuntuserver-minutes in directions for writing minutes [17:05] -- looks done [17:06] [TOPIC] Natty Development [17:06] New Topic: Natty Development === jj-afk is now known as jjohansen [17:06] So, we are in Ubuntu Beta 1 hard freeze. [17:07] Hopefully the ISO building is starting to stabilise, and we should have a potential candidate soon (if not now) [17:07] We could do with some additional testing of these candidates.. [17:07] Daviey: fyi, the aubergine color got dropped from the beta1 debian-installer :-( [17:07] http://people.canonical.com/~platform/workitems/natty/canonical-server-ubuntu-11.04-beta-1.html [17:07] LINK received: http://people.canonical.com/~platform/workitems/natty/canonical-server-ubuntu-11.04-beta-1.html [17:07] Daviey: sort of inadvertent fallout of making it configurable [17:08] how come? [17:08] kirkland, that is a shame... [17:08] Daviey: i'm trying to fix it now [17:08] kirkland, So that will land after beta 1 now? [17:08] Daviey: yes, pray that the fix gets accepted for beta2 [17:08] Daviey: cjwatson said that he's not rebuilding debian-installer for beta1 at this point (understandably) [17:09] kirkland, I hope so! I liked the aubergine love. It was in yesterdays ISO - when was it dropped? [17:09] Daviey: debian-installer rebuilt yesterday, which used the updated newt configuration, where newt's palette is configurable [17:10] Daviey: and that configuration did not propagate to the debian-installer bits [17:10] I see, thanks kirkland - is there a new bug / WI that is tracking this? [17:10] Daviey: i'm trying desparately to get it working [17:10] kirkland, rocking. [17:10] Daviey: i honestly haven't had time to file a bug, focused on fixing it ASAP [17:10] kirkland, ok, sounds good. [17:10] Daviey: but i thought i'd mention it here, thanks [17:10] Okay.. regarding our burn down chart.. [17:11] As we are in freeze now, any items that are in main/multiverse need to be adjusted to beta2 - or discussion if they should be dropped. [17:12] Regarding release bugs... We do have a handful.. they look like they are making progress - so not sure we need to discuss them further here. [17:12] Does anyone else have any comments for Natty development? [17:12] moving on [17:12] [TOPIC] Ubuntu Server Team Events [17:12] New Topic: Ubuntu Server Team Events [17:13] Doesn't look like we have any new ones confirmed in the short term. [17:13] [TOPIC] Weekly Updates & Questions for the QA Team (hggdh) [17:13] New Topic: Weekly Updates & Questions for the QA Team (hggdh) [17:13] This Saturday April 2nd. Texas Linux Fest. kirkland and I are presenting [17:13] Hmm well there is puppet camp at the end of next month [17:13] Daviey: ^^ [17:13] RoAkSoAx, ah, thanks! [17:14] Openstack Summit next month [17:14] Yeah, i thought that was > short term. :) [17:14] it is short term :) [17:14] New Topic: Weekly Updates & Questions for the QA Team (hggdh) [17:15] hggdh, the floor is yours, sir [17:15] hggdh, seems afk... we will come back [17:15] [TOPIC] Weekly Updates & Questions for the Kernel Team (smb) [17:15] New Topic: Weekly Updates & Questions for the Kernel Team (smb) [17:16] smb, Are you around? [17:16] Yes, a bit late but I am here [17:16] smb, bug 740658 and bug 741224 have popped up in the last few days. [17:16] Launchpad bug 740658 in linux-meta-ec2 (Ubuntu) "kernels compiled with"CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y" lead to weird clock drifts on some CPUs. This may up ending in DOS" [Undecided,New] https://launchpad.net/bugs/740658 [17:16] Launchpad bug 741224 in linux-ec2 (Ubuntu) "m1.large instances randomly freezing for 5-15 minutes" [Undecided,New] https://launchpad.net/bugs/741224 [17:16] Mostly being trying to bring lucid-ec2 into shape [17:16] both with a fair amount of helpful information. [17:17] * Daviey looks [17:17] just wanted to make sure you'd read through them, one follows through to upstream thread https://patchwork.kernel.org/patch/629361/ [17:18] I think I had been looking at them. But I cannot say for sure exactly how things were there [17:18] smb / smoser: So the main issues with EC2 kernel is with Lucid, not Natty? [17:18] I need to get back tehere again [17:18] Daviey, There is one for natty afaik [17:18] Daviey, the issues are present in all releases. [17:18] :-( [17:18] the java not being installable on t1.micro [17:19] But other things tend to go quite a bit back [17:19] smb, is java on t1.micro looking good for Natty? [17:19] Daviey, no the other way round [17:19] it is not looking good for natty [17:19] but I had not yet time to look back into that [17:20] smb, ok, thanks [17:20] smoser, anything else for EC2? [17:20] There is one set of patches turning up a lot which changes the way interrupts are handled [17:20] * hggdh is back from a phone call [17:20] unfortunately those are not really triviall to get back to Lucid (not to mention hardy) [17:21] both t1.micro/java and those listed above are at least potentially bugs on all releases. i fully trust smb, its just a matter of hours in the day, and as he suggests nothing is trivial [17:21] But at least natty should be fine in that respect [17:21] smb, I'm not sure our users would be too concerned with the fix landing in Hardy tbh. [17:21] Daviey, there has been asking [17:21] there are some users who are interested in hardy fixes [17:21] oh. [17:22] smb, I was trying to make your life easier. :) [17:22] Nothing is impossible for the one that not has to do it. :) [17:22] has there been an update kernel for hardy yet? [17:22] Anyway those may go to Lucid [17:22] But then I still have to get that into there as well [17:23] Okay... are there any pressing issues for non-ec2 kernels atm? [17:23] zul, There has been no update to xen speciafically [17:23] smb: cool [17:23] I am not sure whether there has not been other changes in between though [17:24] kernel related.... john johansen sent a mail to ubuntu-server mailing list [17:24] asking for input on -virtual kernel. [17:24] yes! [17:24] yep [17:24] please, if the -virtual kernel has affected you, please speak up there. [17:24] zul, Actually, maybe you want to check whether you got the same amount of patches in your packatge [17:24] * jjohansen was waiting to pitch it [17:24] https://lists.ubuntu.com/archives/ubuntu-server/2011-March/005348.html [17:24] smb: lets take it off line [17:24] There may have been something needing fix for a cve but I lost a bit track of time [17:24] ok [17:25] jjohansen, Do you want to speak? [17:25] jjohansen, go [17:25] zul, fyi, hggdh has info on hardy kernel updates as well. [17:25] Daviey: not really, I was just going to do a one more thing. The kernel team is looking for kernel input, please reply to the mail, or hunt me down [17:26] I think its been covered [17:26] super, thanks! [17:26] It's good to see there is not much concern with the tradional kernel for natty.. [17:26] * Daviey is happy [17:26] Thanks smb and jjohansen ! [17:26] [TOPIC] Weekly Updates & Questions for the QA Team (hggdh) [17:26] New Topic: Weekly Updates & Questions for the QA Team (hggdh) [17:27] hggdh, floor is yours, sir! [17:27] thanks [17:27] we are busy on ISO testing; also still working on the Euca bug [17:27] no news there yet [17:28] smoser: ec2 images ready for ISO testing? [17:28] hggdh, yes. [17:28] * Daviey has been working with hggdh to try and resolve the euca bug. [17:28] jamespage, is working on this , we're attempting to test through jenkins with the work eh's done there. [17:29] jamespage, Do you want to comment on the jenkins testing? [17:29] yep [17:30] so I executed a full set of tests this afternoon; its thrown up a couple of minor bugs with the testing framework which I will fix ASAP. [17:30] Results here -> http://jenkins.qa.ubuntu-uk.org/view/natty-ec2/ if anyone wants to take a look [17:30] jamespage / smoser: Is this expected to be the primary testing, or will traditional testing still be conducted for b1? [17:30] jamespage: can we consider these results as the "official beta" results? [17:31] heh [17:31] leaning torwards this being primary [17:31] +1 [17:31] That should be a good time saving! [17:31] They are against 20110329 [17:31] so we will need to run again [17:31] OK [17:31] Suggest I fix issues [17:31] (not really much time saving... the other tests were all automated as well) [17:31] I *think* we now have the final ISO -- the .2 [17:32] and they re-run once we think we have a good image for beta 1 [17:32] (candidate) [17:32] jamespage, Are they triggered automatically? [17:32] Daviey: yes indeed, the final, er, candidate [17:32] heh [17:32] No - thats intentional as they cost $$ to execute. [17:33] ok, so smoser pings you to fire them? [17:33] At the moment they have to be submitted individually (which is a bit of a pain) [17:33] Yes - thats fine. [17:33] groovy. [17:33] Anything else for hggdh, or QA related? [17:34] .. from me [17:34] hggdh, super... thanks.. I think we'll be talking more this week. :) [17:34] moving on... [17:34] well, since we're there. [17:34] hold on [17:34] smoser, go [17:34] so is there anything anyone knows about that should cause respin of 20110329 uec images ? [17:35] (built on taht date ~ 1:00 am UTC) [17:35] manifest http://uec-images.ubuntu.com/server/natty/current/natty-server-uec-amd64.manifest [17:36] smoser, Have you already tested those? [17:36] that is what jamespage ran a test on. [17:36] ah [17:37] nothing of interest has changed AFAIK. [17:38] moving on. [17:38] [TOPIC] Weekly Updates & Questions for the Documentation Team [17:38] New Topic: Weekly Updates & Questions for the Documentation Team [17:38] We do have quite alot of docs to do before release. [17:38] We need to review the current documentation. [17:38] and some people have WI for new docs. [17:39] [ACTION] Please review the current documentation. [17:39] ACTION received: Please review the current documentation. [17:39] what about the inclusion of new documentation [17:39] Hopefully we'll be able to touch some docs before next meeting.. if we comment next meeting what we have done, that will help. [17:40] RoAkSoAx, Yes, if the current documentation is weak in an area, it needs new documentation :) [17:40] [TOPIC] Weekly Updates & Questions from the Ubuntu Community [17:40] New Topic: Weekly Updates & Questions from the Ubuntu Community [17:40] Daviey: I mean completely new documentation that I'd like to include [17:41] RoAkSoAx, Yes, is that on one of the WI's? [17:41] Daviey: I would love to include Cluster Docs [17:41] Daviey: which I have made available at: https://wiki.ubuntu.com/ClusterStack/Natty [17:42] RoAkSoAx, That sounds like a good idea.. do you know how to submit it? [17:42] Daviey: nope, that's why I was asking :) [17:43] RoAkSoAx, Okay, I'll take the action of providing guidance to -server ml. [17:43] cool ;) [17:43] (I need to check with the docs team, anyway) [17:43] [ACTION] Daviey to talk with docs team about new submissions. [17:43] ACTION received: Daviey to talk with docs team about new submissions. [17:44] [TOPIC] Weekly Updates & Questions from the Ubuntu Community [17:44] New Topic: Weekly Updates & Questions from the Ubuntu Community [17:44] Is there anything new here? [17:44] any new contributors want to say hello? :) [17:45] [TOPIC] Open Discussion [17:45] New Topic: Open Discussion [17:45] Anyone have anything else to add? [17:46] Daviey is the new Ubuntu Server Technical Lead [17:46] whoohoo [17:46] heh [17:46] \o/ [17:46] STC. :) [17:46] \o/ - congrats Daviey [17:46] * Daviey blushes. [17:47] moving on gracefully. [17:47] [TOPIC] Announce next meeting date and time [17:47] Tuesday, April 5 2011 16:00 UTC [17:47] New Topic: Announce next meeting date and time [17:47] congrats [17:47] * robbiew begins the delegations of time waisting work and meanless duties [17:47] meaningless [17:48] oh joy [17:48] #endmeeting [17:48] Meeting finished at 11:48. [17:58] o/ [17:58] \o [17:58] * tgardner waves [17:58] \o [17:58] o/ [17:58] o/ [17:59] * smb is here [17:59] * ogasawara waves [18:00] #startmeeting [18:00] Meeting started at 12:00. The chair is bjf. [18:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [18:00] ## [18:00] ## This is the Ubuntu Kernel Team weekly status meeting. [18:00] ## [18:00] [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting [18:00] [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty [18:00] LINK received: https://wiki.ubuntu.com/KernelTeam/Meeting [18:00] LINK received: https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty [18:00] # Meeting Etiquette [18:00] # [18:00] # NOTE: '..' indicates that you are finished with your input. [18:00] [TOPIC] Release Metrics (JFo) [18:00] New Topic: Release Metrics (JFo) [18:00] Release Meeting Bugs (6 bugs, 8 Blueprints) [18:00] ==== Beta 1 Milestoned Bugs (59 across all packages (down 29)) ==== [18:00] * 4 linux kernel bugs (no change) [18:00] * 0 linux-ti-omap bugs (no change) [18:00] * 0 linux-meta-ti-omap bug (no change) [18:00] ==== Release Targeted Bugs (274 across all packages (up 1)) ==== [18:00] * 22 linux kernel bugs (up 2) [18:00] * 0 linux-ti-omap bugs (no change) [18:00] * 0 linux-meta-ti-omap bug (no change) [18:00] ==== Milestoned Features ==== [18:00] * 7 blueprints (Including HWE Blueprints) [18:01] ==== Maverick Updates Bugs ==== [18:01] * 60 Linux Bugs (down 13) [18:01] ==== Lucid Updates Bugs ==== [18:01] * 94 Linux Bugs (no change) [18:01] ==== Bugs with Patches Attached:84 (up 1) ==== [18:01] * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]] [18:01] * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]] [18:01] .. [18:01] [TOPIC] Blueprints: Natty Bug Handling (JFo) [18:01] [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling [18:01] New Topic: Blueprints: Natty Bug Handling (JFo) [18:01] LINK received: https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling [18:01] * I am reviewing the items this week (had planned to do last week, but didn't get to it) [18:01] to determine what, if any, items need to be postponed or require further discussion at UDS. There [18:01] are several items that are relatively straightforward and simply need to have the time allotted [18:01] for them to be completed. I'll plan and implement that schedule for myself also this week. [18:01] .. [18:02] [TOPIC] Status: General Natty (apw / ogasawara) [18:02] New Topic: Status: General Natty (apw / ogasawara) [18:02] Beta-1 is this Thursday, March 31. Beta-1 will ship with the 2.6.38-7.39 kernel which is based on mainline v2.6.38. Do not expect any further uploads of the kernel until after Beta. In the mean time we've been queueing patches in the master-next branch including rebasing to the most recent 2.6.38.2 stable update. Also keep in mind that Kernel Freeze is April 14, ~2weeks away. After kernel freeze we will transition t [18:02] o our SRU policy when submitting and accepting patches. See: [18:02] [LINK] https://wiki.ubuntu.com/KernelTeam/KernelUpdates and [18:02] [LINK] https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat [18:02] LINK received: https://wiki.ubuntu.com/KernelTeam/KernelUpdates and [18:02] LINK received: https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat [18:02] I'd like to also note that Kernel Freeze is also the same date as Beta 2. Any uploads beyond that would likely have to be of the kitten killing nature. [18:02] .. [18:03] [TOPIC] Status: Stable Kernel Team (sconklin / bjf) [18:03] New Topic: Status: Stable Kernel Team (sconklin / bjf) [18:03] || [18:03] || We are extending the verification phase of this kernel cycle to two weeks in order to resync with master [18:03] || Natty interlock schedule. [18:03] || [18:03] || Due to a shortage of testing resources and testing required for the upcoming Natty release, there will [18:03] || not be a normal two-week kernel release cadence for the next few weeks. The schedule is as follows: [18:03] || [18:03] || kernel (maverick, lucid) -> proposed 3/25 [18:03] || verification in progress this week [18:03] || hw cert/qa - 4/1-4/7 [18:03] || kernel (maveric, lucid) -> update 4/7 [18:03] || kernel ( maverick, lucid?)-> proposed 4/22 [18:03] || verification 4/25-4/29 [18:03] || hw cert/qa - 4/29 - 5/5 [18:03] || kernel (maverick, lucid? ) to update 5/5 [18:03] || [18:03] || * We will complete verification (or revert of patches) by this Friday for the current kernels. [18:03] || [18:03] || * We will have no uploads on the 8th of April, effectively skipping one of the two week [18:03] || cycles that we have been on. [18:03] || [18:03] || * We will upload Maverick and Lucid to -proposed on Friday, April 22 [18:03] || [18:03] || We still have not found the root cause of a build failure for the hppa architecture for the Hardy [18:03] || linux-backports-modules package. This must be understood and resolved before we can release the [18:03] || Hardy kernel packages, so if it is not resolved by the end of this week we will have to delay [18:03] || the testing phase for Hardy until we understand it. [18:03] .. [18:04] * tgardner is working on it... [18:04] [TOPIC] Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf) [18:04] New Topic: Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf) [18:04] || Package || Upd/Sec || Proposed || TiP || Verified || [18:04] || || || || || || [18:04] || dapper linux-source-2.6.15 || 2.6.15-57.94 || 2.6.15-57.95 || 0 || 0 || [18:04] || || || || || || [18:04] || hardy linux-restricted-modules-2.6.24 || || 2.6.24.18-29.9 || 0 || 0 || [18:04] || --- linux-ubuntu-modules-2.6.24 || 2.6.24-28.47 || 2.6.24-29.49 || 0 || 0 || [18:04] || --- linux-backports-modules-2.6.24 || 2.6.24-28.37 || 2.6.24-29.39 || 0 || 0 || [18:04] || --- linux-meta || 2.6.24.28.30 || 2.6.24.29.31 || 0 || 0 || [18:04] || --- linux || 2.6.24-28.86 || 2.6.24-29.88 || 3 || 3 || [18:04] || || || || || || [18:04] || karmic linux-ec2 || 2.6.31-308.28 || 2.6.31-308.29 || 1 || 1 || [18:05] || --- linux || 2.6.31-23.74 || 2.6.31-23.75 || 1 || 1 || [18:05] || || || || || || [18:05] || lucid linux-ec2 || 2.6.32-314.27 || 2.6.32-315.28 || 5 || 4 || [18:05] || --- linux-ports-meta || 2.6.32.30.23 || 2.6.32.31.23 || 0 || 0 || [18:05] || --- linux-meta-lts-backport-maverick || 2.6.35.25.36 || 2.6.35.28.37 || 0 || 0 || [18:05] || --- linux-lts-backport-maverick || 2.6.35-25.44~lucid1 || 2.6.35-28.50~lucid1 || 13 || 12 || [18:05] || --- linux-backports-modules-2.6.32 || 2.6.32-30.29 || 2.6.32-31.31 || 0 || 0 || [18:05] || --- linux-firmware || 1.34.4 || 1.34.7 || 1 || 1 || [18:05] || --- linux || 2.6.32-30.59 || 2.6.32-31.60 || 5 || 4 || [18:05] || --- linux-meta || 2.6.32.30.36 || 2.6.32.31.37 || 0 || 0 || [18:05] || --- linux-meta-ec2 || 2.6.32.314.15 || 2.6.32.315.16 || 0 || 0 || [18:05] || || || || || || [18:05] || maverick linux-backports-modules-2.6.35 || 2.6.35-28.19 || 2.6.35-28.20 || 0 || 0 || [18:05] || --- linux || 2.6.35-28.49 || 2.6.35-28.50 || 5 || 4 || [18:05] || || || || || || [18:05] http://people.canonical.com/~kernel/reports/versions.html has ner-live version information [18:05] LINK received: http://people.canonical.com/~kernel/reports/versions.html has ner-live version information [18:05] .. [18:06] [TOPIC] Incoming Bugs: Regressions (JFo) [18:06] New Topic: Incoming Bugs: Regressions (JFo) [18:06] Incoming Bugs [18:06] 453 Natty Bugs (up 94) [18:06] 1238 Maverick Bugs (up 6) [18:06] 1053 Lucid Bugs (up 8) [18:06] Current regression stats (broken down by release): [18:06] ==== regression-update ==== [18:06] * 42 maverick bugs (no change) [18:06] * 76 lucid bugs (up 1) [18:06] * 7 karmic bugs (no change) [18:06] * 0 hardy bugs (no change) [18:06] ==== regression-release ==== [18:06] * 217 natty bugs (up 55) [18:06] * 239 maverick bugs (down 3) [18:06] * 222 lucid bugs (up 1) [18:06] * 38 karmic bugs (no change) [18:06] * 2 hardy bugs (no change) [18:06] ==== regression-proposed ==== [18:06] * 10 natty bugs (up 2) [18:06] * 0 maverick bugs (no change) [18:06] * 0 lucid bugs (no change) [18:06] * 0 karmic bug (no change) [18:06] .. [18:07] [TOPIC] Incoming Bugs: Bug day report (JFo) [18:07] New Topic: Incoming Bugs: Bug day report (JFo) [18:07] nothing to report on until next week. [18:07] .. [18:07] [TOPIC] Triage Status (JFo) [18:07] New Topic: Triage Status (JFo) [18:07] Another pretty slow week for triage. [18:07] .. [18:07] [TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/) [18:07] New Topic: Open Discussion or Questions: Raise your hand to be recognized (o/) [18:08] thanks everyone [18:08] #endmeeting [18:08] Meeting finished at 12:08. [18:08] thanks bjf [18:08] Thanks! [18:08] thanks bjf [18:56] o/ [18:58] * stgraber waves [18:58] my first meeting in a month [19:00] not that we actually had many others ;) [19:00] * wendar waves [19:00] last one we were only two attending [19:00] hehe [19:00] well I had tests [19:00] I guess we might need to restaff the ARB [19:00] and now a job :) [19:01] as pretty much everyone is busy with a lot of other things and we aren't that many on the board [19:01] well im good to go from here on in [19:01]