13:00 #startmeeting Weekly Main Inclusion Requests status 13:00 Meeting started Tue Sep 25 13:00:03 2018 UTC. The chair is cyphermox. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 13:00 13:00 Available commands: action commands idea info link nick 13:00 anybody absolutely wants to chair? 13:00 seems you started :) 13:01 I'm fine with not chairing :p 13:01 ack 13:01 well, let's carry on 13:01 #topic New MIRs 13:01 hi 13:01 I'm playing it by ear, bear with me 13:01 new since X? 13:02 new since the last I noticed 13:02 sorting the bugs by bug number? 13:02 fine with me 13:02 there's pmdk 13:02 I updated pmdk 13:02 LP: #1790856 13:02 Launchpad bug 1790856 in pmdk (Ubuntu) "[MIR] pmdk" [Undecided,New] https://launchpad.net/bugs/1790856 13:02 ok 13:02 this is now on the security team 13:03 cpaelzer: wasn't it server team? 13:03 it is ours 13:03 ok 13:03 but all former concerns were eliminated 13:03 alright 13:03 next step, security 13:03 kk 13:03 it is in our prioritized list 13:03 LP: #1786489 rygel 13:03 Launchpad bug 1786489 in rygel (Ubuntu) "[MIR] rygel" [Undecided,New] https://launchpad.net/bugs/1786489 13:03 the whole dlna stack was assigned to me last week 13:03 this is desktop, I thought it had been reviewed before 13:04 Important to know this also drags in gupnp-dlna (MIR bug #1785649) and gupnp-av (MIR bug #1785629) 13:04 bug 1785649 in gupnp-dlna (Ubuntu) "[MIR] gupnp-dlna" [Undecided,New] https://launchpad.net/bugs/1785649 13:04 material for 19.04 at this stage 13:04 bug 1785629 in gupnp-av (Ubuntu) "[MIR] gupnp-av" [Undecided,New] https://launchpad.net/bugs/1785629 13:04 yep, those 3 ;) 13:04 yup 13:04 oh, actually 13:04 well, didrocks, best of luck with all that ;) 13:04 cpaelzer: we shouldn't review MIRs we filed ourselves... 13:04 cyphermox: thanks, I'll need it :p TBH, I don't plan having a look before 3 weeks, once we are near release 13:05 you're marked as the reporter for the pmdk bug 13:05 cpaelzer: that is why I had doko make the update after I summarized the state 13:05 unsure how we can mark those so that they don't came back in our meeting until $DELAY 13:05 cyphermox: ^^ 13:05 cpaelzer: ack. 13:05 didrocks: we can think of something in a bit ;) 13:05 yep ;) 13:05 ok, next 13:06 LP: #1786201 MIR for intel-ipsec-mb 13:06 Launchpad bug 1786201 in intel-ipsec-mb (Ubuntu Cosmic) "MIR for intel-ipsec-mb" [Medium,New] https://launchpad.net/bugs/1786201 13:06 I can take that? 13:06 oh, it's already assigned to security 13:06 this isn't working as well as I thought it would 13:06 on that I acted only as the reporter, and I asked jdstrand to lower the prio 13:07 it is currently in the list as possible to defer to 19.04 13:07 it is high for 19.04 13:07 can we say, make sure we put things in Confirmed if they're assigned / otherwise reviewed 13:07 it will likely be deferred 13:07 and then always just look at News for this meeting? 13:07 ack 13:08 jdstrand: would that work for the security team too? 13:08 if they are on security we would mark them confirmed and assigned to security then? 13:08 or we filter on NEW without assignee? 13:08 don't have strong opinions 13:08 *shrugs* 13:08 we don't filter on NEW vs !NEW 13:08 did "confirmed" so far carry a special meaning for you all? 13:08 so that's fine with me 13:08 not really 13:09 neither did Triaged 13:09 no assignments I have this: 13:09 https://bugs.launchpad.net/~ubuntu-mir/+subscribedbugs?field.searchtext=&search=Search&field.status%3Alist=NEW&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.ha 13:09 s_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&orderby=-id&start=0 13:10 ten bugs, but all slightly older 13:10 actually, not even ten 13:10 the percona-* one is one big chunk 13:10 cyphermox: also given your list so far you don't see "incomplete", e.g. you might miss ledmon LP: #1794219 which I invalidated today 13:10 Launchpad bug 1794219 in ledmon (Ubuntu) "[MIR] ledmon" [Undecided,Incomplete] https://launchpad.net/bugs/1794219 13:11 that is, until the reporter provides the required info 13:11 cpaelzer: well incomplete would mean it's thrown back to the reporter to fix something? 13:11 so do we need to reassign? 13:11 no it exactly is "thrown back to the reporter to fix something" 13:11 which is why I had chosen "no assignee + incomplete" 13:12 yeah 13:12 just saying "such updates" will be missing in your list 13:12 if we check that weekly 13:12 my question is, do we need to go through those right now? 13:12 if we're just assigning new bugs 13:12 I think Team members can mention those if there was anything special but otherwise we can skip them 13:12 opinions? 13:12 we can go through those right after? 13:12 cyphermox: +1 13:13 first new assigns, then go through incompletes see if there's something we missed? 13:13 sounds good 13:13 I'm happy to take percona-* 13:13 and then, if people wants to ask questions on in progress MIRs or are blocked on anything, we can tackle them 13:13 yep 13:13 ok, LP: ##1742711 MIR: vulkan(-loader) 13:14 oops 13:14 LP: #1742711 MIR: vulkan(-loader) 13:14 Launchpad bug 1742711 in vulkan (Ubuntu) "MIR: vulkan(-loader)" [Undecided,New] https://launchpad.net/bugs/1742711 13:14 who wants? 13:14 looks desktopy 13:14 yep, can add 13:15 I don't think the desktop team has signed up for that at all yet 13:15 FYI: the old "All open unclaimed MIR bugs" on https://wiki.ubuntu.com/MIRTeam was broken anyway, I replaced it with cyphermox new link above 13:15 LP: #1605337 [MIR] virtualbox 13:15 Launchpad bug 1605337 in virtualbox (Ubuntu) "[MIR] virtualbox" [Undecided,Incomplete] https://launchpad.net/bugs/1605337 13:15 my filter is not perfect 13:15 carrying on ;) 13:16 LP: #1274247 [MIR] Glusterfs 13:16 Launchpad bug 1274247 in tgt (Ubuntu) "[MIR] Glusterfs" [Undecided,Triaged] https://launchpad.net/bugs/1274247 13:16 it is much better than the old broken link leading to a LP-oops 13:16 I'm not sure why all the other tasks are on that bug for glusterfs 13:16 I think I do 13:17 ok, it was NAKed, and nobody signed up 13:17 (to maintain) 13:17 yep 13:17 looks like this is probably just a triage to do 13:17 the tasks are packages that would drop Delta 13:17 cpaelzer: you want to do the triage? 13:17 I will, but that essentially is setting all to Won't Fix 13:17 yup 13:18 next; LP: #1108935 [MIR] websockify, spice-html5 13:18 Launchpad bug 1108935 in websockify (Ubuntu) "[MIR] websockify, spice-html5" [High,New] https://launchpad.net/bugs/1108935 13:18 security review a year ago, no answer since then 13:18 I would set it as incomplete, thoughts? 13:19 agreed 13:19 (done) 13:19 otoh it was an ACK 13:19 yeah, but with some changes 13:19 well it was opened and driven by chuck 13:19 jamespage: is that something you guys want to have a look at? 13:19 jamespage: do you have any insight what became of this? 13:19 it did not end up on our side of the team split afaik 13:20 * jamespage looks again 13:20 no its an ubuntu-openstack team thing 13:20 Quote "Rationale: Dependency for nova console access" 13:20 if it's still required, what next steps are, how to schedule the engineering time to do the changes 13:20 I see some work in websockify based on the security team review 13:21 let's reassign to the openstack team, with a note? 13:21 yes - done 13:21 ah, cool, thanks! 13:22 np 13:23 and finally, LP: #821883 [MIR] argyll 13:23 Launchpad bug 821883 in argyll (Ubuntu) "[MIR] argyll" [High,New] https://launchpad.net/bugs/821883 13:23 looks like another one with changes requested 13:23 didrocks: doko: you both commented on previously, do you recall what the state is? 13:24 cyphermox: not really, I commented on it in 2011 ;) 13:24 sounds like doko requested 2 changes, one is done 13:24 afaik the exotic build system isn't great, but we don't require MIRs for build-deps anymore 13:24 three years ... 13:25 3 < 7 ;) 13:25 I'll reassign to Till and ask if this is still required 13:25 yep 13:25 yeah, better before looking again 13:26 FYI the linked blueprint is tagged as done 13:26 maybe there was a different way to get this done after all 13:26 we have ICC color profile support for a while in ubuntu 13:26 which is why I wonder why Till still reverted it to NEW 13:27 *shrugs* 13:27 looks like I skipped over one 13:27 LP: #1770146 [MIR] libayatana-appindicator 13:27 Launchpad bug 1770146 in libayatana-appindicator (Ubuntu) "[MIR] libayatana-appindicator" [High,New] https://launchpad.net/bugs/1770146 13:27 seriously? 13:27 * didrocks looks 13:28 ah, doko commented 13:28 nack for desktop team to maintain it anyway: https://bugs.launchpad.net/ubuntu/+source/libayatana-appindicator/+bug/1770146/comments/11 13:28 Launchpad bug 1770146 in libayatana-appindicator (Ubuntu) "[MIR] libayatana-appindicator" [High,New] 13:28 ah I see 13:29 it would replace appindicator, and it looks like maybe there are changes to some revdeps 13:30 and we are not interested in appindicator anymore as based on GNOME which doesn't support this 13:30 still "incomplete - unless an owning team is found" right? 13:30 right 13:30 yeah, I'm updating 13:32 #topic Incomplete bugs / questions 13:33 https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-importance&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=ubuntu-mir&field.structural_subscriber=&field.component-empty-marker=1&field.tag=&field.tags_combinator=ANY&field.status_upstream-empty-marker=1 13:33 &field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_no_package.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search 13:33 another URL of doom 13:34 any questions on open MIR bugs, or stuff that need to be shared? 13:34 maybe the last list should be ordered by last updated 13:35 On "imcomplete bugs" - as I said I marked LP: #1794219 incomplete today waiting for the reporter - being the least experienced here let me know if this was wrong 13:35 Launchpad bug 1794219 in ledmon (Ubuntu) "[MIR] ledmon" [Undecided,Incomplete] https://launchpad.net/bugs/1794219 13:36 no, looks good 13:36 afaik foundations would own it (that's what I recall from discussions last week), but I'll ask to confirm that 13:37 cyphermox: could you move these URLs into the MIRTeam wiki? 13:37 also, to keep the list short, we should try to see if there are bugs there that can be set Won't Fix for real 13:37 doko: yup 13:37 tbh it's filters I set up just now from the LP forms 13:38 maybe I'll try to get something to generate such a report 13:38 still useful in the wiki to use the same every week 13:38 yup 13:39 does anybody feel the need to go over each of the incompletes? I don't really ;) 13:39 not really (and in parallel weekly desktop meeting right now) 13:39 +1 on filtering the incomplete list, best done by whoever was involved back then 13:39 yep 13:39 I will kill a few server items there 13:39 ack 13:39 cool, moving on... 13:39 #topic Any other business? 13:40 anything else MIR Team related that isn't the open MIRs? 13:41 oh, fwiw I'll record the commands and write a short script for running the meetings ;) 13:41 so it's more copy-paste next time 13:41 \o/ 13:41 yay 13:41 #action cyphermox to add bug list URLs to wiki 13:41 * meetingology cyphermox to add bug list URLs to wiki 13:42 cool, then let's call this one done 13:42 jamespage: you were hanging out here, anything you wanted to ask about, concerns, etc? 13:42 not today 13:43 alright 13:43 thanks all! 13:43 #endmeeting