20:04 #startmeeting 20:04 Meeting started Mon Apr 14 20:04:48 2014 UTC. The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 20:04 20:04 Available commands: action commands idea info link nick 20:04 * slangasek takes action! 20:05 * mdeslaur cheers slangasek on 20:05 [TOPIC] next meeting 20:06 according to my calendar, next meeting should be Apr 28, 20:00 UTC 20:06 ... with pitti as the next chair? 20:06 Yeah. 20:06 sounds right 20:06 [AGREED] Next meeting Apr 28, 20:00 UTC, pitti to chair 20:07 [TOPIC] Apologies 20:07 I don't think we had anyone say ahead of time that they wouldn't make it 20:08 but it looks like kees, sabdfl, pitti are absent without regrets, and the rest of us are here 20:08 we actually had pitti say ahead of time that he'd make it for sure ;) 20:08 right :) 20:08 [TOPIC] Action review 20:08 hi stgraber 20:08 were there any actions from last time? they're not noted in the agenda 20:09 * slangasek checks https://wiki.ubuntu.com/TechnicalBoard/TeamReports/Current 20:09 not updated from the previous meeting, so... 20:09 [TOPIC] Review our current "provisional" Micro Release Exceptions 20:10 this one needs to turn into something other than a perpetually carried-over item 20:10 infinity: I recall that you asked kees about it last time, but I don't remember a decision being taken 20:10 kees isn't here for that one, so I guess we skip for now 20:10 I'm here. carry please 20:10 hi kees 20:10 hola 20:10 kees: how do we help turn this into something other than a 'carry'? 20:10 sorry I'm late! 20:10 I think last time, I asked kees to provide enough detail to the list of his intent and proposed strategy that maybe some people could take some load off. 20:10 ok 20:11 how about if I explicitly [action] that? 20:11 slangasek: so, I think we to generate a report showing which MREs have happened, and which haven't. 20:11 attempting to analyze bug counts didn't work; it's way too complex. 20:11 kees: is that something you want to still drive, or is it just defaulting to you and we should try to find someone else to do it? 20:12 slangasek: I've made no head way, so I probably shouldn't own it. one option would be to assign out chunks of MREs to check. 20:12 kees: I think I'd rather tag someone on the SRU team to help out with getting us a general report 20:12 (I think I know just the person) 20:12 so let me take the action to get us the report, and then we can go from there on list? 20:13 okay 20:13 slangasek: Which person did you have in mind? 20:13 [ACTION] slangasek to work with SRU team to get a list of how the provisional MREs have/haven't been used 20:13 * meetingology slangasek to work with SRU team to get a list of how the provisional MREs have/haven't been used 20:13 infinity: bdmurray, the grand master launchpad miner 20:14 slangasek: Seems sensible. 20:14 You should get him a hat with a light on. 20:14 hehe 20:14 and a canary icon for his lp profile 20:14 so there are no other explicit agenda items in the wiki 20:15 [TOPIC] Scan the mailing list archive for anything we missed 20:15 https://lists.ubuntu.com/archives/technical-board/2014-April/ shows the Ubuntu Kylin discussions, and MRE requests for lxc, juju-core, iscsitarget 20:16 I do want to discuss the kylin one here (sorry for not putting it on the agenda explicitly) 20:16 do the MREs need discussion here/now? 20:17 for the lxc one, stgraber has answered pitti's questions; since pitti has already looked at it, it's probably sensible to let him continue driving that one on list 20:17 I think we can continue them on the list 20:17 iscsitarget had a +1 from pitti but has not yet been added to https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions - can someone take care of that? 20:18 (the rule for MREs is still 'a single +1', right?) 20:18 and the juju-core one seems to still be in discussion on list 20:20 (iscsitarget MRE added to the wiki) 20:20 [TOPIC] UbuntuKylin archive 20:21 [LINK] https://wiki.ubuntu.com/Ubuntu%20Kylin/Ubuntu%20Kylin%20Archive 20:21 we have a draft that I believe captures the TB consensus on the mailing list so far 20:21 but I think we only have 3 explicit +1s on this (stgraber, myself, mdeslaur) 20:22 kees, infinity: I've been assuming there's nothing too controversial there at this point, and so have been proceeding with the implementation, but would appreciate an explicit ack 20:22 slangasek: Right, let me quickly review the wiki page again. 20:22 thanks 20:23 slangasek: Does ~ubuntu-archive get r/w access to the repo to force removal issues, or do we just ask nicely? 20:24 infinity: at present I'm expecting that we request removal of the kylin team rather than being hands-on with archive access 20:24 slangasek: Otherwise, looks fine. 20:25 slangasek: I'm okay with us asking nicely in the general case anyway, just thinking that an explicit ACL serves better than polite process if we ever find them unresponsive for too long about a severe issue or whatever. 20:25 infinity: I have no opinion on the mechanics of the oversight; if you think it's important to have direct access, I suggest proposing this to Jack on the list 20:25 slangasek: I don't think it would block my +1 on the proposal. 20:25 ok 20:26 oh hey, we could do an actual explicit vote here 20:26 slangasek: It's about on par with "core-devs should be able to commit to all your *&!% packaging branches", which is never as true as it should be. :P 20:26 [VOTE] ratification of https://wiki.ubuntu.com/Ubuntu%20Kylin/Ubuntu%20Kylin%20Archive 20:26 Please vote on: ratification of https://wiki.ubuntu.com/Ubuntu%20Kylin/Ubuntu%20Kylin%20Archive 20:26 Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname) 20:26 +1 20:26 +1 received from slangasek 20:26 +1 20:26 +1 received from infinity 20:26 +1 20:26 +1 received from mdeslaur 20:27 Hah. You got a new vote and lost an old one. ;) 20:27 stgraber, kees: 20:27 +1 20:27 +1 received from stgraber 20:29 kees: do you need more time to review/consider? 20:30 [ENDVOTE] 20:30 Voting ended on: ratification of https://wiki.ubuntu.com/Ubuntu%20Kylin/Ubuntu%20Kylin%20Archive 20:30 Votes for:4 Votes against:0 Abstentions:0 20:30 Motion carried 20:30 always room for more feedback on the list :) 20:30 [TOPIC] Check up on community bugs 20:31 https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard is quite empty 20:31 so... done 20:31 and that leaves selecting a chair, which I believe we did at the beginning 20:31 anything I've missed? 20:32 nope 20:33 cool 20:33 #endmeeting 20:33 thanks, all! 20:33 thanks slangasek! 15:56 o/ 16:00 \o 16:00 howdy o/ 16:01 o/ 16:01 smoser: Error: Can't start another meeting, one is in progress. 16:01 o/ 16:01 #endmeeting 16:02 oh fiddle. 16:02 that was quick 16:02 smoser: Error: Can't start another meeting, one is in progress. 16:02 #endmeeting 16:02 stgraber, can you fix that ^ 16:02 thanks. 16:02 smoser: Error: Can't start another meeting, one is in progress. 16:02 smoser: Error: Can't start another meeting, one is in progress. 16:02 still no dice 16:02 #endmeeting 16:02 o/ 16:02 stgraber: Error: Can't start another meeting, one is in progress. 16:03 hmm, lost cause apparently 16:03 well then, meetingology, we're going to run our meeting without your help. 16:03 smoser: Error: Can't start another meeting, one is in progress. 16:03 #topic Review ACTION points from previous meeting 16:03 at https://wiki.ubuntu.com/ServerTeam/Meeting i dont see any ACTION points, so moving on. 16:04 #topic Trusty Development 16:04 #link https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule 16:04 in case you were not aware, 14.04 will be released in 2 days. 16:04 its well past time to sneak stuff in. 16:04 still trying tho 16:04 :-) 16:05 well then. 16:05 #subtopic Release Bugs 16:05 #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-t-tracking-bug-tasks.html#ubuntu-server 16:05 we still have some Ctritial and High important bugs there. 16:05 jamespage, they seem to all be generally yours :). 16:06 any comments? 16:06 unsurpisingly we are waiting on swift, neutron and cinder packages to be accepted still 16:06 most other things are OK - ceph will go in as an SRU 16:06 #subtopic Blueprints 16:07 #link http://status.ubuntu.com/ubuntu-t/group/topic-t-servercloud-overview.html 16:07 there really isn't any time to get work items into archive. 16:07 so if you have some to do, you should probably POSTPONE 16:07 unless they're documentation and non-archive related. 16:08 #topic Server & Cloud Bugs (caribou) 16:08 caribou gave prior notice that he'd not be here. so moving on. 16:08 #topic Weekly Updates & Questions for the QA Team (psivaa) 16:08 smoser: nothing to report this week too, smoke tests are fine 16:08 #topic Weekly Updates & Questions for the Kernel Team (smb, sforshee) 16:08 Nothing fancy this week. Are there things you want to bring up? 16:09 my only issue recently with kernel is the development release's purging kernel binaries from archive 16:09 which is annoying to things like d-i, such that user has to always have latest thing. 16:09 this is nothing to do with smb really, but I just wanted to remark on it. 16:10 * smoser smoser raise request to not purge kernels from archive quite so quickly 16:10 smoser, I guess nothing new either 16:10 #topic Open Discussion 16:10 anyone have anything ? 16:10 i like turtles 16:10 That is a archive issue as anythign not in any pocket gets purged iirc 16:10 and sloths 16:10 unseen unicorn 16:10 just saying 16:11 lol 16:11 * hallyn is lost 16:11 hallyn, its tradition for ubuntu releases to be named with an adjective and a animal 16:11 i like sloths better than turtles...if i had a choice 16:11 and its coming close to a point when the next deelopment cycle will be started :) 16:12 thus, the unseen unicorn. 16:12 also, if you're reading here, you might be interested in http://www.canonical.com/careers 16:12 lol. of course 16:12 i think U should just be Ubuntu. we only have one shot at this! ;) 16:12 the slot i guess confused me 16:12 well, ABCs are not zul's forte. 16:12 hehe 16:12 it's tough 16:12 smoser: i blame the canadian school system 16:13 if anything on the jobs page there looks interesting , especially server related, please feel free to contact me. 16:13 teach me french why dont you 16:13 this ends the advertisement portion of our meeting. 16:13 surely by the time this meeting occurs next week we'll have an official U animal. 16:13 #topic Announce next meeting date and time 16:13 unhygenic unicorn? 16:14 Tuesday 2014-04-22 at 1600 UTC - #ubuntu-meeting 16:14 happy tax day to americans. 16:14 #endmeeting 17:00 jsalisbury: Error: Can't start another meeting, one is in progress. 17:00 ## 17:00 ## This is the Ubuntu Kernel Team weekly status meeting. 17:00 ## 17:00 [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting 17:00 [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Trusty 17:00 # Meeting Etiquette 17:00 # 17:00 # NOTE: '..' indicates that you are finished with your input. 17:00 # 'o/' indicates you have something to add (please wait until you are recognized) 17:00 #endmeeting 17:01 jsalisbury, the bot lost its mind 17:01 hmm meetingology is in trouble 17:01 Roll Call for Ubuntu Kernel Weekly Status Meeting 17:01 o/ 17:01 o/ 17:01 o/ 17:01 o/ 17:01 o// 17:01 o/ 17:01 o/ 17:01 o/ 17:01 [TOPIC] ARM Status (ppisati) 17:01 Nothing new to report this week 17:01 .. 17:01 [TOPIC] Release Metrics and Incoming Bugs (jsalisbury) 17:01 Release metrics and incoming bug data can be reviewed at the following link: 17:01 [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt 17:01 .. 17:02 [TOPIC] Milestone Targeted Work Items (ogasawara) 17:02 [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork 17:02 [LINK] http://status.ubuntu.com/ubuntu-t/canonical-kernel-distro-team.html 17:02 || apw || core-1311-kernel || 4 work items || 17:02 || || core-1311-cross-compilation || 2 work items || 17:02 || || core-1311-hwe-plans || 1 work item || 17:02 || ogasawara || core-1403-hwe-stack-eol-notifications || 2 work items || 17:02 || smb || servercloud-1311-openstack-virt || 3 work items || 17:02 .. 17:02 [TOPIC] Status: Trusty Development Kernel (ogasawara) 17:02 The 3.13.0-24.46 Ubuntu kernel in the Trusty archive is currently based on the v3.13.9 upstream stable kernel. The kernel is currently frozen 17:02 in preparation for our final 14.04 release this Thurs Apr 17. kernel. 17:02 We do not anticipate any uploads between now and Thurs. All patches 17:02 from here on out are subject to our Ubuntu SRU policy. 17:02 ----- 17:02 Important upcoming dates: 17:02 [LINK] https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule 17:02 Thurs Apr 17 - Ubuntu 14.04 Final Release (~2 days away) 17:02 .. 17:02 [TOPIC] Status: CVE's 17:02 The current CVE status can be reviewed at the following link: 17:02 http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html 17:02 .. 17:03 [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Saucy/Raring/Quantal/Precise/Lucid (bjf/henrix/kamal) 17:03 Status for the main kernels, until today (Mar. 25): 17:03 * Lucid - Verification and Testing 17:03 * Precise - Verification and Testing 17:03 * Quantal - Verification and Testing 17:03 * Saucy - Verification and Testing 17:03 17:03 Current opened tracking bugs details: 17:03 * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html 17:03 For SRUs, SRU report is a good source of information: 17:03 * http://people.canonical.com/~kernel/reports/sru-report.html 17:03 17:03 17:03 Schedule: 17:03 17:03 cycle: 30-Mar through 26-Apr 17:03 ==================================================================== 17:03 28-Mar Last day for kernel commits for this cycle 17:03 30-Mar - 05-Apr Kernel prep week. 17:03 06-Apr - 12-Apr Bug verification & Regression testing. 17:03 17-Apr 14.04 Released 17:03 13-Apr - 26-Apr Regression testing & Release to -updates. 17:03 17:03 .. 17:03 [TOPIC] Vote on upload rights for kamal. 17:04 https://wiki.ubuntu.com/KamalMostafa/KernelPPUApplication 17:04 +1 17:04 +1 17:04 +1 17:04 "kamal has shown himself to have a keen eye for detail, and a 17:04 strong sense of when to ask for help. I have no hesitations in 17:04 accepting him into the team. +1" 17:04 ^^ from apw 17:04 +1 17:04 +1 17:04 be it resolved, blah, blah... 17:05 thanks folks 17:05 +1 17:05 [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/) 17:05 Thanks everyone 17:05 #endmeeting 17:05 thanks jsalisbury 17:53 #endmeeting 17:53 jose: Error: Can't start another meeting, one is in progress. 17:53 hmm, looks like a bug, I'll poke someone to get it fixed 18:40 [[http://mootbot.libertus.co.uk/cabbagehuggers/2014/cabbagehuggers.2014-04-15-19.20.log.html#5 ratification of https://wiki.ubuntu.com/Ubuntu Kylin/Ubuntu Kylin Archive]] as an output for moinmoin okay? 18:43 wrong channel apologise 18:45 %'s are throwing off the meeting bot for votes, so if they have a url in #vote bit its causing it to fall over 18:48 still wrong channel lderan :P 18:48 aye was just describing what happened :) 18:48 lol, my bas then 18:49 *bad 19:53 #endmeeting 11:55 Mek! 12:00 !rmb 12:00 cjohnston, cyphermox, Destine, ejat, hggdh, IdleOne, iulian, micahg, Pendulum, PabloRubienes, freeflying, jared, s-fox, amachu, and chilicuil. Meeting time. 12:01 Good evening all, please bear with us while we gather enough to reach quorum for the meeting 12:01 Okay 12:05 jared: Error: Can't start another meeting, one is in progress. 12:05 #endmeeting 12:05 Hmm 12:06 I'm not sure I can make the bot work 12:06 jared: Error: Can't start another meeting, one is in progress. 12:07 #endmeeting 12:07 interesting 12:07 I think it needs to be the previous chair to end it 12:08 I think it's uneeded: the meeting has been started by the bot 12:08 So, my logic is the channel is publicly logged anyway, should we just do it old school and manual? 12:08 jared: yes 12:08 AlbertoSN: it's still on a previous meeting, not the current one. 12:08 So we'll just ignore the bot for now 12:08 Hello and welcome to the Ubuntu Membership Review Board for the 1200 UTC meeting for April 16, 2014. 12:08 "We'll do it live!" 12:08 The wiki page for the Review Board is available here: https://wiki.ubuntu.com/Membership/Boards 12:08 We will attempt to get through all of the applicants that have added themselves to that list before today's meeting. If we are unable to make it through the entire list due to time constraints, then at the next meeting we will pick up where we left off. 12:09 The format for the meeting is as follows: We will go through the list of applicants one by one, by date of application (FIFO). 12:09 Each applicant should introduce themselves (1-5 sentences) and provide links to their Ubuntu Wiki page. After the introduction the members of the Membership Review Board will review the pages and, if needed, ask the applicant further questions. 12:09 During this time it is encouraged for other members of the community to show their support for the applicant. Do not be alarmed if the members of the Membership Review Board are quiet during this time; they are most likely reading wiki/launchpad/forum/other pages and deciding how they are going to vote. 12:09 When the board is ready to vote, they will publicly vote in the channel with either +1, 0, or -1 (for membership, abstain, and against membership, respectively). If the sum of those numbers is positive, then the applicant is now an official Ubuntu member! (feel free congratulate them!) 12:09 Quintasan: /msg qengho do you have anyone from Canonical that is also an Ubuntu member to vouch for you during the RMB meeting? If so, it would be good to have them present *now* 12:09 (As much as prerecorded messages are "manual") 12:09 dammit 12:09 oh well 12:10 * hggdh apologises. But the message is considered sent 12:10 :D 12:10 So, we have Chad Miller up first, is Chad here with us (the nickname on Launchpad doesn't appear to be here) 12:10 actually, the nick is present -- qengho 12:10 I'm Chad. https://wiki.ubuntu.com/ChadMiller/DeveloperApplication 12:11 Good evening qengho , sorry was reading the wrong nick 12:11 qengho: can you please introduce yourself while the board reads over the application 12:11 I've been involved in Debian and Ubuntu for a long while. Switched to Linux in 1995, though Slackware. Debian immediately won me over. 12:12 For the record, as the bot is broken, the current boardmembers present are hggdh, Pendulum, IdleOne and I. 12:12 Became Debian Developer in late 1990s. 12:12 Maintained a few packages, and gave up DD in 2004 or so. 12:13 I signed on to code-of-conduct early in Ubuntu's life, and joined Canonical about 4 years ago. 12:14 I've been happy with other people sponsoring my packages, but since I am the only person working on chromium-browser, I think I should try to join officially and get permission to upload directly. 12:15 EOF 12:15 qengho: ah I was wondering that, were you specifically seeking upload rights or just Ubuntu membership? 12:15 qengho: just a question, right now: why are you here instead of the DMB? 12:16 #endmeeting 12:16 DMB = Developer Membership Board (they are the ones who can grant upload rights) 12:16 thank you AlanBell 12:16 anyone can op up and do chair commands 12:16 jared: Well, upload also, but I don't have a strong opinion about it. I have good sponsors available. 12:17 qengho: the main problem being is we are unable to grant any developer rights on this board 12:19 We're happy to proceed based upon gaining Ubuntu Membership but just to let you know the DMB (as pointed out) are the ones capable of giving upload rights (and also have the ability to grant Ubuntu Membership) 12:19 hggdh, jared, I see. Well, I'd still like membership. 12:20 qengho: no problems, just making sure you're aware of all the outcomes 12:21 The DMB also is also able to confer a level of membership that has a little more relevancy to developers than just regular Ubuntu Membership. We can't give it out and I haven't heard it being added on top of someone who was given membership through an RMB 12:22 qengho: our problem is your wiki is geared for a DMB application; there is not much for a RMB application (like, community) 12:23 Oh. 12:23 qengho: this was one reason for me trying to /msg you earlier on 12:23 I would suggest you apply directly to the DMB, if approved by them you would get Ubuntu membership + the upload rights you are seeking 12:23 Excuse me: the Internet connection of my university disconected 12:24 Very well. Thank you. 12:24 but if you want to proceed here that is also fine. Just know that we can't give you upload privs 12:24 AlbertoSN: no problems, just taking through options with qengho still 12:24 qengho: the DMB's next meeting is Monday - https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda is that a suitable time in your time zone? 12:25 I'm around now 12:25 jared: that time is fine. I'll take my application there. 12:25 qengho: sorry about the confusion the application process may have caused. 12:26 And I'm sorry for wasting time. 12:26 no worries :) 12:26 qengho: We just want to make sure that you're able to apply to the team most equipped to deal with your interests and needs. It's not time wasted at all :) 12:26 ^ 12:26 qengho: no time wasting, just making sure you get the right outcome. 12:27 Hah, at least we're consistent 12:28 qengho: did you h ave any other questions about the process or can we move on to the next applicant? 12:30 No questions. EOF 12:30 AlbertoSN: can you please introduce yourself while we read over your application 12:30 qengho: thanks for that 12:31 Yes 12:31 My name is Alberto Salvia Novella: https://wiki.ubuntu.com/es20490446e 12:31 I coordinate the "One Hundred Papercuts" project: https://launchpad.net/hundredpapercuts 12:32 Since, I believe, November or before 12:33 I joined Ubuntu Bug Control a year ago, and since then managed several bugs: https://launchpad.net/~es20490446e/+karma 12:34 AlbertoSN: I've noticed there has been a little friction lately with regards to your handling of bugs. Have you been able to work through that with the team? 12:36 Brian Murray told me he will speak with my in regard of this after tTrusty has been released. But I have no news about it since, I believe, he's somehow busy at this time. 12:37 Better to ask himself. 12:37 AlbertoSN: no worries 12:37 AlbertoSN: Good wiki page and very good contribution in bug management. Try to keep it that way (in regards to bug management). 12:37 Just to let you know, AlbertoSN has my support in his Ubuntu membership application. 12:38 Thank you, NikTh 12:38 :) 12:39 Is there any information you'll find useful about me? 12:40 AlbertoSN: sorry, just reading over information still 12:40 Continue please: I believe watching at what has been already done is better than me explaining it 12:41 AlbertoSN: okay, so I'll lay it out. We are having problems reconciling an application when you have had access removed in Launchpad pending a discussion at a more appropriate time. 12:42 AlbertoSN: We (the board have been discussing) believe it might be better to put your application on hold until you're able to have that discussion with the appropriate people. 12:43 Okay: thank you 12:43 BTW I want to make clear that I will not vote for, or against, AlbertoSN until he, Brian, and I get together 12:43 AlbertoSN: would you be comfortable putting it on hold until such a time? 12:43 I have no hurry 12:44 We don't want to outright deny it without discussion but we do feel an important part of membership is getting along with the community. And while such actions are still outstanding we feel we can't make a proper judgement until that is completed 12:45 Ok 12:46 AlbertoSN: thank you for your understanding. We are more than happy to look at your application again as soon as that is resolved. 12:48 AlbertoSN: do you have any questions for us? 12:51 Nope: thank you 12:52 AlbertoSN: Thank you for your understanding. As we said, please do apply again when you feel ready and the issue with Bug Control is resolved. 12:56 Bai bai 12:57 Have a nice day 12:57 Ok well I think that wraps it up for us this evening/morning 12:57 Thanks to the board members who were around and thanks to the applicants 13:39 AlanBell: Error: Can't start another meeting, one is in progress. 13:39 no it isn't :) 13:39 meetingology: quit