15:03 #startmeeting DMB 15:03 Meeting started Mon Nov 21 15:03:59 2016 UTC. The chair is rbasak. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 15:03 15:03 Available commands: action commands idea info link nick 15:04 #topic Review of previous action items 15:04 sil2100 to deal with the juju packageset creation 15:04 sil2100 sil2100 to update the lubuntu packageset according to the current seed 15:04 sil2100: how's that going? 15:05 Not finished yet, sorry about that - I added new lubuntu packages to the packageset, but eh, still didn't clear up the old ones 15:05 Was doing that semi-manually since the script wasn't reliable 15:05 Yeah I've resorted to doing that too :-/ 15:05 sil2100: what about juju packageset? Or did that get deferred because we have no uploaders? 15:06 Promise to resolve this this week 15:06 rbasak: there are no uploaders right now so it's more of a thing 'for the future' 15:06 #action sil2100 to update the lubuntu packageset according to the current seed (carried over) 15:06 * meetingology sil2100 to update the lubuntu packageset according to the current seed (carried over) 15:06 I wanted to do that but then learned that the TB needs to do that 15:06 sil2100: OK, do you still want an action for that or shall we drop it? 15:06 Let's drop it 15:06 OK 15:07 We can really take care of it when it's needed, I don't want to bother the TB without much merit from that 15:07 #done sil2100 to deal with the juju packageset creation 15:08 #topic MOTU Applications 15:08 #subtopic MattiaRizzolo (mapreri) - application (for Nov 21th) 15:09 mapreri: hello! Please could you start by introducing yourself? 15:09 o/ 15:10 * josvaz__ also here for the same reason as philroche 15:10 I've been contributing to the community (loco team ubuntu-it mostly) since 5 years or so, 3 years ago I started doing some dev stuff like merges, etc. Then I later shifted a bit on the Debian side of the equation, were I became DD last year. 15:10 This is the tl;dr story of me, guess it's a bit longer on the wiki, but I'm happy to provide more. 15:11 Thanks! 15:11 Does anyone have questions for mapreri? 15:12 Well, I have some :) 15:13 shot them :) 15:13 What are your specific reasons for applying for MOTU? 15:16 First, even if this is not true and I know it isn't, I feel a bit limited in what I can do. I know that since I became DM (and then DD) I started doing a lot more just because I didn't even to bother sponsors anymore. Practical examples includes carrying over library transitions in ubuntu; In the past year I started (or collaborated) several of them in Debian, but for the ubuntu side I just prodded my usual sponsors with "please do the 15:16 needed rebuild of these", which is lame. And then I'd like to help a bit with sponsorship stuff; it's working atm, but it's pretty clear that it could use another hand. 15:17 I also have an interested in the same packages I maintain in Debian, but given that I actually care about more than just my garden I figured I could do more. 15:18 s/interested/interest/ 15:18 * LocutusOfBorg will be happy to stop signing and uploading is requests :p 15:18 OK, thanks. 15:18 mapreri: are you also going throught the sponsoring queue to find things that need some work? 15:19 (and, incidentally, I'd like to also apply for PPU for a couple of packages I have in main in ubuntu, btw) 15:20 sil2100: from time to time I look at http://reqorts.qa.ubuntu.com/reports/sponsoring/index.html to see how things are (and they are quite good atm, tbh), but no, I'm not reviewing stuff atm, nor actively looking at it. 15:20 Like, doing reviews so that eventual sponsors have it easier, prepare debdiffs etc. 15:20 Ok 15:21 Next question from me: what and how do you check if an upload is appropriate for Ubuntu with respect to our development cycle? 15:22 like, if that given upload is ok considering the moment we're in the given cycle? (i.e. freezes, etc?) 15:23 Right, that's my question. 15:23 if it's that, basically everything's good untile the Import Freeze, after that changes should be pondered according to which phase the development cycle is 15:24 Can you give me an example of a (made up if needed) change that isn't OK to upload at a particular time? 15:25 starting a openssl transitions one month before the freeze counts as a thing not to do? /me grumbles 15:26 In Ubuntu specifically. What I'm looking for is that you're aware of the Ubuntu development cycle specifically, and that you know what not to upload when. 15:26 otherwise, umh, for example after the feature freeze a new major version of a software which changes all of its interface is not good. 15:27 Do you know where you can find the current freeze dates for Zesty? 15:27 I have scribus in universe. If it happens they release the new 1.5.x series, that's going to change all the interface and invalidate old file types, that's something I'd put after the FF 15:27 https://wiki.ubuntu.com/ZestyZapus/DraftReleaseSchedule ? 15:28 s/I'd put/I wouldn't put/ meh 15:28 Great, thanks. 15:28 I hadn't noticed it was still in draft! 15:28 that was a hell of a typo 15:28 I thought it probably was. I was waiting for the correction :-) 15:28 mapreri: ok, one question from me, a rather easy one: when you get some packages sponsored, do you make sure the new package migrates to the release pocket correctly? 15:28 mapreri: if yes, where do you go to check if a package gets stuck in -proposed? 15:28 it's not a typo, I, slangasek and infinity have yet to go through it one last time and make it not draft 15:28 yes 15:29 cyphermox: the "s/I'd put/I wouldn't put/ meh" I mean :) 15:29 sil2100: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html + _output.txt (which I'm perfectly able to read) 15:29 Excellent 15:29 yeah, I figured after :) 15:29 Any more questions for mapreri? 15:29 micahg: ? 15:29 Not from me, I'm all good 15:30 JOOI, do you know if anybody though to have the britney output more integreted into LP? 15:30 thought* 15:30 I'm not aware of any plans for this. 15:31 oh, well.. guess it's fine enough as it is already (just boring to load multi-MB web page..) 15:32 I guess micahg has no questions 15:32 I think micahg had to step away briefly, and we need him for a quorate vote as there are only four members here today, including him. 15:33 I'm not going anywhere, you can move to another candidate and ask me more questions later if you want :) 15:33 Let's go ahead with the vote. micahg can provide his opinion later anyway. 15:33 #vote Grant mapreri MOTU 15:33 Please vote on: Grant mapreri MOTU 15:33 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) 15:34 sil2100, cyphermox: ^ 15:34 o/ 15:35 +1 (upload history says it all) 15:35 +1 (upload history says it all) received from sil2100 15:35 The world could always use more MOTUs 15:36 :) 15:36 +1 15:36 +1 received from cyphermox 15:36 +1 15:36 +1 received from micahg 15:36 +1 15:36 +1 received from rbasak 15:36 #endvote 15:36 Voting ended on: Grant mapreri MOTU 15:36 Votes for:4 Votes against:0 Abstentions:0 15:36 Motion carried 15:36 \o/\o/ 15:36 Thank you all! :) 15:36 mapreri: congratulations, and thank you for helping Ubuntu out! 15:36 mapreri: congrats! 15:37 Who wants to take the actions to add mapreri? 15:37 Question: if I wanted to ask for PPU for a couple of packages in main, shall I just email the team? 15:38 Technically PPU additions require quorum (four +1s). But we can try to do that on the ML if you want unless in response someone wants to take it to IRC perhaps? 15:38 (those would be pbuilder and libreoffice-dictionaries, btw) 15:38 Or shall we just vote on that now? 15:38 (given that we've all just reviewed all your work) 15:39 (yeah, figured it would be a kinda good moment, even if off agenda (sorry!)) 15:40 mapreri: GunnarHj already uploads libreoffice-dictionaries. Are you in touch with him? 15:41 rbasak: we collaborated last year yes - e.g. he sent some changes to debian, I included them and then he re-uploaded those to debian, given that we couldn't sync the package just yet 15:41 the second debian is an ubuntu.. 15:42 OK, let's vote on that then. 15:42 #vote Grant mapreri PPU to pbuilder and libreoffice-dictionaries 15:42 Please vote on: Grant mapreri PPU to pbuilder and libreoffice-dictionaries 15:42 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) 15:44 +1 15:44 +1 received from cyphermox 15:45 micahg, sil2100: ^ 15:45 +1 15:45 +1 received from micahg 15:45 Also, I'm still looking for a volunteer to make changes/announcements etc. 15:45 +1 15:45 +1 received from sil2100 15:45 +1 15:45 +1 received from rbasak 15:45 #endvote 15:45 Voting ended on: Grant mapreri PPU to pbuilder and libreoffice-dictionaries 15:45 Votes for:4 Votes against:0 Abstentions:0 15:45 Motion carried 15:45 \o/ 15:45 Thank you all again! :) 15:46 I guess I'm doing it then! 15:47 added to MOTU, TB needs to add PPI 15:47 PPU 15:47 Ah, thanks micahg! 15:47 Do you mind sorting those? 15:47 (and the announcement) 15:47 You're welcome! 15:47 been having a little trouble with email I'm trying to resolve 15:47 OK, I'll sort 15:47 #action rbasak to announce mapreri's MOTU and PPU status 15:47 * meetingology rbasak to announce mapreri's MOTU and PPU status 15:47 #action rbasak to get mapreri's PPU additions done by the TB 15:47 * meetingology rbasak to get mapreri's PPU additions done by the TB 15:47 micahg: thanks for handling those o/ 15:48 #subtopic Gianfranco Costamagna (costamagnagianfranco) 15:48 LocutusOfBorg: hello! 15:49 hello :) 15:50 LocutusOfBorg: shall I jump straight to questions? What are your thoughts on the "Areas of Improvement" type comments from the endorsers of your application? 15:51 I don't have any real answer, I think giings is right 15:51 FWIW I try to find the best approach following each cases, and try to keep transitions in sync with Debian 15:52 and I try to avoid breaking the freeze whenever possible :) 15:52 OK 15:52 What about pitti's comment on dropping deltas? 15:52 but sometimes I think breaking it is the right thing to do 15:52 (well, eliminating rather than dropping I guess) 15:52 I think this happened only once, and I still didn't get why and how my workflow failed 15:53 it didn't happen again, so I couldn't debug it further 15:53 considering I uploaded ~1k packages or more, I didn't consider it a real issue 15:53 To be clear, which question are you answering there? 15:53 http://people.ubuntuwire.org/~stefanor/ubuntu-activity/ 15:53 it happened once that during a merge I dropped an ubuntu delta that was still needed 15:54 Ah, I see. 15:54 when I got mail I readded it quickly 15:54 not sure if MoM failed, or I failed, or both of us :p 15:54 As an aside, if MoM failed then that's still the uploader's responsibility to check it, IMHO. 15:55 completely true 15:55 Final question. Above you said "sometimes I think breaking it is the right thing to do". What process would you follow if you thought this case the case? 15:55 this was the case? 15:55 I *always* bother people on #-release :) 15:56 What if I said it was OK in #ubuntu-release? Would you upload it then? 15:56 I don't bother people for some particular cases, e.g. when a new kernel is uploaded after the freeze, and my pet virtualbox-dkms breaks 15:56 Maybe that's too much of a trick question, sorry. 15:56 rbasak, last time I checked you weren't part of ubuntu-release team :p 15:56 I mean: how do you know...right :) 15:56 OK, I'm done. 15:56 Does anyone have any other questions for LocutusOfBorg? 15:57 * mapreri thinks we are supposed to know who wears the release hat :) 15:57 usually I ask directly to one release team member, who I think is the best person to answer my question 15:58 I think that's fine, since any one release team member can grant an exception. 15:58 #vote Grant LocutusOfBorg core dev 15:58 Please vote on: Grant LocutusOfBorg core dev 15:58 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) 15:58 micahg, sil2100, cyphermox: ^ 16:01 LocutusOfBorg: could you please clarify what you mean by your comment about a kernel upload after freeze and virtualbox-dkms breaks? 16:02 micahg, a new kernel release usually breaks kernel modules 16:03 yes, but what does that mean in terms of virtualbox that you would do 16:03 virtualbox builds virtualbox-dkms and virtualbox-guest-dkms kernel modules, and I have to adapt them to make them working/buildable 16:03 e.g. I did this some days ago 16:03 http://launchpadlibrarian.net/293649507/virtualbox_5.1.8-dfsg-6build1_5.1.8-dfsg-7~build1.diff.gz 16:03 look for e.g. 16:04 + #if LINUX_VERSION_CODE < KERNEL_VERSION(4, 8, 0) 16:04 + r = ttm_bo_move_memcpy(bo, evict, no_wait_gpu, new_mem); 16:04 ++#elif LINUX_VERSION_CODE < KERNEL_VERSION(4, 9, 0) 16:04 yeah API changes often break dkms 16:04 Right, so it's anyway a case where you're just fixing a breakage, so all good 16:04 yes, indeed 16:05 Ok, as for voting: 16:05 +1 16:05 +1 received from sil2100 16:07 +1 16:07 +1 received from micahg 16:07 +1 16:07 +1 received from cyphermox 16:07 +1 16:07 +1 received from rbasak 16:07 #endvote 16:07 Voting ended on: Grant LocutusOfBorg core dev 16:07 Votes for:4 Votes against:0 Abstentions:0 16:07 Motion carried 16:08 thanks :) 16:08 LocutusOfBorg: congratulations, and thank you for looking after Ubuntu for us! 16:08 \o/ 16:08 LocutusOfBorg: really, ^5 ! 16:08 LocutusOfBorg: congrats! 16:08 thanks :D 16:08 LocutusOfBorg: to be clear, what I think we were looking for is that you understand that though the virtualbox fix is obviously needed, from a process perspective it is that it is a bugfix that allows you to upload after feature freeze without release team approval, not just because it's obviously appropriate. 16:09 rbasak, yes I got it 16:09 +1 on rbasak's statement 16:10 LocutusOfBorg: we were just struggling a little to hear that from you, but I think we all concluded that you understood that in the end :) 16:11 :) I try to find the best tradeoff between breaking changes and bugfixes, it isn't always a clear line, but I ask when in doubt 16:11 action rbasak to announce LocutusOfBoar'd core dev status 16:11 #action rbasak to add LocutusOfBorg to ~ubuntu-core-dev 16:11 * meetingology rbasak to add LocutusOfBorg to ~ubuntu-core-dev 16:11 ta 16:11 #action rbasak to announce LocutusOfBoar'd core dev status 16:11 * meetingology rbasak to announce LocutusOfBoar'd core dev status 16:11 s/Boar/Borg/ Sorry! 16:11 :) 16:12 #topic Request to add gce-compute-image-packages to the ubuntu-cloud packageset 16:13 philroche: o/ 16:13 rbasak: o/ 16:13 Sorry we didn't address this on the ML already. 16:13 np 16:14 I'm surprised that the package isn't seeded. 16:14 And nor is it in main. But it's installed by default? 16:15 That should have no bearing on packageset membership though. 16:15 This is a new package. The previous incarnation, gce_utils [1], was in proposed. [1] https://launchpad.net/ubuntu/+source/gce-utils 16:15 *is in proposed 16:15 I think your request is obviously correct now that I've looked, so +1 for the packageset change, and we don't need a vote. 16:16 Super. Thanks 16:16 #action rbasak to add gce-compute-image-packages to the ubuntu-cloud packageset 16:16 * meetingology rbasak to add gce-compute-image-packages to the ubuntu-cloud packageset 16:16 I'm not sure it's in the right place though. Perhaps a question for the release team. 16:17 thanks Robbie! 16:17 philroche: is the package in cloud images today? 16:18 rbasak: It is in Yakkety dailies images for GCE 16:18 OK, I'll raise that separately, thanks. Not a DMB thing. 16:18 #topic Any other business 16:18 I'd like to raise two things. 16:19 1) Requests in the ML not yet addressed; 2) Meeting dates over the Christmas period. 16:20 I see GunnarHj's request and cpaelzer's request in the ML not yet addressed. I'd be happy to take both of these. 16:20 But we should probably have a section in the agenda to check for these. Any objections to me adding that? 16:21 For future meetings, the next meeting on 5 December should I think be fine. 16:21 19 December seems unlikely to get quorum and currently has no applications. 16:22 Same for 2 Jan. 16:22 So I propose we drop those two, and next meet on 16 Jan, unless anyone objects (now or later). 16:23 I guess that means nobody objects. 16:23 #action rbasak to address GunnarHj's im-config yakkety question on the ML 16:23 * meetingology rbasak to address GunnarHj's im-config yakkety question on the ML 16:24 #action rbasak to address cpaelzer's dovecot-antispam ubuntu-server packageset request on the ML 16:24 * meetingology rbasak to address cpaelzer's dovecot-antispam ubuntu-server packageset request on the ML 16:25 #agreed Skip meetings on 19 December and 2 January unless anyone objects now or in the future 16:25 #agreed Add "Unaddressed ML requests" to the meeting agenda 16:25 #endmeeting