== Meeting information == * #ubuntu-meeting: ubuntu-server-team, 11 Jun at 16:01 — 16:24 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-11-16.01.log.html]] == Meeting summary == === Review ACTION points from previous meeting === The discussion about "Review ACTION points from previous meeting" started at 16:01. * ''ACTION:'' (carried over) arosales: create a overview topic bp for servercloud === Saucy Development === The discussion about "Saucy Development" started at 16:03. * ''ACTION:'' everyone look over blueprints one more time === Ubuntu Server Team Events === The discussion about "Ubuntu Server Team Events" started at 16:08. === Weekly Updates & Questions for the QA Team (plars) === The discussion about "Weekly Updates & Questions for the QA Team (plars)" started at 16:09. === Weekly Updates & Questions for the Kernel Team (smb) === The discussion about "Weekly Updates & Questions for the Kernel Team (smb)" started at 16:10. === Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak) === The discussion about "Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)" started at 16:14. * ''ACTION:'' rbasak to follow up on go 1.1. saucy arm issue === Open Discussion === The discussion about "Open Discussion" started at 16:15. * ''ACTION:'' rbasak consider telling hallyn to add a todo item to meeting checklist to remind meeting chair about the wiki page checklist. === Announce next meeting date, time and chair === The discussion about "Announce next meeting date, time and chair" started at 16:23. == Vote results == == Action items == * (carried over) arosales: create a overview topic bp for servercloud * everyone look over blueprints one more time * rbasak to follow up on go 1.1. saucy arm issue * rbasak consider telling hallyn to add a todo item to meeting checklist to remind meeting chair about the wiki page checklist. == Action items, by person == * arosales * (carried over) arosales: create a overview topic bp for servercloud * hallyn * rbasak consider telling hallyn to add a todo item to meeting checklist to remind meeting chair about the wiki page checklist. * rbasak * rbasak to follow up on go 1.1. saucy arm issue * rbasak consider telling hallyn to add a todo item to meeting checklist to remind meeting chair about the wiki page checklist. == People present (lines said) == * hallyn (66) * Daviey (30) * rbasak (18) * arosales (9) * plars (9) * meetingology (7) * smb (6) * ubottu (3) * jamespage (2) * adam_g_ (1) == Full Log == 16:01 #startmeeting ubuntu-server-team 16:01 Meeting started Tue Jun 11 16:01:05 2013 UTC. The chair is hallyn. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 16:01 16:01 Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired 16:01 #topic Review ACTION points from previous meeting 16:01 o/ 16:01 \o 16:01 (carried forward) arosales to follow up with Norvald regarding SRU 16:01 hallyn, I still have to todo to create a server cloud burndown. I am working on it now. should have an a topic by eod. 16:01 hallyn, that one can be removed 16:01 cool, thanks 16:02 arosales: thanks 16:02 arosales create a overview topic bp for servercloud 16:02 oh that's that 16:02 arosales: the bp one can be removed, wht about the SRU item? 16:02 hallyn, reverse 16:02 * hallyn confused 16:02 ok 16:02 sru can be removed 16:02 topic can stay 16:03 to ensure I get it done :-) 16:03 but you intend to get that done today 16:03 hallyn, correct 16:03 #action (carried over) arosales: create a overview topic bp for servercloud 16:03 * meetingology (carried over) arosales: create a overview topic bp for servercloud 16:03 #topic Saucy Development 16:04 Release Tracking Bug Tasks - http://reports.qa.ubuntu.com/reports/rls-mgr/rls-s-tracking-bug-tasks.html#server 16:04 there are 4 critical bugs in that link 16:04 bug 1175028 16:04 bug 1175028 in mongodb (Ubuntu Saucy) "Mongodb links GPL code with SSL" [Critical,Confirmed] https://launchpad.net/bugs/1175028 16:04 defer 16:04 currently being discussed by TB 16:04 ok, bug 1176686 16:04 bug 1176686 in qtchooser (Ubuntu Raring) "qtchooser does not properly work with multiarch" [Critical,Triaged] https://launchpad.net/bugs/1176686 16:05 is that server? 16:05 hallyn: nah 16:05 ok, bug 969733 16:05 bug 969733 in oss4 (Ubuntu Precise) "oss4-dkms 4.2-build2005-2ubuntu1: oss4 kernel module failed to build (cp: cannot stat `/lib/modules/3.2.0-23-generic/source/include/linux/limits.h': No such file or directory)" [Undecided,In progress] https://launchpad.net/bugs/969733 16:05 also not server i'm guessing 16:06 ok, so nm the critical ones - anything you wanted to bring up here, Daviey? 16:06 Nope. :) 16:06 Things seem to be progressing well. 16:06 Just really, make sure bluepritns are totally nailed. :) 16:07 are there any that are worrying you? 16:07 And do add WI's as more stuff appears 16:07 hallyn: not specifically 16:07 hm, yeah i might have some WIs to add... 16:07 ok, do you want an action to do one more once-over on all our blueprints,? 16:08 #action everyone look over blueprints one more time 16:08 * meetingology everyone look over blueprints one more time 16:08 #topic Ubuntu Server Team Events 16:08 anything coming up? 16:08 Nothing I can think of.. 16:08 arosales: know of anything? 16:09 ok, moving on 16:09 #tpic Weekly Updates & Questions for the QA Team (plars) 16:09 bleh 16:09 #topic Weekly Updates & Questions for the QA Team (plars) 16:09 plars: all well? 16:09 nothing big from me at the moment, there were some failures late last week with the server image 16:09 but all is well now 16:09 except the floodlight test still of course 16:09 Daviey, for events just oscon coming up 16:09 awesome. questions for plars? 16:09 kernel team has a kernel to bisect for that 16:10 going to try to get to it this week if I can, but the other guy that does production qa (psivaa) is out right now 16:10 so I'm covering a lot at the moment 16:10 will get to it as soon as I can 16:10 thanks, plars 16:10 plars: Thanks for the update 16:10 #topic Weekly Updates & Questions for the Kernel Team (smb) 16:10 Kernel is good (until we slap in 3.10 at least). Questions? 16:10 your irc comment pasting reflex time may be better than the brake reflex time of most drivers around here 16:10 smb: Are kernel uploads being regression tested against dkms packages yet? 16:11 Daviey, Have you told us which? 16:11 Officially I mean 16:11 Or better plars 16:11 smb: When this was last discussed, i suggetsed all dkms packages 16:12 * 16:12 smb: jibel mentioned yesterday that he has a prototype of this, not sure on the details other than that 16:12 At least having a documented history of when the regression was introduced has value. 16:12 This would be a few and maybe not all with a naming scheme to detect and not necessarily server related 16:12 plars: Oh splendid. Can you find out the details for next weeks meeting please? 16:13 Daviey: why wait a week? I'll either send smb an email, or have jibel do it since he's closer to the action on that piece 16:13 smb: Right, it's not actually that many. Listing the reverse dependencies of dkms itself should suffice 16:13 plars, Sounds good 16:13 no action needed for that? 16:14 ok, moving on 16:14 plars: pls keep me in the loop 16:14 #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak) 16:14 Nothing new to report. Any questions for me? 16:14 hi rbasak 16:14 rbasak, is the go 1.1 issue in saucy resolved now? 16:14 * jamespage is being lazy 16:14 Oh, good question. I don't think there's been any progress on it. I need to follow up. 16:15 rbasak: How are the arm saucy images looking? 16:15 * rbasak makes a note 16:15 #action rbasak to follow up on go 1.1. saucy arm issue 16:15 * meetingology rbasak to follow up on go 1.1. saucy arm issue 16:15 thanks, moving on in 3, 16:15 2, 1, 16:15 #topic Open Discussion 16:16 anything? 16:16 \o 16:17 Just a note for meeting chairs, while they're all here. 16:17 There's been some confusion lately about what needs to be done after a meeting. 16:17 good thinking 16:17 There's a good list in the Knowledgebase 16:17 I just wanted to point out that the steps are enumerated at the bottom of https://wiki.ubuntu.com/ServerTeam/KnowledgeBase 16:17 Right. 16:17 yes, everyeone please follow that and fill in if anything is missing 16:18 I think we've done a good job of keepign it uptodate 16:18 thanks rbasak. is there anything in particular that isn't being done? 16:18 (regularly) 16:18 specifically, "move yourself to the back" hasn't been done for a while it seems 16:18 Sometimes minutes aren't being done also. 16:19 It causes confusion in subsequent meetings, since action items go missing or are from older meetings that have already been resolved. 16:19 i think it might help if we say it should be done by either thu or friday 16:19 I think it's just due to all chairs not knowing that the process is documented. 16:19 So now it's documented :) 16:19 once it gets into monday, i think ppl feel that it's too late 16:20 but i'll wait for someone else to recommend that :) moving on? 16:20 I think part of the problem is that individually we chair quite infrequently 16:20 +1 16:20 feels frequent to me :) 16:20 A reminder at the end of the meeting might help. Perhaps we could add it as a standing action item in the agenda? 16:20 rbasak: Fancy being the resident chair? :) 16:21 * hallyn takes a step back and admires rbasak's team spirit 16:21 :) 16:21 As resident chair, I delegate the task of doing this week's minutes to hallyn :-P 16:21 rbasak: a remidner at most should consist of a pointer to the wiki page 16:21 +1, super 16:22 remember, moin minutes are generated courtesy of meetingology. 16:22 yeah but i prefer manually generated, actually meaningful notes 16:22 moin generated ones aren't actually helpful imo. just to fill in a chekcmark in your todo list 16:22 True. 16:22 I use the moin notes as a starting point 16:23 But one step at a time. Step 1: do something for the minutes. Anything. 16:23 The chair can take care to word their action points suitably to make a more useful autogenerated moin output 16:23 #action rbasak consider telling hallyn to add a todo item to meeting checklist to remind meeting chair about the wiki page checklist. 16:23 * meetingology rbasak consider telling hallyn to add a todo item to meeting checklist to remind meeting chair about the wiki page checklist. 16:23 I'll do it now :) 16:23 INVALID 16:23 all right, moving on, 16:23 #topic Announce next meeting date, time and chair 16:24 same time, same place? 16:24 That'll be next tuesday, June 18 at 16:00 UTC in #ubuntu-meeting. 16:24 thanks, everyone. 16:24 thanks for charing hallyn :-) 16:24 thanks for chairing hallyn 16:24 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)