#title #ubuntu-meeting Meeting Meeting started by s3h at 16:01:01 UTC. The full logs are available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-22-16.01.log.html . == Meeting summary == *Review ACTION points from previous ''LINK:'' https://blueprints.launchpad.net/~ubuntu-server/+specs?role=drafter (Daviey, 16:04:06) ''LINK:'' https://blueprints.launchpad.net/~james-page/+specs?searchtext=servercloud-q&role=assignee (Daviey, 16:04:12) ''LINK:'' https://blueprints.launchpad.net/~james-page/+specs?searchtext=servercloud-q&role=assignee (s3h, 16:04:57) ''LINK:'' http://people.canonical.com/~davewalker/delta.html (Daviey, 16:06:53) ''ACTION:'' zul talk to arosales and jamespage offline about SRU tracker (s3h, 16:07:05) *Quantal Development ''ACTION:'' zul to also pull Ursinha into SRU tracker talks (s3h, 16:08:28) *Ubuntu Server Team Events *Weekly Updates & Questions for the Kernel Team (smb) ''LINK:'' http://people.canonical.com/chucks/libvirt (s3h, 16:29:37) *Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak) *Open Discussion ''LINK:'' https://wiki.ubuntu.com/MainInclusionProcess and https://wiki.ubuntu.com/UbuntuMainInclusionRequirements should be reviewed by interested people (jdstrand, 16:37:18) ''ACTION:'' email arosales/Daviey if interested in ubuntu-mir membership (s3h, 16:38:20) ''ACTION:'' arosales to follow up with Ursinha on best approach for blueprint management this cycle (s3h, 16:46:18) *Announce next meeting date and time Meeting ended at 16:51:06 UTC. == Votes == == Action items == * zul talk to arosales and jamespage offline about SRU tracker * zul to also pull Ursinha into SRU tracker talks * email arosales/Daviey if interested in ubuntu-mir membership * arosales to follow up with Ursinha on best approach for blueprint management this cycle == Action items, by person == * arosales ** zul talk to arosales and jamespage offline about SRU tracker ** email arosales/Daviey if interested in ubuntu-mir membership ** arosales to follow up with Ursinha on best approach for blueprint management this cycle * Daviey ** email arosales/Daviey if interested in ubuntu-mir membership * jamespage ** zul talk to arosales and jamespage offline about SRU tracker * Ursinha ** zul to also pull Ursinha into SRU tracker talks ** arosales to follow up with Ursinha on best approach for blueprint management this cycle * zul ** zul talk to arosales and jamespage offline about SRU tracker ** zul to also pull Ursinha into SRU tracker talks == People present (lines said) == * s3h (75) * SpamapS (56) * arosales (23) * zul (22) * Daviey (19) * jdstrand (16) * Ursinha (15) * rbasak (9) * jamespage (8) * smoser (7) * ubottu (7) * meetingology (7) * roaksoax (5) * smb (4) * hggdh (4) * jimbaker` (3) * m_3 (3) * lynxman (1) * utlemming (1) == Full Log == 16:01:01 #startmeeting 16:01:01 Meeting started Tue May 22 16:01:01 2012 UTC. The chair is s3h. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 16:01:01 16:01: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:39 #TOPIC Review ACTION points from previous 16:02:12 sigh, bad lag 16:02:16 jamespage to send out an email to ubuntu-server about the new template 16:02:28 done 16:02:38 sweet 16:02:49 daviey update release bugs for quantal 16:03:21 Daviey: ^ 16:03:38 * utlemming has a conflict 16:04:01 hye 16:04:03 Hey 16:04:06 The spec's which are currently under consideration are: 16:04:06 https://blueprints.launchpad.net/~ubuntu-server/+specs?role=drafter 16:04:06 If there is a spec you are watching that is not on this list, please make it known. 16:04:08 heeeeeylo 16:04:09 The Spec's that people are responsible for driving to Approved state are, for example: 16:04:12 https://blueprints.launchpad.net/~james-page/+specs?searchtext=servercloud-q&role=assignee 16:04:15 Note, that 'Assignee' actually means the person responsible for driving the WI *specifications* (and getting the blueprint Approved).. *NOT* necessarily doing the tasks. :) 16:04:18 I went through them earlier today, and most are in a pretty good state. However, please can those that require review (to be Approved), please be set to 'Review' state please. 16:04:30 Any questions about Spec state? 16:04:31 o/ 16:04:37 LINK https://blueprints.launchpad.net/~james-page/+specs?searchtext=servercloud-q&role=assignee 16:04:55 ^^ obv, switch out james-page for $launchpad-id 16:04:57 #LINK https://blueprints.launchpad.net/~james-page/+specs?searchtext=servercloud-q&role=assignee 16:05:12 thanks Daviey 16:05:17 zul 16:05:27 hmm? 16:05:31 zul talk to arosales and jamespage offline about SRU tracker 16:05:35 havent done yet 16:05:37 jamespage: did zul sync up with you? If not, I'll need to catch up with zul. 16:05:44 ah ok 16:05:53 I'll catch up with you later zul 16:05:59 oh no! 16:06:04 (null) 16:06:10 zul: you can't run.. your knee :P 16:06:11 Regarding Development for Quantal... Are people frantically working on Merges? 16:06:19 knee is fine :P 16:06:33 o/ (sorry for the tardiness) 16:06:34 Are we not using the bot? 16:06:35 i started working on merges yesterday 16:06:37 zul: arosales: carry that over? 16:06:48 I'm frantically working on the critical path for ARM server and MAAS. I regret I haven't managed to look at blueprints since UDS. And not done any merges :-/ 16:06:50 I have a report here, showing the delta with *sid*/*unstable*... NOT the default parent series of wheezy/testing: 16:06:52 s3h: yep 16:06:53 http://people.canonical.com/~davewalker/delta.html 16:07:05 #ACTION zul talk to arosales and jamespage offline about SRU tracker 16:07:05 * meetingology zul talk to arosales and jamespage offline about SRU tracker 16:07:18 ok NOW carrying on :) 16:07:24 #TOPIC Quantal Development 16:07:25 I'd still like to do some merges though if there are any that can wait a couple of weeks. I have an apache2 one in a local branch pending testing. 16:07:32 Daviey: so we should me merging from wheezy? 16:07:36 can I be involved in the SRU tracker discussion, please? 16:07:51 Ursinha: yes since you took over it basically 16:07:53 :) 16:08:01 roaksoax: no, but see if there are hits we should be merging. 16:08:08 lol, thanks zul 16:08:22 rbasak: apache2 should be 2.4, right? 16:08:28 #ACTION zul to also pull Ursinha into SRU tracker talks 16:08:28 * meetingology zul to also pull Ursinha into SRU tracker talks 16:08:31 * rbasak looks 16:08:49 wait no 16:08:54 2.4 is stil in Debian experimental 16:09:00 looks like squeeze will ship w/ 2.2 16:09:07 (which sucks) 16:09:12 But, timing. ;) 16:09:12 I just have a 2.2.22-5ubuntu1 prepared, to fix a specific bug 16:09:21 quantal is on 2.2.22-1ubuntu1 16:09:24 rbasak: yeah stick with that 16:09:30 we don't want to do the transition before Debian :) 16:09:34 :-) 16:09:40 * SpamapS has learned how painful that can be w/ MySQL 5.5 16:10:25 (null) 16:10:59 SpamapS: do you mind driving release bugs? 16:11:05 SpamapS: hah hah :) 16:11:28 eh, uh.. sure.. let me just find that link 16:11:40 SpamapS: http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html 16:11:49 ^^ I updated it to Quantal the other day. 16:12:00 Still, not very populated.. but that is expected at this point in the cycle. 16:12:01 bug 888123 16:12:02 Launchpad bug 888123 in openjdk-7 (Ubuntu Quantal) "erlang version 14.b.2-dfsg-3ubuntu2 failed to build with openjdk-7" [High,Confirmed] https://launchpad.net/bugs/888123 16:12:18 jamespage: ^ 16:12:35 bug 930916 16:12:36 on it - waiting for doko to reappear to check my openjdk-7 fix (its a scary package) 16:12:37 Launchpad bug 930916 in amavisd-new (Ubuntu) "amavis start-stop script fails to stop amavisd" [High,Confirmed] https://launchpad.net/bugs/930916 16:12:59 The bug I keep procrastinating on. Will try to get some time for it later this week. Busy w/ juju SRU to precise today. 16:13:03 SpamapS, is that SRU worthy? 16:13:09 Yes 16:13:16 it was in precise's release bugs too :-P 16:13:16 I could pick it up if that would help 16:13:28 jamespage: sure. take it. :) Its a very simple fix. 16:13:35 SpamapS, ack 16:13:37 bug 974584 16:13:39 Launchpad bug 974584 in sysvinit (Ubuntu Quantal) "Semaphores cannot be created in lxc container" [High,Triaged] https://launchpad.net/bugs/974584 16:13:54 I'm waiting to see if someone speaks up there, else I'll aks for the patch to be sponsored tomorrow 16:14:03 woot 16:14:18 bug 1001846 16:14:19 Launchpad bug 1001846 in cobbler (Ubuntu) "cobbler fails to install with error code 1" [High,New] https://launchpad.net/bugs/1001846 16:15:13 so that seems to be a corner case and I've requested for more information even though the proposed fix makes sense 16:15:26 bug 880339 16:15:27 Launchpad bug 880339 in mysql-5.5 (Ubuntu Precise) "AppArmor profile needs update" [Medium,Incomplete] https://launchpad.net/bugs/880339 16:15:39 I believe that one is well understood and is actually a bug in dh_apparmor 16:16:18 In some cases, /etc/apparmor.d/local/usr.sbin.mysqld is removed because of the transfer of ownership from 5.1 -> 5.5 16:16:35 Have a patch, just need to apply it (got stalled because apparmor was FTBFS, but that got fixed recently) 16:16:38 bug 901881 16:16:40 Launchpad bug 901881 in glance (Ubuntu) "nova and glance should depend on python-keystone" [Low,In progress] https://launchpad.net/bugs/901881 16:17:15 zul: ^^ 16:17:24 SpamapS: ill double check 16:18:04 I see we have the MIR's listed there too... we should probably track those 16:18:25 new libvirt is pending a MIR btw 16:18:38 Now is also a good time to raise any issues NOT being tracked on that list. :) 16:18:44 and that MIR is not on ts list 16:19:02 (dwarves-dfsg) 16:19:03 zookeeper, I think, is approved.. but we haven't added the depends yet because it was basically done for juju 16:19:17 netcf should also be on that list 16:19:30 is that accomplished with a tag? 16:19:39 do we have a server team member on the MIR team? 16:19:54 no, but it really wouldn't matter. The MIR process is bottlenecked on security 16:20:17 i mean after the bottleneck 16:20:29 after the bottleneck there's nothing to do but seed/upload/etc. 16:20:38 zul: we do not. 16:21:01 SpamapS: i mean when the bottleneck is done someone the server team can poke and do our bidding 16:21:04 but anyways 16:21:10 care to discuss in open discussion? 16:21:18 sure 16:21:18 zul: we don't need to be on the MIR team to do anything after the security review is done. 16:21:26 * jdstrand looked at the queue and doesn't see security team subscribed to anything 16:21:28 arosales: Daviey: do we wannt to o through blueprints at this point? 16:21:36 (for MIRs) 16:21:37 zul: once that is done, the bug is approved, and any core dev can go edit the seeds or upload a depending package 16:21:40 ruh ro 16:21:53 SpamapS: what MIR(s) are you referring to? 16:22:16 s3h: I think the main points Daviey already discussed 16:22:20 jdstrand: I'm more discussing the general process and the fact that adding MIR team members would just overload your team more. 16:22:29 oh 16:22:31 ie getting blueprints updated, correct status, and approved 16:22:36 arosales: thanks, great 16:22:40 well, I was promised it wouldn't be like last time ;) 16:22:58 jdstrand: "Words are wind, Jon Snow" 16:23:03 heh 16:23:03 ;) 16:23:09 moving on then 16:23:19 I don't see any big MIR's this cycle 16:23:21 thanks SpamapS! 16:23:28 #TOPIC Ubuntu Server Team Events 16:23:43 SpamapS: i do 16:23:48 but anyways 16:23:58 SpamapS, zul: actually, doko and I discussed adding members to the ubuntu-mir team. we think it would be a good idea if someone else wanted to help out (beyond security audits) 16:24:07 zul: do you want to discuss that now? 16:24:23 jdstrand: sure lets discuss that in the open discussion section 16:24:29 * jdstrand nods 16:24:31 s3h: no lets continue later 16:24:44 ok, any events coming up? 16:25:06 m_3 @ gluecon 23-24 of May 16:25:07 m_3: you still going to gluecon? 16:25:19 submitting for the aws/ec2 conference in November 16:25:22 i'm at usenix config mgmt summit to discuss juju on june 12 16:25:36 jimbaker`: cool! 16:25:53 SpamapS: they rejected the talks... but they're local so maybe I can get a lightning talk in 16:26:01 SpamapS, thanks, this will be my first time presenting juju in public, so fingers crossed ;) 16:26:19 cool, thanks 16:26:26 #TPIC Weekly Updates & Questions for the QA Team (hggdh) 16:26:26 m_3, lightning talks for gluecon are tonight, so doable 16:26:38 hi 16:27:13 I have been working the last week in Boston, so I have no updates. 16:27:15 m_3: and no charm school? 16:27:21 But I will answer any questions ;-) 16:27:22 .. 16:27:42 SpamapS: nope... hopefully next year... it'd be a good crowd for at least an intro juju talk 16:27:45 any questions for hggdh? 16:28:12 thanks hggdh. moving on, 16:28:23 #TOPIC Weekly Updates & Questions for the Kernel Team (smb) 16:28:25 Hello... 16:28:36 Trying to understand bug 999755... slowly. Apart from that... other questions? 16:28:37 Launchpad bug 999755 in linux (Ubuntu) "Kernel crash on EC2 m1.large instances" [Medium,Confirmed] https://launchpad.net/bugs/999755 16:28:45 .. 16:29:06 smb: you might wnat to test zul's proposed libvirt merge for quantal against xen 16:29:37 http://people.canonical.com/chucks/libvirt 16:29:46 ~chucks/libvirt 16:29:55 s3h, Yes, I guess I should... 16:29:57 yeah that 16:30:26 any other questions for smb? if not... 16:30:52 #TOPIC Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak) 16:30:53 Nothing to report. Work on ARM server continues. Any questions for me? 16:31:40 sounds like no, thanks rbasak 16:31:46 #TOPIC Open Discussion 16:32:10 jdstrand: so, despite what I thought, the MIR team actually *could* use a member from the server team? 16:33:05 SpamapS: yes! 16:33:56 how it would probably work though is that the server team member would review non-server stuff and the desktop member would review server stuff (to avoid conflict of interest). but that is an implementation detail 16:34:11 Yeah that sounds like a good idea. 16:34:27 there is certainly enough work to go around and I feel it would benefit not only the mir team, but all teams trying to pursue MIRs 16:34:33 arosales: maybe you and Daviey can work out who might be available for such a post? 16:34:33 who all would be interested? 16:34:36 Daviey: ^^ 16:34:46 * SpamapS steps backward 16:34:49 I have enough :) 16:35:01 any volunteers ? 16:35:03 * s3h Daviey and arosales to work a list of who is available for MIR team 16:35:08 (as an aside, we have work items on the security team surrounding improving the audit process as well) 16:35:11 he/she doesnt need to be core-dev do they? 16:35:19 I might be interested. if i don't have to be cored-ev 16:35:30 or be able to speell 16:35:40 spelling is a must ;) 16:35:47 so i am out as well 16:35:49 s3h: you're a server dev, are you not? 16:36:00 yes 16:36:01 well, they all currently are, but technically no because it is up to the filer to adjust the seeds, etc 16:36:07 s3h: I think that shows enough packaging know-how 16:36:36 but the person must be able to do pretty thorough packaging reviews. core-dev just happens to demonstrate that 16:36:59 let's not focus on me :) perahps whoeer is interested should email Daviey/arosales 16:37:18 https://wiki.ubuntu.com/MainInclusionProcess and https://wiki.ubuntu.com/UbuntuMainInclusionRequirements should be reviewed by interested people 16:37:23 and turn on their spell checker 16:37:52 ok, anything actionable here? 16:38:20 #ACTION email arosales/Daviey if interested in ubuntu-mir membership 16:38:20 * meetingology email arosales/Daviey if interested in ubuntu-mir membership 16:38:21 s3h: you forgot the # 16:38:36 on the first one 16:38:51 do you think we need both actions? 16:39:02 I also assume a couple of of rounds of MIR can help with core-dev applicaton 16:39:19 I am sure the MIR team would welcome help 16:39:20 What is required for membership? 16:39:34 able to do pretty thorough packaging reviews 16:40:00 ok shall we move on? any further topics? 16:40:02 Is contributing developer a requirement for example? 16:40:08 and knowledgeable about https://wiki.ubuntu.com/MainInclusionProcess and https://wiki.ubuntu.com/UbuntuMainInclusionRequirements 16:40:22 s3h: one other topic 16:40:39 rbasak: jdstrand would know for sure 16:40:54 rbasak: you're about ready for a server dev application tho.. so I wouldn't worry too much about not having upload rights "today" :) 16:41:06 s3h: Everyone comfortable with integrating the blueprint template jamespage emailed out? 16:41:14 Also documented at https://wiki.ubuntu.com/BlueprintSpec 16:41:34 I followed it with my blueprints and liked it 16:41:37 well, actually I wouldn't. I kind of inherited my position :) if you are core-dev, I don't think there is any problem. if you aren't, I think the existing team would have to talk to the candidate 16:41:53 what do others think? 16:42:05 thanks for giving it a try s3h 16:42:55 if anyone needs any help interpreting the template into their blueprints please feel free to ping me 16:43:06 or ping in ubuntu-server 16:43:14 for reference: http://comments.gmane.org/gmane.linux.ubuntu.server/6138 16:43:27 be great if server team had some solid blueprint documentation with this template 16:44:04 so I personally am backing my bp's in lp +junk. What are others doing? Do we set up a team to combine all the blueprints? 16:44:16 (as per smoser's suggestion) 16:44:42 I think we still need to iron that out and perhaps sync up with Ursinha 16:44:49 Ursinha was working on some things to make this better integrated with launchpad. 16:44:59 s3h: good point to bring up though 16:45:07 ie, to give a comment field and history of work items. 16:45:20 Ursinha: do you have any update on that? 16:45:39 s3h: you can give me an action to follow up with Ursinha on the best approach for this cycle. 16:45:43 the issue with you doing that on your own, s3h is that someone will just edit the whiteboard manually, and then either lose their changes, or not be able to commit to your +junk branch to change it properly 16:45:49 and is there anything in that work that would block creating the ubuntu-server-blueprints lp group 16:46:14 Its worth noting that any branch can be attached to any blueprint.. 16:46:18 #ACTION arosales to follow up with Ursinha on best approach for blueprint management this cycle 16:46:18 * meetingology arosales to follow up with Ursinha on best approach for blueprint management this cycle 16:46:28 well, s3h, urshina's proposal would largely mitigate the need for that. 16:46:32 so if we do an auto-sync thing from branch -> BP we can also link the branch, and make a project, like 'ubuntu-blueprints' to keep them all in 16:46:36 smoser: I get emails whenever they do, so I can udpate it in my copy 16:46:57 this sounds like an implementation discussion tho :-P 16:46:59 smoser: sure, but in the meantime we risk losing our whiteboard contents 16:46:59 there are two things that can be done 16:47:03 not something for this meeting. :p 16:47:09 okay :P 16:47:09 there she is! 16:47:21 good. please discuss, and lets find a solution for this. 16:47:24 thanks god I have hilight for misspells :P 16:47:26 Ursinha: I catch up with you off-line 16:47:29 sure 16:47:51 first: using a bot that parses email, and also parses a message in the whiteboard explaining the change 16:48:17 then the bot removes that and we have a page somewhere else looking like the bug activity pagwe in launchpad 16:48:35 second approach, is changing launchpad to include blueprint activity 16:48:49 Ursinha: thanks 16:48:54 second one in way cleaner, but it will take a bit of time 16:49:00 can you send an email to the m-l after you and arosales discus? 16:49:18 I'm currently working on it, but don't want to wait for it to finish to start doing something 16:49:19 sure 16:49:37 thanks. any other topics? 16:49:42 thanks for working on that Ursinha 16:49:58 arosales, it's my pleasure 16:50:00 I've been doing some work on the bug triage workflow 16:50:09 ah! 16:50:09 should have something for you all to review this week 16:50:18 jamespage: awesome, thanks 16:50:19 jamespage, awesome :) 16:50:38 #TOPIC Announce next meeting date and time 16:50:55 Tuesday May 29 at 1600 UTC. right here. 16:51:06 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)